17.06.2013 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Executing the Package<br />

If you simply click Execute in the Package Execution Utility, your package will be off and running. After<br />

it runs, you should find a text file in whatever location you told your package to store it; open it up, take<br />

a look, and verify that it was what you expected.<br />

Executing Using the <strong>SQL</strong> <strong>Server</strong> Agent<br />

We haven’t really discussed the <strong>SQL</strong> <strong>Server</strong> Agent up to this point, but, from an SSIS point of view, think<br />

of the <strong>SQL</strong> <strong>Server</strong> Agent as a job scheduler that allows you to do the same thing as running DTExec.exe,<br />

but doing so on a specific time and frequency basis with very robust job and task scheduling systems to<br />

integrate your package into a larger set of system jobs.<br />

We will discuss the agent in a bit more detail in our next chapter.<br />

Executing a Package from Within a Program<br />

<strong>SQL</strong> <strong>Server</strong> offers a very rich object model that is usable from within any .NET language. The programmability<br />

object model is well beyond the scope of this book, but suffice to say that you can not only programmatically<br />

execute packages, but dynamically build packages to meet a certain need before executing them.<br />

A Final Word on Packages<br />

I want to take a moment and reiterate how much we’ve really only touched the surface of what’s possible.<br />

As I’ve said before, there are entire books (rather large ones actually) written around Integration Services<br />

as the sole topic.<br />

The package we focused on here was generated by the Import/Export Wizard, but the end product was<br />

a typical SSIS package. Not only could we edit it, but we could well have built it from scratch ourselves.<br />

We could easily add other tasks to deal with things like “scrubbing” data after importing it to some form<br />

of “staging” area and then perform additional tasks. We can add complex branching to deal with errors<br />

or perform several tasks in parallel; the possibilities go on and on.<br />

Summary<br />

Chapter 18: Getting Integrated with Integration Services<br />

<strong>SQL</strong> <strong>Server</strong> Integration Services is a robust Extract, Transform, and Load tool. You can utilize Integration<br />

Services to provide one-off or repeated import and export of data to and from your databases — mixing<br />

a variety of data sources while you’re at it.<br />

While becoming expert in all that Integration Services has to offer is a positively huge undertaking, getting<br />

basic imports and exports up and running is a relative piece of cake. I encourage you to start out<br />

simple, and then add to it as you go. As you push yourself further and further with what SSIS can do,<br />

take a look at other books that are specific to what SSIS has to offer.<br />

561

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!