SQL Azure Migration Wizard v3.8.8 & v4.0.1

Commented Issue: Original text encoding changed [6938]

ghuey — Fri, 11 May 2012 19:57:52 GMT

Analyze TSQL file changes the text encoding in the target. For example,

Mykolaïvs changed to MykolaÃ¯vs
Comments: ** Comment from web user: ghuey **

Hi,

I found the problem and I have actually fixed it, but that introduced another problem that I am working on with the comments. This one might take some time. It will be fixed in the next release. I will let you know when I post the fix.

Regards,
George

Commented Issue: Incorrectly remove comments [6937]

ghuey — Thu, 10 May 2012 23:57:47 GMT

When I analyzed the TSQL script, the tool incorrectly removed the comments which contains TSQL statements inside the comment.

/*
USE [MyDatabase];
IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[mySchema].[myProc]') AND type in (N'P', N'PC'))
DROP PROCEDURE [mySchema].[myProc];
GO
*/

turned into

*/
Comments: ** Comment from web user: ghuey **

Ok, I believe it is fixed in v3.8.8. Check it out and let me know if it didn't work.

Thanks,
George

Updated Release: SQLAzureMW v3.8.8 and v4.0.1 (May 10, 2012)

ghuey — Thu, 10 May 2012 23:55:27 GMT

Requirements
SQLAzureMW v3x requires SQL Server 2008 R2 SP1 bits to be on the same machine.

SQLAzureMW v4x requires SQL Server 2012 bits to be on the same machine.

Issues
If you have a question / issue with SQLAzureMW, please post your question via the discussion http://sqlazuremw.codeplex.com/discussions page.

Binaries
.NET 3.5 SP1
Only tested (so far) on Windows 7 RTM (should work fine on XP or Vista)

Language Translations (Special Thanks)

大和屋貴仁 (Takahito Yamatoya) - Japanese
安納順一 (Junichi Anno) - Japanese
Oliver Hauth - German
Sam Vanhoutte - Dutch
Luis Antonio Soler Barrera – Spanish
Axel Guerrier – French
梁琦 (Mog Liang) – Chinese

Source
Visual Studio 2008 SP1
.NET 3.5 SP1
Only tested (so far) on Windows 7 RTM (should work fine on XP or Vista)
Please let us know if you encounter any problems or difficulties

v3.8.8

Fixed bug that removed USE statement and moved the check to NotSupportedByAzureFile.Config

v3.8.7

Modified NotSupportedByAzureFile.config to look for a MERGE in a regex pattern "SELECT\w\W ^;*\sINTO" to avoid false positives.
Fixed bug with changed a nonclustered index (that had INCLUDE columns) to clustered index

v3.8.6

Fixed bug when reading trace files and getting an event with no text data (null string).

v3.8.5

Fixed bug for user names having a space in them. Put quotes around the name for BCP.
Removed hard coded trace events to check and added key “TraceEventsToCheck” to application config file.
Fixed issue with SQLAzureMW not displaying error message when SQL Server client side tools are not installed on the machine.
Modified SQLAzureMWBatchUpload to do parallel processing.

v3.8.4

No code change. Just modified NotSupportedByAzureFile.Config to remove check for SPARSE columns since SQL Azure now supports SPARSE columns.

v3.8.3

Added Retry class
Modified app.config files to include new retry key values
Fixed bug when migrating SQL Azure Federation to SQL Azure Federation
Put retry wrapper around SQLHelper commands

v3.8.2

Fixed logic in SQLAzureMWBatchUpload to add { true | false } to -d (drop database) command
Moved Regex valid SQL table character match string to app.config file. See key: SpecialTableCharacters

v3.8.1

Added check for 08S01 in app.confg
Fix bug in SQLAzureMWBatchBackup to enable scripting of user defined functions.

v3.8

Added support for database collation
Added 100 & 150 GB options for creating a database in SQL Azure

v3.7.8

