How to apply migrations with MSSQL server?

[chrisknu]

Hi there,

I'm accustomed to migrations being generated with table/schema changes via a local hasura console (postgres).

When attempting to set up migrations with a local instance of hasura/MSSQL, I'm running into this error:

hasura migrate create "init" --from-server --database-name
FATA[0000] cannot fetch schema dump: schema dump for source of kind mssql is not supported

I can get the metadata to export and apply just fine, but migrations seem to be failing. Any help is welcome.

[BenoitRanque]

MSSQL support for this functionality does not exist yet, you would need to create your init migration manually using the MSSQL equivalent of PG_DUMP

[chrisknu]

Is it possible to have a blank 'init' created and a 'mssql does not support this action' warning thrown in the console? It looks like migrations after the initial one work just fine, but it took a bit of time to figure that out.

…

On Mon, Feb 21, 2022 at 2:15 PM Benoit Ranque ***@***.***> wrote: MSSQL support for this functionality does not exist yet, you would need to create your init migration manually using the MSSQL equivalent of PG_DUMP — Reply to this email directly, view it on GitHub <#8180 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALORIJ5P3HHLMJ4V6DOJLDU4KFNJANCNFSM5OPPLQXA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[BenoitRanque]

The init migration is only necessary so you can track your database's initial state before you started creating migrations with the console.
You can absolutely write that file manually. As for the errors in the console, I'm a bit confused, aren't you running into this error from the CLI?

[chrisknu]

Correct, I was hitting the “mssql is not supported” error from the cli… and tracked it back to the line linked above. At the time, I didn’t know mssql had no pg_dump equivalent.. and thus thought (because of the error and missing mapping) that it was yet to be implemented. A slightly more verbose error message would have helped short circuit me/anybody else that could hit the same issue

…

On Mon, Feb 21, 2022 at 7:15 PM Benoit Ranque ***@***.***> wrote: The init migration is only necessary so you can track your database's initial state before you started creating migrations with the console. You can absolutely write that file manually. As for the errors in the console, I'm a bit confused, aren't you running into this error from the CLI? — Reply to this email directly, view it on GitHub <#8180 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALORIMZ4RQ7W5QFSKZOQQDU4LIQJANCNFSM5OPPLQXA> . You are receiving this because you authored the thread.Message ID: ***@***.***>