SQL Azure support

[flyway]

Original author: ryanmich...@gmail.com (May 07, 2013 20:14:35)

When I try to execute locally against SQL Express the migrations work correctly. When I moved to Windows Azure using their SQL DB, I had to change the jar file but that wasn't the only issue.

Now when I try to run the migration it says:

Flyway (Command-line Tool) v.2.1.1

Creating Metadata table: [dbo].[schema_version]
ERROR: FlywayException: Unable to insert row for version '1' in metadata table [dbo].[schema_version]
ERROR: Occured in com.googlecode.flyway.core.metadatatable.MetaDataTableImpl.addAppliedMigration() at line 163
ERROR: Caused by com.microsoft.sqlserver.jdbc.SQLServerException: Built-in function 'SUSER_NAME' is not supported in this version of SQL Server.
ERROR: Occured in com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError() at line 216
C:\x\flyway-commandline-2.1.1> .\flyway.cmd init

It turns out that that function: SUSER_NAME is not in SQL Azure but is in SQL Express. How can I use this framework with a Windows Azure SQL DB?

Original issue: http://code.google.com/p/flyway/issues/detail?id=489

[flyway]

From axel.fontaine.business@gmail.com on May 07, 2013 22:19:18
Hi Ryan,

thanks for reporting this. I've just commited a fix for this. Could you try the latest code from GitHub and let me know if it works for you?

Cheers
Axel

[flyway]

From axel.fontaine.business@gmail.com on May 24, 2013 18:26:43
Hi Ryan,

any news?

Cheers
Axel

[flyway]

From ryanmich...@gmail.com on May 28, 2013 21:18:43
Decided to use the RoundhousE framework instead, didn't want to compile this.

[flyway]

From frederik...@gmail.com on June 04, 2013 23:22:20
Hi Axel,

Is this fix in any of the released versions or "only" in master so far?
We are having the same issue with Azure and it would be awesome to have a fix for it.

Cheers, Frederik

[flyway]

From frederik...@gmail.com on June 06, 2013 04:26:10
Hi Axel,

Just thought I let you know that we built the latest version from master, and everything works fine for us now with SQL Azure as well.
Thanks for implementing the fix. Do you already know when the next "official" version will be released which includes this fix?

Cheers, Frederik

[frederikd]

+1

[axelfontaine]

Fixed, tested, and officially support as of 2.2.