Fixed code to look for special character #
Added support for SQL Azure Federations
Modified SQLAzureMW.exe.config to allow user to specify source and target database type
Modified connect to database dialog box to allos database type
Getting software ready for next release of SQL Azure

v3.7.7

Fixed command parsing error which caused app to crash when parsing a TSQL file.
Added retry logic when getting row count from Windows Azure

v3.7.6

Removed "IsSystemObject" from User Defined Tables Types (works with SQL Server, but does not work with SQL Azure).

v3.7.5

Added function GetSmoServer to CommonFunc class in SQLAzureMWUtils
Refined Regex search command for Backup / Kill commands
Refined Regex search command for Raiserror commands
I installed SQL Server 2008 R2 SP1 which is what SQLAzureMW v3.7.5 is compiled against. So if you don't have SP1 installed and you run into issues running SQLAzureMW, please let me know!

Released: SQLAzureMW v3.8.8 and v4.0.1 (May 10, 2012)

Thu, 10 May 2012 23:55:27 GMT

大和屋貴仁 (Takahito Yamatoya) - Japanese
安納順一 (Junichi Anno) - Japanese
Oliver Hauth - German
Sam Vanhoutte - Dutch
Luis Antonio Soler Barrera – Spanish
Axel Guerrier – French
梁琦 (Mog Liang) – Chinese

Source
Visual Studio 2008 SP1
.NET 3.5 SP1
Only tested (so far) on Windows 7 RTM (should work fine on XP or Vista)
Please let us know if you encounter any problems or difficulties

v3.8.8

Fixed bug that removed USE statement and moved the check to NotSupportedByAzureFile.Config

v3.8.7

Modified NotSupportedByAzureFile.config to look for a MERGE in a regex pattern "SELECT\w\W ^;*\sINTO" to avoid false positives.
Fixed bug with changed a nonclustered index (that had INCLUDE columns) to clustered index

v3.8.6

Fixed bug when reading trace files and getting an event with no text data (null string).

v3.8.5

Fixed bug for user names having a space in them. Put quotes around the name for BCP.
Removed hard coded trace events to check and added key “TraceEventsToCheck” to application config file.
Fixed issue with SQLAzureMW not displaying error message when SQL Server client side tools are not installed on the machine.
Modified SQLAzureMWBatchUpload to do parallel processing.

v3.8.4

No code change. Just modified NotSupportedByAzureFile.Config to remove check for SPARSE columns since SQL Azure now supports SPARSE columns.

v3.8.3

Added Retry class
Modified app.config files to include new retry key values
Fixed bug when migrating SQL Azure Federation to SQL Azure Federation
Put retry wrapper around SQLHelper commands

v3.8.2

Fixed logic in SQLAzureMWBatchUpload to add { true | false } to -d (drop database) command
Moved Regex valid SQL table character match string to app.config file. See key: SpecialTableCharacters

v3.8.1

Added check for 08S01 in app.confg
Fix bug in SQLAzureMWBatchBackup to enable scripting of user defined functions.

v3.8

Added support for database collation
Added 100 & 150 GB options for creating a database in SQL Azure

v3.7.8

Fixed code to look for special character #
Added support for SQL Azure Federations
Modified SQLAzureMW.exe.config to allow user to specify source and target database type
Modified connect to database dialog box to allos database type
Getting software ready for next release of SQL Azure

v3.7.7

Fixed command parsing error which caused app to crash when parsing a TSQL file.
Added retry logic when getting row count from Windows Azure

v3.7.6

Removed "IsSystemObject" from User Defined Tables Types (works with SQL Server, but does not work with SQL Azure).

v3.7.5

Added function GetSmoServer to CommonFunc class in SQLAzureMWUtils
Refined Regex search command for Backup / Kill commands
Refined Regex search command for Raiserror commands
I installed SQL Server 2008 R2 SP1 which is what SQLAzureMW v3.7.5 is compiled against. So if you don't have SP1 installed and you run into issues running SQLAzureMW, please let me know!

