SQL Database Migration Wizard v3.9.12 & v4.0.15

Reviewed: SQLAzureMW v3.9.12 and v4.0.15 (May 07, 2013)

Faraz321 — Tue, 07 May 2013 14:46:06 GMT

Rated 5 Stars (out of 5) - Just Signed In to say thanks for this Gem. Solved great problem for me as a beginner. Thank again. Faraz

Reviewed: SQLAzureMW v3.9.12 and v4.0.15 (May 07, 2013)

Faraz321 — Tue, 07 May 2013 14:45:24 GMT

Rated 5 Stars (out of 5) - Just Signed In to say thanks for this Gem. Solved great problem for me as a beginner. Thank again. Faraz faraz321@live.com

New Post: v4.0.15 source

ghuey — Sat, 04 May 2013 13:01:51 GMT

Hi,

The only difference between v4 and v3 is that I change the reference for SQL Server and modify the app.config file (look at the bottom of the config file).

I have this in the app.config file for v4:

<startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0" />
</startup>

I have this in the app.config file for v3

<startup>
    <supportedRuntime version="v2.0.50727" sku="Client"/>
</startup>

I uploaded my v4 VS project here: https://sqlazuremw.codeplex.com/downloads/get/674506

Let me know if you have any questions.

Regards,
George

Updated Release: SQLAzureMW v3.9.12 and v4.0.15 (May 04, 2013)

ghuey — Sat, 04 May 2013 12:52:29 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
小朱 (Jeff Chu) - Chinese Traditional (Taiwan)

Source
Visual Studio 2010 SP1
.NET 3.5 SP1
Works on Windows 8 and Windows 7 (should work fine on XP or Vista).
Please let us know if you encounter any problems or difficulties

v3.9.12 & v4.0.15

Added the capability of doing a search and replace of a sub string found within the rules engine. For example, you have SELECT col1, col2 FROM Employees (NOLOCK) and now you want to replace "(" with "WITH (" so that the results would be SELECT col1, col2 FROM Employees WITH (NOLOCK). Look for XML property "SearchReplace" in NotSupportedByAzureFile.config to see an example.

v3.9.11 & v4.0.14

Added dependency checker to see if Microsoft.SqlServer.Smo and Microsoft.ExceptionMessageBox are on the machine SQLAzureMW is being run on. The dependency information is stored in Dependencies.xml.

v3.9.10 & v4.0.13

Added rule in NotSupportedByAzureFile.Config to remove DATA_COMPRESSION from indexes.
Added BCP error handling to examine message to see if it is a warning in which case do nothing.

v3.9.9.1 & v4.0.12.1

Modified SQLAzureMW to allow you to specify a default collation.

v3.9.9 & v4.0.12

No real bug fixes in this release, but I found that WinForms differs from Windows 7 vs. Windows 8. So, I rebuilt the application on the Windows 8 OS and now the fonts look better for Windows 8 and still seem to run on Windows 7. If you have any font issues, let me know.

v3.9.8 & v4.0.11

SQL Azure Migration Wizard is proud to announce its seventh translation into an international language: Chinese Traditional (Taiwan)! 小朱 (Jeff Chu) did all of the translation work to Chinese Traditional (Taiwan) and deserves all of the credit.

v3.9.7 & v4.0.10

Fixed bug where ALTER TABLE statements did not go through compatibility checker and parser.

v3.9.6.1 & v4.0.9.1 SQLAzureMWBatchBackup

Added the capability to select which database objects you want to backup. To specify which objects to backup, you will need to edit the ObjectSelector.xml file. Inside of that file is documentation on how it works.

v3.9.6 & v4.0.9

Fixed code to handle an empty string password.

v3.9.5 & v4.0.8

Fixed code to take all table constraints and move it to the end of generated script.

v3.9.4 & v4.0.7

Fixed BCP output commands to put quotes around password

v3.9.3 & v4.0.6

Changed some SQL Azure to SQL Database
Fixed BCPArgs parsing to remove need for special character checking

v3.9.2 & v4.0.5

Modified script to move all foreign key constraints to end of TSQL Script
Fixed bug in SQLAzureMWBatchUpload to check for server type in upload process.

v3.9.1 & v4.0.4

Modified code to not rely on SMO for target server.

v3.9 & v4.0.3

Fixed a bug in character counting (look for CrLf or Cr)

v3.8.9 & v4.0.2

Fixed a bug with identifying comments in SQL to avoid false positives. The major impact of this was on parsing SQL text files.

v3.8.8 & v4.0.1

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.

Released: SQLAzureMW v3.9.12 and v4.0.15 (May 04, 2013)

Sat, 04 May 2013 12:52: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
小朱 (Jeff Chu) - Chinese Traditional (Taiwan)

