Integration Services (SSIS)

SQLServerCentral Article

How to use OUTPUT clause result in SSIS 2005 / 2008 (RC0)

  • Article

The OUTPUT clause was a new feature in SQL Server 2005 that can prove very handy in many situations. New author Gennadiy Chornenkyy brings us a look at how you can add this code to your SSIS packages and retrieve ID values back from the database.

4.27 (11)

You rated this post out of 5. Change rating

2008-08-18

9,465 reads

Technical Article

Trash Destination Adapter

  • Article

The Trash Destination and this article came from early experiences of using SSIS and community feedback at the time. When developing a package it is very useful to have a destination adapter that does nothing but consume rows with no setup requirement. You often want run a package part way through development, or just add a path so you can set a Data Viewer.

2008-05-29

1,183 reads

Blogs

Creating a Striped Backup Set with AI

By

I needed to test a striped backup, so I decided to ask the AI’s...

Trace Flag 1448 – Lessons from a Technical Interview

By

In SQL Server environments where transactional replication runs alongside Always On Availability Groups (AGs),...

Disable the sa login in SQL Server (and sleep better)

By

Disable the sa login in SQL Server (and sleep better)If you run SQL Server...

Read the latest Blogs

Forums

Create an HTML Report on the Status of SQL Server Agent Jobs

By Nisarg Upadhyay

Comments posted to this topic are about the item Create an HTML Report on...

SQLPS and syspolicy_purge_history job

By schleep

The SQLPS.exe file has gone AWOL on 2 of my 4 SQL servers, ie,...

Be Wary of Data

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Be Wary of Data

Visit the forum

Question of the Day

Locking Hierarchies

You have a table [dbo].[orders] without a Clustered Index (Heap). The table does not have any other nonclustered indexes! You rund the following command in Read Committed Isolation Level:

SELECTo_orderdate,
        o_orderkey,
        o_custkey,
        o_storekey
FROMdbo.orders
WHEREo_orderkey = 3877;

What locking hierarchy will Microsoft SQL Server use?

 

See possible answers