Updated Release: SQLAzureMW v3.8.8 and v4.0.1 (May 10, 2012)

ghuey — Thu, 10 May 2012 23:50:05 GMT

大和屋貴仁 (Takahito Yamatoya) - Japanese
安納順一 (Junichi Anno) - Japanese
Oliver Hauth - German
Sam Vanhoutte - Dutch
Luis Antonio Soler Barrera – Spanish
Axel Guerrier – French
梁琦 (Mog Liang) – Chinese

Source
Visual Studio 2008 SP1
.NET 3.5 SP1
Only tested (so far) on Windows 7 RTM (should work fine on XP or Vista)
Please let us know if you encounter any problems or difficulties

v3.8.7

Modified NotSupportedByAzureFile.config to look for a MERGE in a regex pattern "SELECT\w\W ^;*\sINTO" to avoid false positives.
Fixed bug with changed a nonclustered index (that had INCLUDE columns) to clustered index

v3.8.6

Fixed bug when reading trace files and getting an event with no text data (null string).

v3.8.5

Fixed bug for user names having a space in them. Put quotes around the name for BCP.
Removed hard coded trace events to check and added key “TraceEventsToCheck” to application config file.
Fixed issue with SQLAzureMW not displaying error message when SQL Server client side tools are not installed on the machine.
Modified SQLAzureMWBatchUpload to do parallel processing.

v3.8.4

No code change. Just modified NotSupportedByAzureFile.Config to remove check for SPARSE columns since SQL Azure now supports SPARSE columns.

v3.8.3

Added Retry class
Modified app.config files to include new retry key values
Fixed bug when migrating SQL Azure Federation to SQL Azure Federation
Put retry wrapper around SQLHelper commands

v3.8.2

Fixed logic in SQLAzureMWBatchUpload to add { true | false } to -d (drop database) command
Moved Regex valid SQL table character match string to app.config file. See key: SpecialTableCharacters

v3.8.1

Added check for 08S01 in app.confg
Fix bug in SQLAzureMWBatchBackup to enable scripting of user defined functions.

v3.8

Added support for database collation
Added 100 & 150 GB options for creating a database in SQL Azure

v3.7.8

Fixed code to look for special character #
Added support for SQL Azure Federations
Modified SQLAzureMW.exe.config to allow user to specify source and target database type
Modified connect to database dialog box to allos database type
Getting software ready for next release of SQL Azure

v3.7.7

Fixed command parsing error which caused app to crash when parsing a TSQL file.
Added retry logic when getting row count from Windows Azure

v3.7.6

Removed "IsSystemObject" from User Defined Tables Types (works with SQL Server, but does not work with SQL Azure).

v3.7.5

Added function GetSmoServer to CommonFunc class in SQLAzureMWUtils
Refined Regex search command for Backup / Kill commands
Refined Regex search command for Raiserror commands
I installed SQL Server 2008 R2 SP1 which is what SQLAzureMW v3.7.5 is compiled against. So if you don't have SP1 installed and you run into issues running SQLAzureMW, please let me know!

Released: SQLAzureMW v3.8.8 and v4.0.1 (May 10, 2012)

Thu, 10 May 2012 23:50:05 GMT

大和屋貴仁 (Takahito Yamatoya) - Japanese
安納順一 (Junichi Anno) - Japanese
Oliver Hauth - German
Sam Vanhoutte - Dutch
Luis Antonio Soler Barrera – Spanish
Axel Guerrier – French
梁琦 (Mog Liang) – Chinese

Source
Visual Studio 2008 SP1
.NET 3.5 SP1
Only tested (so far) on Windows 7 RTM (should work fine on XP or Vista)
Please let us know if you encounter any problems or difficulties

v3.8.7

Modified NotSupportedByAzureFile.config to look for a MERGE in a regex pattern "SELECT\w\W ^;*\sINTO" to avoid false positives.
Fixed bug with changed a nonclustered index (that had INCLUDE columns) to clustered index