Added the capability of doing a search and replace of a sub string found within the rules engine. For example, you have SELECT col1, col2 FROM Employees (NOLOCK) and now you want to replace "(" with "WITH (" so that the results would be SELECT col1, col2 FROM Employees WITH (NOLOCK). Look for XML property "SearchReplace" in NotSupportedByAzureFile.config to see an example.

v3.9.11 & v4.0.14

Added dependency checker to see if Microsoft.SqlServer.Smo and Microsoft.ExceptionMessageBox are on the machine SQLAzureMW is being run on. The dependency information is stored in Dependencies.xml.

v3.9.10 & v4.0.13

Added rule in NotSupportedByAzureFile.Config to remove DATA_COMPRESSION from indexes.
Added BCP error handling to examine message to see if it is a warning in which case do nothing.

v3.9.9.1 & v4.0.12.1

Modified SQLAzureMW to allow you to specify a default collation.

v3.9.9 & v4.0.12

No real bug fixes in this release, but I found that WinForms differs from Windows 7 vs. Windows 8. So, I rebuilt the application on the Windows 8 OS and now the fonts look better for Windows 8 and still seem to run on Windows 7. If you have any font issues, let me know.

v3.9.8 & v4.0.11

SQL Azure Migration Wizard is proud to announce its seventh translation into an international language: Chinese Traditional (Taiwan)! 小朱 (Jeff Chu) did all of the translation work to Chinese Traditional (Taiwan) and deserves all of the credit.

v3.9.7 & v4.0.10

Fixed bug where ALTER TABLE statements did not go through compatibility checker and parser.

v3.9.6.1 & v4.0.9.1 SQLAzureMWBatchBackup

Added the capability to select which database objects you want to backup. To specify which objects to backup, you will need to edit the ObjectSelector.xml file. Inside of that file is documentation on how it works.

v3.9.6 & v4.0.9

Fixed code to handle an empty string password.

v3.9.5 & v4.0.8

Fixed code to take all table constraints and move it to the end of generated script.

v3.9.4 & v4.0.7

Fixed BCP output commands to put quotes around password

v3.9.3 & v4.0.6

Changed some SQL Azure to SQL Database
Fixed BCPArgs parsing to remove need for special character checking

v3.9.2 & v4.0.5

Modified script to move all foreign key constraints to end of TSQL Script
Fixed bug in SQLAzureMWBatchUpload to check for server type in upload process.

v3.9.1 & v4.0.4

Modified code to not rely on SMO for target server.

v3.9 & v4.0.3

Fixed a bug in character counting (look for CrLf or Cr)

v3.8.9 & v4.0.2

Fixed a bug with identifying comments in SQL to avoid false positives. The major impact of this was on parsing SQL text files.

v3.8.8 & v4.0.1

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.

New Post: v4.0.15 source

paulhuck — Sat, 04 May 2013 00:52:18 GMT

Is the source code for the v4 edition available?
The Source Code and downloads pages only seem to have the v3.9 edition.

Thanks!

Reviewed: SQLAzureMW v3.9.12 and v4.0.15 (May 01, 2013)

dmiser — Wed, 01 May 2013 22:35:58 GMT

Rated 5 Stars (out of 5) - Worked perfectly. Added cluster indexes and cleaned up the aspnet_Membership error automatically. Literally 5 minutes to convert my local DB to Azure. Wonderful job!

Reviewed: SQLAzureMW v3.9.12 and v4.0.15 (May 01, 2013)

robdavey555 — Wed, 01 May 2013 18:06:31 GMT

Rated 5 Stars (out of 5) - All worked first time getting from SQL2008 to Azure. Took about 5 minutes.

New Post: dependencies for SQLAzureMW are missing . Version 3.9.12

Kwilksys — Wed, 01 May 2013 10:33:37 GMT

hi

I have use the wrong version for sql 2012 and it is now working fine.

Thanks

New Post: dependencies for SQLAzureMW are missing . Version 3.9.12

Kwilksys — Wed, 01 May 2013 10:29:22 GMT

hi,

I have downloaded the latest version on windows 8 . Have unzip and tried to run it but
got an error .

"MicrosoftExceptionMessagesBox, Version = 10.0.0.0, Culture = neutral,
PublicKeyToken=89845dcd8080cc91 or one of its dependencies. The system cannot find the file specified.
I have installed SQL 2012 full version.
Strange it seem I can run on my windows 7 with sql 2008 installed

Appreciate any assistance on this.
Regards

Commented Issue: Unable to install SQL Database Migration Wizard v3.9.12 & v4.0.15 [7392]

Duality — Tue, 30 Apr 2013 08:40:05 GMT

