SQLAzureMWBatchUpload

Feb 9 at 9:00 PM
I want to migrate RDS backed up data with SQLAzureMW (in TSQL format ) to SQL server and have to automate it .
So decided to use SQLAzureBatchUpload . If run the command without changing anything in config I get this :
__If you want, you can override the config file by specifying the parameters you
ant to override.
usage: SQLAzureMWBatchUpload -S server -U username -P password -D Northwind -d
rue -s 1

[-S target server name]
[-U username]
[-P password]
[-D target database name]
[-c database collation]
[-i TSQL input file]
[-o output file]
[-e Edition (web or business)
[-s database size in GBs (web = 1 or 5) (business = 10, 20, 30, 40, 50, 100 or
50)]
[-T trusted connection]
[-d {true or false} drop existing database]

Note that the above args override the values in the application config file.


If I change the config file I get this :

Signature error
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: sqlazuremwbatchupload.exe
Problem Signature 02: 4.0.18.0
Problem Signature 03: 53304ac8
Problem Signature 04: System.Xml
Problem Signature 05: 4.0.30319.18058
Problem Signature 06: 51e9d22a
Problem Signature 07: 9af
Problem Signature 08: 0
Problem Signature 09: IOIBMURHYNRXKW0ZXKYRVFN0BOYYUFOW
OS Version: 6.2.9200.2.0.0.272.7
Locale ID: 1033
Additional Information 1: 36ff
Additional Information 2: 36ff0865562c1311fc215a1413b3482f
Additional Information 3: 8aaa
Additional Information 4: 8aaa1b8c9a8b3be03d0f6edfc88bde2c
  • I am using SQLserver 2012 Enterprise
  • SQLAZureMW v4.0.18 release Binary for SQL SErver 2012
  • SQLAzureMWBatchUpload v4.0.18
    *.net version 4
    Here is the command I use :
    SQLAzureMWBatchUpload -S cgswsql02\cgswsql02A -D TestSQLAZURE -i C:\SQLAzureMW\BCPData\Cornerstonebackup.sql -T true
  • TestSQLAzure DB is already created in SQL server
Thanks,
Coordinator
Feb 14 at 1:52 AM
Hi,

Just out of curiosity, if you specify everything in the command line, does SQLAzureMWBatchUpload work ok? Is it only when you modify the config file that it does not work? Another question is could you try v4.15.6? and last question is what nodes did you change in the config file? I want to try to reproduce the issue you found on my machine.

Thanks,
George