v3.8.6

Fixed bug when reading trace files and getting an event with no text data (null string).

v3.8.5

Fixed bug for user names having a space in them. Put quotes around the name for BCP.
Removed hard coded trace events to check and added key “TraceEventsToCheck” to application config file.
Fixed issue with SQLAzureMW not displaying error message when SQL Server client side tools are not installed on the machine.
Modified SQLAzureMWBatchUpload to do parallel processing.

v3.8.4

No code change. Just modified NotSupportedByAzureFile.Config to remove check for SPARSE columns since SQL Azure now supports SPARSE columns.

v3.8.3

Added Retry class
Modified app.config files to include new retry key values
Fixed bug when migrating SQL Azure Federation to SQL Azure Federation
Put retry wrapper around SQLHelper commands

v3.8.2

Fixed logic in SQLAzureMWBatchUpload to add { true | false } to -d (drop database) command
Moved Regex valid SQL table character match string to app.config file. See key: SpecialTableCharacters

v3.8.1

Added check for 08S01 in app.confg
Fix bug in SQLAzureMWBatchBackup to enable scripting of user defined functions.

v3.8

Added support for database collation
Added 100 & 150 GB options for creating a database in SQL Azure

v3.7.8

Fixed code to look for special character #
Added support for SQL Azure Federations
Modified SQLAzureMW.exe.config to allow user to specify source and target database type
Modified connect to database dialog box to allos database type
Getting software ready for next release of SQL Azure

v3.7.7

Fixed command parsing error which caused app to crash when parsing a TSQL file.
Added retry logic when getting row count from Windows Azure

v3.7.6

Removed "IsSystemObject" from User Defined Tables Types (works with SQL Server, but does not work with SQL Azure).

v3.7.5

Added function GetSmoServer to CommonFunc class in SQLAzureMWUtils
Refined Regex search command for Backup / Kill commands
Refined Regex search command for Raiserror commands
I installed SQL Server 2008 R2 SP1 which is what SQLAzureMW v3.7.5 is compiled against. So if you don't have SP1 installed and you run into issues running SQLAzureMW, please let me know!

Commented Issue: Incorrectly remove comments [6937]

ghuey — Thu, 10 May 2012 22:52:05 GMT

Actually, let me correct myself. It is not the GO that was the issue, it was the "USE [MyDatabase]" that caused me the issue. SQLAzureMW looks for the "USE [MyDatabase]" commands and removes them since SQL Azure does not like them. The problem is:

1) I should not remove them from a comment line
2) Not only did I remove the USE statement, but I removed everything else through the GO.

Sorry,
George

Commented Issue: Incorrectly remove comments [6937]

ghuey — Thu, 10 May 2012 22:43:21 GMT

Oh, as a side note, the logic flaw on my part is the "GO" inside the comments. I see the GO and start a new command. My bad.

Commented Issue: Incorrectly remove comments [6937]

ghuey — Thu, 10 May 2012 22:38:41 GMT

Yes, I see the issue. It will be fixed in v3.8.8 & v4.0.1

I will respond back to this when I post the fix.

Thanks for reporting this.
George

Created Issue: Original text encoding changed [6938]

Giavinh — Thu, 10 May 2012 22:33:20 GMT

Analyze TSQL file changes the text encoding in the target. For example,

Mykolaïvs changed to MykolaÃ¯vs

Commented Issue: Incorrectly remove comments [6937]

Giavinh — Thu, 10 May 2012 20:52:20 GMT

Sometimes it happens as below

/*
USE [MyDatabase];
GO
IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[mySchema].[myProc]') AND type in (N'P', N'PC'))
DROP PROCEDURE [mySchema].[myProc]
GO
*/

turned into

IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[mySchema].[myProc]') AND type in (N'P', N'PC'))
DROP PROCEDURE [mySchema].[myProc]
GO
*/

