SQL Azure Migration Wizard v3.8.2

Source code checked in, #67616

ghuey — Fri, 03 Feb 2012 22:04:52 GMT

Fixed code to call IsTargetServerFederation()

New Post: Error: Index was outside the bounds of the array

kokujin — Thu, 02 Feb 2012 11:09:29 GMT

Hello

This does not work for me. I've had my DB Admins update our test database to SP1, and I still get the error. I've tried only one table schema and it fails, any more ideas?

[edit] Reading the solutions more carefully, I think I need to update Management Studio as well... going to do that now and report back.

[edit2]Yep, I had to update my own installation of SQL Server (which in turn updates SSMS). All working now!

Patch Uploaded: #11370

richardastbury — Tue, 31 Jan 2012 11:12:22 GMT

richardastbury has uploaded a patch.

Description:
If the password contains an equals character, it must be escaped with an preceding equals character. (i.e. = -> ==).

New Post: SQLAzureMWBatchUpload Parameter DropOldDatabaseIfExists

chriseull — Mon, 30 Jan 2012 14:27:33 GMT

Hello George,
The missing SpecialTableCharacters key was the issue. I was reusing my config file from before.

Thank you for looking into this.
Chris

New Post: Migration wizard error

ghuey — Sun, 29 Jan 2012 23:43:38 GMT

Hi,

I just wanted to check back with you and see if you got things running.

Regards,

George

New Post: Error: Index was outside the bounds of the array

ghuey — Fri, 27 Jan 2012 21:48:54 GMT

Thanks!!!

Reviewed: SQL Azure Migration Wizard v3.8.2 (gen 27, 2012)

delfo — Fri, 27 Jan 2012 13:22:59 GMT

Rated 5 Stars (out of 5) - This is a great product very simple and usefull !!! Microsoft's guy should learn how to do jobs like this in this simple and usefull !!

New Post: Error: Index was outside the bounds of the array

delfo — Fri, 27 Jan 2012 13:21:02 GMT

Thanks a lot.

after upgrading all works fine.

You have made a great product very simple and usefull !!!

New Post: Error: Index was outside the bounds of the array

ghuey — Fri, 27 Jan 2012 12:03:08 GMT

