By: Greg Robidoux | Last Updated: 2006-09-28 | Comments (5) | XML
One very common process that occurs in most SQL Server environments is the need to import and export data. With SQL Server 7.0 and 2000 we had DTS (Data Transformation Services) and now with SQL Server 2005 we have SSIS (SQL Server Integration Services). These are great GUI environments and give you a lot of flexibility to move data in and out of SQL Server. In addition to these GUI tools there is the tried and true BCP (Bulk Copy Program) that has been around for a lot longer then DTS or SSIS.
Even though this tool has been around quite some time, there are always enhancements and with SQL Server 2005 additional enhancements have been added as well. One of the features of BCP is to create a format file that defines the data that is coming into SQL Server and where it should go during the import process. With SQL Server 2005 an enhancement has been made so this format file can either be the standard format or in an XML format.
Creating a format file for bcp is not new to SQL Server 2005 and these files can be created using older versions as well as with SQL Server 2005. This can be done by using a command similar to the following, which creates a format file based on the structure of the Categories table in the Northwind database.
bcp Northwind.dbo.Categories format nul -c -f categories.fmt -T -S servername
This creates a standard format file that can then be edited to handle differences in your source and destination formats. When you run this command, this is the output you get. For additional information take a look at books online.
1 SQLCHAR 0 12 "\t" 1 CategoryID ""
2 SQLCHAR 0 30 "\t" 2 CategoryName SQL_Latin1_General_CP1_CI_AS
3 SQLCHAR 0 0 "\t" 3 Description SQL_Latin1_General_CP1_CI_AS
4 SQLCHAR 0 0 "\r\n" 4 Picture ""
In order to create an XML version of the format file the command is identical except we use the -x parameter.
bcp AdventureWorks.HumanResources.Department format nul -c -x -f department.xml -T -S servername
This is the output from running the above command. Instead of having a simple text file we now have an XML file that is easier to understand as well as easier to modify.
<BCPFORMAT xmlns="http://schemas.microsoft.com/sqlserver/2004/bulkload/format" xmlns:xsi="http:// www.w3.org/2001/XMLSchema-instance">
<FIELD ID="1" xsi:type="CharFixed" LENGTH="7"/>
<FIELD ID="2" xsi:type="CharFixed" LENGTH="100"COLLATION="Latin1_General_CS_AS"/>
<FIELD ID="3" xsi:type="CharFixed" LENGTH="100"COLLATION="Latin1_General_CS_AS"/>
<FIELD ID="4" xsi:type="CharTerm" TERMINATOR="\r\n"MAX_LENGTH="24"/>
<COLUMN SOURCE="1" NAME="DepartmentID" xsi:type="SQLSMALLINT"/>
<COLUMN SOURCE="2" NAME="Name" xsi:type="SQLNVARCHAR"/>
<COLUMN SOURCE="3" NAME="GroupName" xsi:type="SQLNVARCHAR"/>
<COLUMN SOURCE="4" NAME="ModifiedDate" xsi:type="SQLDATETIME"/>
Other then how to create and modify the format files, the rest of BCP still works the same. So you would still reference your format file just as before. The -x option is only used when creating the format file.
- Take a look at understanding the XML schema syntax
- Take a look at how BCP works and how this could be an addition to your processing if you are not already using BCP
- Take a look at how to create a format file and other options for creating a format file
Last Updated: 2006-09-28
About the author
View all my tips