When saving a deployment script produced by SQL Comparison SDK, you may want to save the script for later use by the ADO .NET client (SqlCommand). Since the script produced using SQL Toolkit's BlockSaver class in meant for SQL Server Management Studio, it includes batch separators (GO commands) that aren't understood by ADO .NET and will cause errors when run for this reason.

It is possible to save the SQL Toolkit ExecutionBlock in a way where batch markers are not included in the script by looping through the individual batches and saving only batches that are not marked as a batch marker. Here is an example code snippet which assumes that you have already populated an ExecutionBlock called "block":

  using (System.IO.StreamWriter sw=new System.IO.StreamWriter(@"c:\temp\test.sql"))
	{
		for (int i = 0; i < block.batchcount;="">
		{
			Batch b = block.GetBatch(i);
			if (b.Marker == false)
			{
				sw.Write(b.Contents + "\r\n");
			}
		}
	}

Please note that you may want to use the NoSqlPlumbing option as well when you create the ExecutionBlock to prevent transactional operations from appearing in the script. ADO .NET has its own methods for rolling back and committing transactions if necessary.

work.BuildFromDifferences(stagingVsProduction, Options.Default | Options.NoSQLPlumbing, true);