Integration Services (SSIS)

External Article

SQL Server 2005 - SQL Server Integration Services - Part 6

  • Article

In this article, we are continuing coverage of Foreach Loop container functionality, by discussing different types of loop enumerators. So far, we have presented methods for working with files in a folder as well as records in a recordset (using Foreach File and Foreach ADO enumerators, respectively). Our next enumerator is based on the SQL Server Management Objects technology (hence it is referred to as the SMO enumerator), which is the SQL Server 2005, .NET-based management framework providing replacement for COM-based DMO (Distributed Management Objects) that served an equivalent role in earlier versions of SQL Server.

2005-08-22

2,338 reads

External Article

SQL Server Integration Services - Part 5

  • Article

We will continue our review of Foreach enumerators starting with Foreach ADO, since this one probably qualifies as the most popular choice in its category. This is due to the fact that ADO recordsets offer a convenient way of dealing with data sources, regardless of their type (for example, within SSIS, you can easily populate a recordset by executing a SQL query or by reading the content of a flat file)

2005-08-01

1,791 reads

SQLServerCentral Article

Portable DTS Packages

  • Article

Moving DTS Packages from one SQL Server 2000 server to another can be a real hassle. There are any number of issues that occur whenever you seek to use a package on different servers. New author Jonathan Stokes brings us a technique he's used many times to build portable DTS packages.

You rated this post out of 5. Change rating

2005-07-25

11,535 reads

Technical Article

Shredding a Recordset

  • Article

Shredding a recordset in this instance means that we are going to show you how to take a recordset produced in your SSIS package, loop over the rows in that recordset, break apart the columns and do something with them. This is really useful when you want to preform an action on a row of data for every row of data just like we are going to do here. Sure we could use an ExecuteSQL task to get the recordset as well but that does limit our choices of source data whereas doing it in the pipeline does not. Something useful we hope.

2005-06-21

2,103 reads

Technical Article

Reproduced with kind permission from the blog of Ashvini Sharma (MSFT)

  • Article

InfoPath forms can be saved to XML, these XML Files can later be used in SSIS XMLSource adapter to pull out the data in tables and columns. However, there are some common problems you may meet in these scenarios. This article describes how to work around these potential problems. The issues mentioned in this article is not only specific to InfoPath files, it can also be referenced in other similar situations as well.

2005-06-20

1,328 reads

Blogs

“We love to debate minutiae”

By

I am guilty as charged. The quote was in reference to how people argue...

Advice I Like: Knots

By

Learn how to tie a bowline knot. Practice in the dark. With one hand....

Shifting Mindsets: Why FinOps is Essential for Cloud Efficiency

By

As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...

Read the latest Blogs

Forums

Windows logins for users migrated from DomainA to DomainB

By a.koopman

Hi, I have a SQL Server instance where users connect to via Windows Authentication,...

Multiple Deployment Processes

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Multiple Deployment Processes

How to Use sqlpackage to Detect Schema Drift Between Azure SQL Databases

By Kunal Rathi

Comments posted to this topic are about the item How to Use sqlpackage to...

Visit the forum

Question of the Day

Upgrading Admin Queries

I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?  

See possible answers