I am having problems installing the SQL Database Migration Wizard v3.9.12 & v4.0.15
I am trying to install it in Windows 2008 R2 server,
I get an error
"Sorry,but dependencies for SQLAzureMW are missing"
Error message = Could not load file or assembly
"Microsoft.ExceptionMessageBox, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified

What am i doing wrong?

Thanks
Comments: ** Comment from web user: Duality **

Ah, yes, I was using v3.9.12, using v4.0.15 now and it works without any changes required. Thanks.

Commented Issue: Unable to install SQL Database Migration Wizard v3.9.12 & v4.0.15 [7392]

ghuey — Mon, 29 Apr 2013 15:56:25 GMT

Are you running SQLAzureMW v4.0.15? That version is built for SQL Server 2012 and it has the dependency.xml file setup for version 11 like you posted. If you are running SQLAzureMW v3.9.12, then the dependency.xml file is for SQL Server 2008 R2 SP1.

I am glad you are up and running.

Regards,
George

Commented Issue: Unable to install SQL Database Migration Wizard v3.9.12 & v4.0.15 [7392]

Duality — Fri, 26 Apr 2013 16:04:02 GMT

If you have SQL Server 2012, as I do, the reference I have is v11.
So I changed the file to:
<Dependency>
<Assembly>Microsoft.ExceptionMessageBox, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91</Assembly>
<Type>Microsoft.SqlServer.MessageBox.ExceptionMessageBox</Type>
</Dependency>
And it works.
So this is a bug.

Commented Issue: Unable to install SQL Database Migration Wizard v3.9.12 & v4.0.15 [7392]

ghuey — Wed, 10 Apr 2013 01:22:31 GMT

Hi,

SQLAzureMW required SQL Server 2008 R2 SP1 or greater. When SQLAzureMW runs, it looks for the the assemblies that it needs to run. It looks like you are running SQLAzureMW 3.9.12 right? It also looks like you might have part of SQL Server 2008 R2 SP1 installed, but for some reason, Microsoft.ExceptionMessageBox is missing. If you want to try something, edit Dependency.xml and remove this:

<Dependency>
<Assembly>Microsoft.ExceptionMessageBox, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91</Assembly>
<Type>Microsoft.SqlServer.MessageBox.ExceptionMessageBox</Type>
</Dependency>