Created Issue: Incorrectly remove comments [6937]

Giavinh — Thu, 10 May 2012 20:50:18 GMT

New Post: Index was outside the bounds of the array (but a little bit different)

ghuey — Thu, 10 May 2012 17:09:56 GMT

I am not 100% sure. What I would do is download SQL Server 2008 R2 Evaluation edition or SQL Server 2012 Evaluation edition (for SQLAzureMW v4.0) and run against that. You could also look at downloading all of SQL Server 2008 R2 Express with Management Tools (http://www.microsoft.com/en-us/download/details.aspx?id=23650) and see if that works for you.

This should get you up and running.

Sorry I don't have a better solution at this time.
George

Updated Wiki: Home

ghuey — Thu, 10 May 2012 15:21:43 GMT

Project Description
SQL Azure Migration Wizard (SQLAzureMW) is designed to help you migrate your SQL Server 2005/2008/2012 databases to SQL Azure. SQLAzureMW will analyze your source database for compatibility issues and allow you to fully or partially migrate your database schema and data to SQL Azure.

Requirements
SQLAzureMW v3x and tools requires SQL Server 2008 R2 SP1 bits to run.
SQLAzureMW v4x and tools requires SQL Server 2012 bits to run.

SQL Azure
Microsoft® SQL Azure™ is a cloud-based relational database service built on SQL Server® technologies. It provides a highly available, scalable, multi-tenant database service hosted by Microsoft in the cloud. To sign up for SQL Azure, go to SQL Azure Special Offers and Pricing Information.

Announcing Reduced Pricing on SQL Azure

SQL Azure Federation
SQL Azure Federations allows DBAs to scale out their database by federating (sharding) their database. SQL Azure Federation makes it easier to set up the federated databases, and automate the process of adding new federation members.

For more information on SQL Azure Federations see:

For a limited time, new customers can sign up for SQL Azure and get a 1GB Web Edition Database for no charge…and no commitment. This is a great way to try SQL Azure – and the Windows Azure platform – without the risk. For more information go to Windows Azure Platform Introductory Special

Windows Azure
Microsoft is offering a Windows Azure 3 month free trial, so you can try Windows Azure and SQL Azure for free.
For more information go to Try Windows Azure 3 Month free trial.

SQLAzureMW Supported Languages

SQL Azure MWが、国際対応できたことを発表できて光栄に思う。最初の翻訳言語は、日本語です！
SQL Azure MW unterstützt nun die deutsche Sprache.
SQL Azure MW ondersteunt nu de taal Nederlands.
SQL Azure MW ahora soporta el idioma español.
SQL Azure MW supporte maintenant la langue française
SQL Azure MW 现在支持中文了。

Project Description Continued
SQL Azure Migration Wizard (SQLAzureMW) is an open source application that has been used by thousands of people to migrate their SQL database to and from SQL Azure. SQLAzureMW is a user interactive wizard that walks a person through the analysis / migration process. One of the main requests from the SQLAzureMW community was to take the user interactive wizard and make it command line driven interface so that it could be used in an automated backup process to back up their SQL Azure schema / data to a data store for disaster recovery. I am excited to let you know that SQLAzureMW now has two tools that can be used from a command line:

SQLAzureMWBatchBackup:
- This is used to create a backup of a database schema and data. The data is downloaded via BCP. The TSQL output from SQLAzureMWBatchBackup can be used by SQLAzureMW or SQLAzureMWBatchUpload.
SQLAzureMWBatchUpload:
- Takes the output from SQLAzureMW or SQLAzureMWBatchBackup and runs it against the target SQL Azure (or SQL Server) server.

Complete documentation for SQLAzureMW, SQLAzureMWBatchBackup and SQLAzureMWBatchUpload can be found on the download site.

The SQLAzureMW tools greatly simplify schema analysis and migration process. If you don’t have an SQL Azure account and have been thinking about moving your data to the cloud (SQL Azure), but have been afraid to try because of “unknowns” like cost, compatibility, and effort? SQL Azure Migration Wizard SQLAzureMW is a free set of open source applications that have been developed by the database community to help you address these issues. SQLAzureMW will help you analyze your SQL Server database for compatibility issues and will migrate your schema and data to SQL Azure.

SQLAzureMW Project Details
The SQL Azure Migration Wizard (SQLAzureMW) gives you the options to analyzes, generates scripts, and migrate data (via BCP) from:

SQL Server to SQL Azure
SQL Azure to SQL Server
SQL Azure to SQL Azure

It will also analyze SQL Profiler trace files and TSQL script for compatibility issues with SQL Azure.

If your source is a SQL Server database, SQLAzureMW will list all of the object types (i.e. Tables, Stored Procedures, Views, etc.) and let you decide which ones you want analyzed / scripted. Using the “Advanced” options you can tell SQLAzureMW which compatibility checks to perform and if the data should be migrated.
If your source is a file containing TSQL, then you will be given the option to have SQLAzureMW check the TSQL for incompatibilities and fix where possible or just run the script without any compatibility checking.
You can specify a SQL Profiler trace file for analysis.

SQLAzureMWBatchBackup Project Details
The SQLAzureMWBatchBackup is a command line application that will analyze, create TSQL script of database and backup data (via BCP) from a SQL Server or SQL Azure database. The output of SQLAzureMWBatchBackup can be used in SQLAzureMWBatchUpload.

SQLAzureMWBatchUpload Project Details
The SQLAzureMWBatchUpload is a command line application that will run a TSQL script file (and use BCP to upload data) against a target server. SQLAzureMW and SQLAzureMWBatchBackup can be used to generate the TSQL script and the BCP files that can then be used by SQLAzureMWBatchUpload for uploading to a target server. The target server can be SQL Azure or SQL Server.

Configurable
There is a config file “NotSupportedByAzureFile.Config” that is used to define what to look for / replace within the SQL generated code. This file uses RegEx expressions and if you see a pattern that you want removed from the SQL Script, you can put the pattern in the config file and specify what you want to replace it with (if anything).

When the SQL script is generated, an analysis window will be displayed telling you what areas need to be fixed prior to running the script against SQL Azure. Once you are satisfied, you can tell the wizard to run your script against SQL Azure and your script will be ran against your cloud database and the success / failed results will be displayed in a wizard window.

SQL Azure Migration Wizard Utils (SQLAzureMWUtils)
SQLAzureMWUtils is a class library that a developer can use to assist them in developing for SQL Azure. To find out more, read the SQLAzureMWBatch documentation.

Note

SQL Azure Migration Wizard does not catch all of the compatibility issues between different levels of SQL Server databases (i.e. level 80, 90, and 100). SQL Azure is based on SQL Server 2008 (level 100). If you are migrating from an older database (level 80 or 90), you should go through the upgrade process first (at least in the dev environment) and once on SQL Server 2008, then migrate to SQL Azure. Here are some great resources to help you with migrating from older versions of SQL Server:

Further Reading

SQL Azure Compatibility Assessment
Microsoft announced the release of a new experimental cloud service, "SQL Azure Compatibility Assessment" (VSTS573070), as one of SQL Azure Labs. DBAs who are considering moving their SQL Server databases to SQL Azure can use this service to check if the database schema is compatible with SQL Azure grammar. They use SQL Server Data Tools to extract a .dacpac file from the SQL Server database, upload it to our portal1 and get a report listing the schema objects that are not supported in SQL Azure and the objects that need to be fixed prior to deployment into SQL Azure. See the TechNet Wiki for details.

Microsoft SQL Server Migration Assistant (SSMA): The free Microsoft SQL Server Migration Assistant (SSMA) makes it easy to migrate data from Oracle, Microsoft Access, MySQL, and Sybase to SQL Server. SSMA converts the database objects to SQL Server database objects, loads those objects into SQL Server, migrates data to SQL Server, and then validates the migration of code and data.

For information on SQL Azure and the Windows Azure Platform, please see the following resources:

We welcome your feedback! Please let us know if you like this tool or how we can improve it!

Updated Release: SQLAzureMW v3.8.7 and v4.0 (May 10, 2012)

ghuey — Thu, 10 May 2012 15:19:29 GMT

大和屋貴仁 (Takahito Yamatoya) - Japanese
安納順一 (Junichi Anno) - Japanese
Oliver Hauth - German
Sam Vanhoutte - Dutch
Luis Antonio Soler Barrera – Spanish
Axel Guerrier – French
梁琦 (Mog Liang) – Chinese

Source
Visual Studio 2008 SP1
.NET 3.5 SP1
Only tested (so far) on Windows 7 RTM (should work fine on XP or Vista)
Please let us know if you encounter any problems or difficulties

v3.8.7

Modified NotSupportedByAzureFile.config to look for a MERGE in a regex pattern "SELECT\w\W ^;*\sINTO" to avoid false positives.
Fixed bug with changed a nonclustered index (that had INCLUDE columns) to clustered index

v3.8.6

Fixed bug when reading trace files and getting an event with no text data (null string).

v3.8.5

Fixed bug for user names having a space in them. Put quotes around the name for BCP.
Removed hard coded trace events to check and added key “TraceEventsToCheck” to application config file.
Fixed issue with SQLAzureMW not displaying error message when SQL Server client side tools are not installed on the machine.
Modified SQLAzureMWBatchUpload to do parallel processing.

v3.8.4

No code change. Just modified NotSupportedByAzureFile.Config to remove check for SPARSE columns since SQL Azure now supports SPARSE columns.

v3.8.3

Added Retry class
Modified app.config files to include new retry key values
Fixed bug when migrating SQL Azure Federation to SQL Azure Federation
Put retry wrapper around SQLHelper commands

v3.8.2

Fixed logic in SQLAzureMWBatchUpload to add { true | false } to -d (drop database) command
Moved Regex valid SQL table character match string to app.config file. See key: SpecialTableCharacters

v3.8.1

Added check for 08S01 in app.confg
Fix bug in SQLAzureMWBatchBackup to enable scripting of user defined functions.

v3.8

Added support for database collation
Added 100 & 150 GB options for creating a database in SQL Azure

v3.7.8

Fixed code to look for special character #
Added support for SQL Azure Federations
Modified SQLAzureMW.exe.config to allow user to specify source and target database type
Modified connect to database dialog box to allos database type
Getting software ready for next release of SQL Azure

v3.7.7

Fixed command parsing error which caused app to crash when parsing a TSQL file.
Added retry logic when getting row count from Windows Azure

v3.7.6

Removed "IsSystemObject" from User Defined Tables Types (works with SQL Server, but does not work with SQL Azure).

v3.7.5

Added function GetSmoServer to CommonFunc class in SQLAzureMWUtils
Refined Regex search command for Backup / Kill commands
Refined Regex search command for Raiserror commands
I installed SQL Server 2008 R2 SP1 which is what SQLAzureMW v3.7.5 is compiled against. So if you don't have SP1 installed and you run into issues running SQLAzureMW, please let me know!

Released: SQLAzureMW v3.8.7 and v4.0 (May 10, 2012)

Thu, 10 May 2012 15:19:28 GMT

大和屋貴仁 (Takahito Yamatoya) - Japanese
安納順一 (Junichi Anno) - Japanese
Oliver Hauth - German
Sam Vanhoutte - Dutch
Luis Antonio Soler Barrera – Spanish
Axel Guerrier – French
梁琦 (Mog Liang) – Chinese

Source
Visual Studio 2008 SP1
.NET 3.5 SP1
Only tested (so far) on Windows 7 RTM (should work fine on XP or Vista)
Please let us know if you encounter any problems or difficulties

v3.8.7

Modified NotSupportedByAzureFile.config to look for a MERGE in a regex pattern "SELECT\w\W ^;*\sINTO" to avoid false positives.
Fixed bug with changed a nonclustered index (that had INCLUDE columns) to clustered index

v3.8.6

Fixed bug when reading trace files and getting an event with no text data (null string).

v3.8.5

Fixed bug for user names having a space in them. Put quotes around the name for BCP.
Removed hard coded trace events to check and added key “TraceEventsToCheck” to application config file.
Fixed issue with SQLAzureMW not displaying error message when SQL Server client side tools are not installed on the machine.
Modified SQLAzureMWBatchUpload to do parallel processing.

v3.8.4

No code change. Just modified NotSupportedByAzureFile.Config to remove check for SPARSE columns since SQL Azure now supports SPARSE columns.

v3.8.3

Added Retry class
Modified app.config files to include new retry key values
Fixed bug when migrating SQL Azure Federation to SQL Azure Federation
Put retry wrapper around SQLHelper commands

v3.8.2

Fixed logic in SQLAzureMWBatchUpload to add { true | false } to -d (drop database) command
Moved Regex valid SQL table character match string to app.config file. See key: SpecialTableCharacters

v3.8.1

Added check for 08S01 in app.confg
Fix bug in SQLAzureMWBatchBackup to enable scripting of user defined functions.

v3.8

Added support for database collation
Added 100 & 150 GB options for creating a database in SQL Azure

v3.7.8

Fixed code to look for special character #
Added support for SQL Azure Federations
Modified SQLAzureMW.exe.config to allow user to specify source and target database type
Modified connect to database dialog box to allos database type
Getting software ready for next release of SQL Azure

v3.7.7

Fixed command parsing error which caused app to crash when parsing a TSQL file.
Added retry logic when getting row count from Windows Azure

v3.7.6

Removed "IsSystemObject" from User Defined Tables Types (works with SQL Server, but does not work with SQL Azure).

v3.7.5

Added function GetSmoServer to CommonFunc class in SQLAzureMWUtils
Refined Regex search command for Backup / Kill commands
Refined Regex search command for Raiserror commands
I installed SQL Server 2008 R2 SP1 which is what SQLAzureMW v3.7.5 is compiled against. So if you don't have SP1 installed and you run into issues running SQLAzureMW, please let me know!

New Post: Index was outside the bounds of the array (but a little bit different)

jkpindahbc — Tue, 08 May 2012 22:02:32 GMT

There are no updates in SQL 2008 R2 SP1 if you only have Sql Management Studio Installed. Any ideas where to go from here?

New Post: SQLAzureMW data migration stories

ghuey — Tue, 01 May 2012 03:29:37 GMT

Thanks very much for the reply and the positive feedback!!!

New Post: SQLAzureMW data migration stories

PabloInNz — Tue, 01 May 2012 02:30:30 GMT

Hi George,

We are just taking the first steps of migrating a solution to Azure and the SQLAzureMW tool has been invaluable. It's made life very simple and so far on the couple of customer databases we have migrated for our internal testing, it has performed spotlessly. It also picked up a couple of places where we had to change the schema slightly as it wasn't supported in Azure, which was an added bonus.

Commented Issue: Changing index to a clustered index does not remove INCLUDE columns [6906]

ghuey — Tue, 24 Apr 2012 22:08:16 GMT

When SQLAzureMW forces a change of an index to a clustered one (because it detects that there is no such index on a table; mandatory in Azure) it scripts the CREATE INDEX statement with the CLUSTERED attribute but does not take account of any INCLUDEd columns in the original non-clustered index. Thus an illegal statement is generated. Removing the INCLUDE parameter from the automatically generated T-SQL statement would resolve this. [SQLAzureMW v3.8.6 / SQL Server 2008 R2 10.50.2806]
Comments: ** Comment from web user: ghuey **

Ok, this should be fixed in v3.8.7.

Regards,
George