NET application, would you stuff all of your code into one master function called RunItAll()? How about mashing together unrelated subroutines into a single 2000 line T-SQL stored procedure? As you mature in your development experience I’ll bet you separate code functionality into manageable chunks of views, stored procedures and triggers. And if you’re not a developer at all, think about a warm happy place while I take this short journey into an architecture discussion. To understand this, think about object oriented programming or distributed SQL development. But that first relies on a definition of SSIS scalability. In this article I will take some leaps forward and introduce some steps to create more scalable packages. A particularly good starting point can be found on TechNet in a tutorial series, “Creating a Simple ETL Package Tutorial” ( ). For some good primers, check out SQL Books Online, the samples included with your SQL Server 2005 installation and Microsoft TechNet. We will assume that you have some experience, however slight, with SSIS. SSIS Package Componentization: One Package to Rule Them All!įirst let me be clear, this is not a beginners primer to SSIS (SQL Server Integration Services). SSIS Package Componentization - Simple Talk Skip to content
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |