Database Reference
In-Depth Information
Figure 11.85
Configuring the custom workload driver.
A known issue that we must address is the way the .csv and .txt files are created and
their failure to import into SQL Server 2012 (SQL Server 2008 too). The reason for this
is when the configuration files are created, an extra carriage return is present in the file
and this causes the import into SQL to fail. By running the files through a conversion
utility to remove these returns, we fix the issue. This is what the next section addresses.
To fix this issue, we need to run .txt and .csv files through a Unix-to-DOS conversion
utility. The utility we used was a free-to-use tool located at
http://www.efgh.com/software/unix2dos.htm
.
As of the writing of this chapter, the
author has placed no restrictions on its use. Download and run unix2dos.exe by dragging
and dropping .txt and .csv files onto it. This must be done starting at the ds2 folder level
and all files in this hierarchy. Missing a file could result in the SQL load failing.
Tip
Copy the executable into each directory and leave it there; that way, you know
which directories you have completed. In addition, sort files by
Type
, highlight
all the .csv and .txt files, and then drag and drop them onto the executable. Use the
Date Modified
column to verify all files have been converted.
Note
Not all .txt files need to be run through the conversion utility (for example,
Read Me documentation), but we just have to be on the safe side.