And try to run. You might be able to get buy without that (I don't really know, but what the heck, it is worth a try) if you don't get any errors, but it is needed to if the program finds a problem it wants to report. If that does not work, then you need to install ... I believe the client tools, but not for sure.

Regards,
George

Created Issue: Unable to install SQL Database Migration Wizard v3.9.12 & v4.0.15 [7392]

techranger — Tue, 09 Apr 2013 22:24:20 GMT

Updated Release: SQLAzureMW v3.9.12 and v4.0.15 (Apr 08, 2013)

ghuey — Mon, 08 Apr 2013 19:19:16 GMT

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

Added the capability of doing a search and replace of a sub string found within the rules engine. For example, you have SELECT col1, col2 FROM Employees (NOLOCK) and now you want to replace "(" with "WITH (" so that the results would be SELECT col1, col2 FROM Employees WITH (NOLOCK). Look for XML property "SearchReplace" in NotSupportedByAzureFile.config to see an example.

v3.9.11 & v4.0.14

Added dependency checker to see if Microsoft.SqlServer.Smo and Microsoft.ExceptionMessageBox are on the machine SQLAzureMW is being run on. The dependency information is stored in Dependencies.xml.

v3.9.10 & v4.0.13

Added rule in NotSupportedByAzureFile.Config to remove DATA_COMPRESSION from indexes.
Added BCP error handling to examine message to see if it is a warning in which case do nothing.

v3.9.9.1 & v4.0.12.1

Modified SQLAzureMW to allow you to specify a default collation.

v3.9.9 & v4.0.12

No real bug fixes in this release, but I found that WinForms differs from Windows 7 vs. Windows 8. So, I rebuilt the application on the Windows 8 OS and now the fonts look better for Windows 8 and still seem to run on Windows 7. If you have any font issues, let me know.

v3.9.8 & v4.0.11

SQL Azure Migration Wizard is proud to announce its seventh translation into an international language: Chinese Traditional (Taiwan)! 小朱 (Jeff Chu) did all of the translation work to Chinese Traditional (Taiwan) and deserves all of the credit.

v3.9.7 & v4.0.10

Fixed bug where ALTER TABLE statements did not go through compatibility checker and parser.

v3.9.6.1 & v4.0.9.1 SQLAzureMWBatchBackup

Added the capability to select which database objects you want to backup. To specify which objects to backup, you will need to edit the ObjectSelector.xml file. Inside of that file is documentation on how it works.

v3.9.6 & v4.0.9

Fixed code to handle an empty string password.

v3.9.5 & v4.0.8

Fixed code to take all table constraints and move it to the end of generated script.

v3.9.4 & v4.0.7

Fixed BCP output commands to put quotes around password

v3.9.3 & v4.0.6

Changed some SQL Azure to SQL Database
Fixed BCPArgs parsing to remove need for special character checking

v3.9.2 & v4.0.5

Modified script to move all foreign key constraints to end of TSQL Script
Fixed bug in SQLAzureMWBatchUpload to check for server type in upload process.

v3.9.1 & v4.0.4

Modified code to not rely on SMO for target server.

v3.9 & v4.0.3

Fixed a bug in character counting (look for CrLf or Cr)

v3.8.9 & v4.0.2

Fixed a bug with identifying comments in SQL to avoid false positives. The major impact of this was on parsing SQL text files.

v3.8.8 & v4.0.1

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.

Released: SQLAzureMW v3.9.12 and v4.0.15 (Apr 08, 2013)

Mon, 08 Apr 2013 19:19:15 GMT

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

Added the capability of doing a search and replace of a sub string found within the rules engine. For example, you have SELECT col1, col2 FROM Employees (NOLOCK) and now you want to replace "(" with "WITH (" so that the results would be SELECT col1, col2 FROM Employees WITH (NOLOCK). Look for XML property "SearchReplace" in NotSupportedByAzureFile.config to see an example.

v3.9.11 & v4.0.14

Added dependency checker to see if Microsoft.SqlServer.Smo and Microsoft.ExceptionMessageBox are on the machine SQLAzureMW is being run on. The dependency information is stored in Dependencies.xml.

v3.9.10 & v4.0.13

Added rule in NotSupportedByAzureFile.Config to remove DATA_COMPRESSION from indexes.
Added BCP error handling to examine message to see if it is a warning in which case do nothing.

v3.9.9.1 & v4.0.12.1

Modified SQLAzureMW to allow you to specify a default collation.

v3.9.9 & v4.0.12

No real bug fixes in this release, but I found that WinForms differs from Windows 7 vs. Windows 8. So, I rebuilt the application on the Windows 8 OS and now the fonts look better for Windows 8 and still seem to run on Windows 7. If you have any font issues, let me know.

v3.9.8 & v4.0.11

SQL Azure Migration Wizard is proud to announce its seventh translation into an international language: Chinese Traditional (Taiwan)! 小朱 (Jeff Chu) did all of the translation work to Chinese Traditional (Taiwan) and deserves all of the credit.

v3.9.7 & v4.0.10

Fixed bug where ALTER TABLE statements did not go through compatibility checker and parser.

v3.9.6.1 & v4.0.9.1 SQLAzureMWBatchBackup

Added the capability to select which database objects you want to backup. To specify which objects to backup, you will need to edit the ObjectSelector.xml file. Inside of that file is documentation on how it works.

v3.9.6 & v4.0.9

Fixed code to handle an empty string password.

v3.9.5 & v4.0.8

Fixed code to take all table constraints and move it to the end of generated script.

v3.9.4 & v4.0.7

Fixed BCP output commands to put quotes around password

v3.9.3 & v4.0.6

Changed some SQL Azure to SQL Database
Fixed BCPArgs parsing to remove need for special character checking

v3.9.2 & v4.0.5

Modified script to move all foreign key constraints to end of TSQL Script
Fixed bug in SQLAzureMWBatchUpload to check for server type in upload process.

v3.9.1 & v4.0.4

Modified code to not rely on SMO for target server.

v3.9 & v4.0.3

Fixed a bug in character counting (look for CrLf or Cr)

v3.8.9 & v4.0.2

Fixed a bug with identifying comments in SQL to avoid false positives. The major impact of this was on parsing SQL text files.

v3.8.8 & v4.0.1

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.

New Post: migration error. SQL to Azure

mkariti — Thu, 04 Apr 2013 15:12:33 GMT

Hi George,
Tried to contact you via PM but not sure if you got it.
cheers
mkariti

New Post: migration error. SQL to Azure

ghuey — Thu, 04 Apr 2013 12:34:09 GMT

The last two lines are the output of a BCP upload, but not the end of the program. The very last line you should see is:

 Processing finished at 4/4/2013 7:25:54 AM -- UTC -> 4/4/2013 12:25:54 PM

Telling you that the process is finished. During the data upload process, I kick off several tabs for the parallel upload of data. Are all of the tabs gone except for the Results tab? Question for you. Would you mind if I see the SQL script that is generated during the export process? I would like to see if I can't figure out what is going on. I tried creating a database with different collation and I had no problem moving one of my test databases. What collation did you use? I can try that one as well.

Thanks for your time,
George

Source code checked in, #71496

ghuey — Thu, 04 Apr 2013 12:20:24 GMT

v3.9.11