RequirementsSQLAzureMW 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.
IssuesIf 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)
SourceVisual 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.