Beginning Microsoft SQL Server 2008 ... - S3 Tech Training

Chapter 18: Getting Integrated with Integration Services
546
For now, leave the actual Data Source drop-down box as SQL Native Client — this is generally the preferred
method for accessing SQL Server. From there, set up your authentication information (I’ve used
Windows Authentication in the preceding example) and choose AdventureWorks2008 as your database.
You’re now ready to click Next, where you’ll see what is, at first glance, essentially the same dialog. This
time, however, we’re going to make a bit of a change in things. Change the Destination field to be Flat File
Destination and, as shown in Figure 18-4, the rest of the options change to something more suitable to a
file system–based destination instead of a table in our SQL Server.
Figure 18-4
As you can see, I’ve chosen to name my output file TextExport.csv, and filled out the other information
in a manner appropriate for a typical comma-delimited file.
Let me digress long enough to warn you to be very careful about using comma-delimited files. While
this is something of a “tried and true” method of exporting and importing data, consider your delimiter
very carefully; does your data potentially already have commas in it? What is that going to do to your
exported (or imported) data? Just something to keep in mind when deciding formats (if the choice is
yours — most of the time it won’t be).