Generating a BCP Utility Script for SQL Azure

6월 9, 2010에 게시됨

[This article was contributed by the SQL Azure team.]

If you are migrating tables from SQL Server to SQL Azure, one of the easiest ways is to use bcp utilityto draw data out of your SQL Server into a file and then move the data from the file to SQL Azure. However, it can be tedious to write all the bcp utility commands by hand, since bcp utility requires that you execute a single command for each table, moving one table’s worth of data at a time (Find about more about how to use bcp utility with SQL Azure in our early blog post). Would it not be nice to move all the tables with a single batch file? This article presents a Transact-SQL script that will create a batch file with all the bcp utility commands you need to move a whole database.


Before you run the script below:

  • You need to have already created the database schema on SQL Azure before you move files with bcp utility. You can do this using the Generate Script Wizard; see our previous blog post for more information.
  • The tables on the SQL Azure destination database should be empty, which means that you shouldn’t run the BCP utility batch file twice on the same destination database.
  • The script below runs in SQL Server Management Studio connected to the source SQL Server database. You will need to modify the variables at the top of the script to reflect your source SQL Server and destination SQL Azure server, before you execute the script.

The Transact-SQL script will generate the commands for a batch file using Transact-SQL PRINT statements. After executing the script, just copy the whole output to a file with a .bat extension. Once you have the batch file create you can run it from the command line to facilitate the move of your database.

Preserving Primary Keys

If you are using IDENTITY to generate the primary keys in your database, the bcp utility commands generated will preserve the numbering of your primary keys using the –E flag. However, the referential integrity of the foreign keys will not be checked when they are inserted. This was done so that rows could be inserted regardless of the dependencies amongst the tables – primary keys do not need to be inserted before foreign keys.

Because the primary keys are not regenerated there should not be any constraints violated as long as the source database is not written too while the batch file is running. Here lies the hitch, you need to make sure that your source database is either in read only mode, or that no application is writing data to it. The bcp utility commands are not wrapped inside a big transaction. There can be significant time between the time the first command in the batch file is executed and the last, this gives an opportunity for the data writes.

The Script

SET NOCOUNT ON    DECLARE @DestServer nvarchar(max)  DECLARE @DestDatabase nvarchar(max)  DECLARE @DestLogin nvarchar(max)  DECLARE @DestPassword nvarchar(max)    DECLARE @SrcServer nvarchar(max)  DECLARE @SrcDatabase nvarchar(max)  DECLARE @SrcLogin nvarchar(max)  DECLARE @SrcPassword nvarchar(max)    -- SQL Azure Server  SET        @DestServer = ''  SET        @DestDatabase = 'yourDatabase'  SET        @DestLogin = 'yourLogin@yourServer'  SET        @DestPassword = 'yourPassword'    -- SQL Server  SET        @SrcServer = 'yourServer'  SET        @SrcDatabase = 'yourDatabase'  SET        @SrcLogin = 'yourLogin'  SET        @SrcPassword = 'yourPassword'    PRINT 'echo %DATE% %TIME% > bcp.log'  PRINT ''    ---------------------------------------------------    DECLARE @Schema nvarchar(max)  DECLARE @Table nvarchar(max)    DECLARE table_cursor CURSOR FOR      SELECT TABLE_SCHEMA, TABLE_NAME      FROM information_schema.tables       WHERE Table_Type = 'BASE TABLE'      OPEN table_cursor;    -- Perform the first fetch.  FETCH NEXT FROM table_cursor INTO @Schema, @Table;    -- Check @@FETCH_STATUS to see if there are any  -- more rows to fetch.  WHILE @@FETCH_STATUS = 0  BEGIN        PRINT 'REM Download ' + @Schema + '.' + @Table      PRINT 'echo bcp.exe ' + @SrcDatabase + '.' + @Schema + '.' +          @Table + ' out ' +           @Schema + '.' + @Table + '.bcp -q -h "TABLOCK" -N -CRAW -S' +          @SrcServer + ' >> bcp.log'      PRINT 'bcp.exe ' + @SrcDatabase + '.' + @Schema + '.' + @Table +           ' out ' + @Schema + '.' + @Table +           '.bcp -q -h "TABLOCK" -N -CRAW -S' + @SrcServer +           ' -U' + @SrcLogin + ' -P' + @SrcPassword + ' >> bcp.log'      PRINT ''        PRINT 'REM Upload ' + @Schema + '.' + @Table      PRINT 'echo bcp.exe ' + @DestDatabase + '.' + @Schema + '.' +           @Table + ' in ' + @Schema + '.' + @Table +           '.bcp -q -h "TABLOCK" -N -E -CRAW -S' + @DestServer +          ' >> bcp.log'      PRINT 'bcp.exe ' + @DestDatabase + '.' + @Schema + '.' +           @Table + ' in ' + @Schema + '.' + @Table +            '.bcp -q -h "TABLOCK" -N -E -CRAW -S' + @DestServer +            ' -U' + @DestLogin + ' -P' + @DestPassword + ' >> bcp.log'      PRINT ''           -- This is executed as long as the previous fetch succeeds.     FETCH NEXT FROM table_cursor  INTO @Schema, @Table;  END    CLOSE table_cursor;  DEALLOCATE table_cursor;


Do you have questions, concerns, comments? Post them below and we will try to address them.