The issue you described below is that SQL Azure requires applications using SMO to be running on SQL Server 2008 R2 SP1. In July, SQL Azure upgraded the servers (for more info see: http://blogs.msdn.com/b/windowsazure/archive/2011/07/13/announcing-sql-azure-july-2011-service-release.aspx). These changes require that any program using SMO run on SQL Server 2008 R2 SP1. So, you need to download SP1 and you should be ok. You can download SQL Server 2008 R2 SP1 here: http://www.microsoft.com/download/en/details.aspx?id=26727.

Regards,

George

New Post: Error: Index was outside the bounds of the array

delfo — Fri, 27 Jan 2012 10:10:44 GMT

Hi,

i have installed and run the wizard and all works fine until i reach the phase where, after insert all data for connecting to a SQL Azure server the application try to retrieve the database list.

I get this error:

Index was outside the bounds of the array (Microsoft.SqlServer.Smo)

What can i do ??

Thanks

PS:
I Have SSMS 2008R2 and a local Sql 2008 R2 database

New Post: SQLAzureMWBatchUpload Parameter DropOldDatabaseIfExists

ghuey — Fri, 27 Jan 2012 03:20:26 GMT

Hi Chris,

Just out of curiosity, did you save off your old SQLAzureMWBatchUpdate.exe.config file and use it over the new one? I tried and tried to reproduce the issue that you were talking about and failed until I removed this line from the new config file:

If you used your old config file, then this key is missing and it caused the exact error you mentioned. Anyway, can you check and if it is not in your config file, please add it and see what happens?

I don’t like this section of my code and it has caused me a lot of problems. I will have to rethink what I am doing here. But I wanted to see if this was the cause of your problem.

As a side note, I noticed that your BCPArgs at the bottom of the script were like this:

-- BCPArgs::[dbo].[Menus] in "dummydb.Menus.dat" -E -n -b 10000 -a 16384 -o "dummydb.Import.Menus.log"

I was actually surprised that my code worked with that. The reason is that there is no value between the first two ::

It should look more like this:

-- BCPArgs:128942:[dbo].[Menus] in "dummydb.Menus.dat" -E -n -b 10000 -a 16384 -o "dummydb.Import.Menus.log"

Where the 128942 is replaced with the number of records in your .dat file. I use that number to determine the number of loops I need to make when chunking the data (see ChunkSize in config file). I also use this number to verify that the number of records uploaded was the number of records expected. I guess the number of rows you are uploading are smaller than the ChunkSize so it works. Anyway, if you know the number of records in the bcp dat file, it should go in place of 128942.

Let me know if adding the SpecialTableCharacters key to the config file works for you. I am traveling for the next week so my response will only be at night (sorry if I am slow in responding).

Thanks,

George

New Post: SQLAzureMWBatchUpload Parameter DropOldDatabaseIfExists

chriseull — Thu, 26 Jan 2012 17:42:59 GMT

George,

That was fast!
I tried 3.8.2 and I am getting an error (see script and output below). I haven't tried adding the "-d false" to my command line yet.
When I switch back to 3.8.1 (exe & dll) everything runs fine.
It seems to be when the program gets to the 1st bcp line in my sql file.

Thank you,
chris

Command Line

".\SQLAzureMWBatchUpload.exe" -i "ContentMenuSet.Import.sql" -o ".\ContentMenuSet.Import.log" -S server.database.windows.net -U username@server -P password -D databasename

Script

DELETE FROM [dbo].[ViewMenuItems]
GO

DELETE FROM [dbo].[SubMenuItems]
GO

DELETE FROM [dbo].[ConfigMenuItems]
GO

DELETE FROM [dbo].[MenuItems]
GO

DELETE FROM [dbo].[Menus]
GO

-- BCPArgs::[dbo].[Menus] in "dummydb.Menus.dat" -E -n -b 10000 -a 16384 -o "dummydb.Import.Menus.log"
GO

-- BCPArgs::[dbo].[MenuItems] in "dummydb.MenuItems.dat" -E -n -b 10000 -a 16384 -o "dummydb.Import.MenuItems.log"
GO

-- BCPArgs::[dbo].[ConfigMenuItems] in "dummydb.ConfigMenuItems.dat" -E -n -b 10000 -a 16384 -o "dummydb.Import.ConfigMenuItems.log"
GO

-- BCPArgs::[dbo].[SubMenuItems] in "dummydb.SubMenuItems.dat" -E -n -b 10000 -a 16384 -o "dummydb.Import.SubMenuItems.log"
GO

-- BCPArgs::[dbo].[ViewMenuItems] in "dummydb.ViewMenuItems.dat" -E -n -b 10000 -a 16384 -o "dummydb.Import.ViewMenuItems.log"
GO

Output

SQLAzureMWBatchUpload, Version 3.8.2.0
Process started at 1/26/2012 11:20:25 AM -- UTC -> 1/26/2012 5:20:25 PM ...
-- Success: DELETE FROM [dbo].[ViewMenuItems]
-- Success: DELETE FROM [dbo].[SubMenuItems]
-- Success: DELETE FROM [dbo].[ConfigMenuItems]
-- Success: DELETE FROM [dbo].[MenuItems]
-- Success: DELETE FROM [dbo].[Menus]

Unhandled Exception: System.ArgumentOutOfRangeException: StartIndex cannot be less than zero.
Parameter name: startIndex
   at System.String.Remove(Int32 startIndex)
   at SQLAzureMWUtils.TargetProcessor.BCPUploadData(Server targetServer, String targetDatabase, AsyncUpdateStatus updateStatus, AsyncQueueBCPJob queueBCPJob, String bcpArgs, StringCollection& bcpUploadCommands)
   at SQLAzureMWUtils.TargetProcessor.ExecuteSQLonTarget(Server targetServer, String targetDatabase, String collation, String edition, Int32 dbSize, AsyncUpdateStatus updateStatus, AsyncQueueBCPJob queueBCPJob, String sqlToExecute, Boolean bDropDatabaseIfExists)
   at SQLAzureMWBatchUpload.Program.Process()
   at SQLAzureMWBatchUpload.Program.Main(String[] args)

New Post: Migration wizard error

ghuey — Thu, 26 Jan 2012 14:06:44 GMT

Hi,

Are you running version 3.8.2 or did you run into this with v3.8.1?

Also, were you able to connect to SQL Azure ok and create a database? Was it the BCP process or just before?

Thanks for your time,

George

New Post: Migration wizard error

ProjectMala — Thu, 26 Jan 2012 13:24:03 GMT

The migration wizard gets almost to the end and then puts up an error saying:-

Connection failed

SQL State 37000

SQL Server Error 40531

Server name cannot be determined

Commented Issue: Tables with an ! crash Azure MW when BCP'ing data into SQL Azure [6726]

ghuey — Thu, 26 Jan 2012 03:34:06 GMT

We recently had an issue with migrating a client's database to SQL Azure for an acceleration lab. The database had ~230 tables and kept crashing at some point in the BCP process.

We eventually tracked it down to a table that had the name something like dbo.DELETEME!_OLDTABLENAME

(Don't get me started on what this was doing in the database, but...)

It would seem that a table that has an exclamation mark in it crashes the Azure MW with an unhandled index out side or bounds exception. This ob course makes it pretty hard to track down what triggered the problem.
Comments: ** Comment from web user: ghuey **

Hi, it is amazing the table names that people come up with . I have ran into this before and I had the regex check string hardcoded. So, I finally moved the regex string that checks for valid table characters and moved it to the app config file. Basically, I need to discover [schema].[table] from the BCP command and I have to create a regex string that returns
[schema] and [table] is two matches. Anyway, I added ! to the regex string and moved the string to the config file. Look for the key “SpecialTableCharacters” in the config file if you find another exception that needs to be added.

Check out v3.8.2 and let me know if it does not work for you.

Thanks for the catch!
George

New Post: SQLAzureMWBatchUpload Parameter DropOldDatabaseIfExists

ghuey — Thu, 26 Jan 2012 03:27:20 GMT

Hi,

Now there is. I modified the command parameter to be “-d { true | false }”. If you don’t specify –d, then I use value specified in the config file. Please check out v3.8.2 and see if it works for you.

Thanks for the catch,

George

Updated Release: SQL Azure Migration Wizard v3.8.2 (Jan 25, 2012)

ghuey — Thu, 26 Jan 2012 03:21:49 GMT

Requirements
SQL Azure Migration Wizard v3x requires SQL Server 2008 R2 SP1 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.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: SQL Azure Migration Wizard v3.8.2 (Jan 25, 2012)

Thu, 26 Jan 2012 03:21:49 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.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!

Source code checked in, #67424

ghuey — Thu, 26 Jan 2012 03:05:32 GMT

Moved check for valid table characters to app.config file. key name=SpecialTableCharacters Fixed bug in SQLAzureMWBatchUpload to allow override of dropping database

New Post: SQLAzureMWBatchUpload Parameter DropOldDatabaseIfExists

chriseull — Wed, 25 Jan 2012 20:01:28 GMT

Is there a way with the command line parameter to override the config file setting DropOldDatabaseIfExists if the option is already set to true in the file?
It appears that the -d parameter only turns on the option.