MSFTDPProdSamples Wiki & Documentation Rss Feed

New Comment on "SS2008!Readme_Displaying Column and Catalog Metadata for Sparse Columns (OLE DB)"

ollio — Tue, 31 May 2011 11:52:34 GMT

For 'Considerations for Installing SQL Server Samples and Sample Databases' I found that link http://msdn.microsoft.com/en-us/library/ms161556.aspx What would be microsoft without Google?

New Comment on "SS2008!Readme_Displaying Column and Catalog Metadata for Sparse Columns (OLE DB)"

ollio — Tue, 31 May 2011 11:51:00 GMT

Hint, I should look at: 'Considerations for Installing SQL Server Samples and Sample Databases', but I don't get a clue nor a link, where to find that information. Bad marketing..

New Comment on "SS2008!Readme_Displaying Column and Catalog Metadata for Sparse Columns (OLE DB)"

ollio — Tue, 31 May 2011 11:48:27 GMT

This installation is idot. Now clue in which path the installation goes, nor about the names of any files installed. Pure Rubbish, poor quality.

Updated Wiki: Home

bonniefe — Tue, 08 Dec 2009 23:49:24 GMT

SQL Server Samples Portal Page > SQL Server Data Programming Product Samples

This project contains Data Programming samples released with Microsoft SQL Server product. These samples are in the following five categories: ADO, ODBC, and OLEDB. If you are interested in contributing Data Programming samples, please let us know by posting in the developers' forum.

To download these samples click on the Releases tab (or click here), optionally select another (older) release, then click on the Windows Installer package (MSI file) which matches the architecture of the installation computer.

For information about how to use CodePlex to access SQL Server samples, click here.
To download samples databases, click here and then click the appropriate MSI file.
For release notes and brief descriptions of all the sample databases and code, including restrictions on SQL Express and Vista, click here.

ADO.NET

Sample	SQL Server 2005	SQL Server 2008 & SQL Server 2008R2
Large Binary Object (LOB) Handling using ADO.Net	SS2005	n/a
MARS	SS2005	n/a

ODBC

Sample	SQL Server 2005	SQL Server 2008 & SQL Server 2008R2
BulkCopyFormatAndData	SS2005	SS2008
How to bulk copy a SELECT result set (ODBC)	SS2005	SS2008
How to bulk copy data from program variables (ODBC)	SS2005	SS2008
How to bulk copy without a format file (ODBC)	SS2005	SS2008
How to create a bulk copy format file (ODBC)	SS2005	SS2008
How to log long-running queries (ODBC)	SS2005	SS2008
How to process ODBC errors (ODBC)	SS2005	SS2008
How to process return codes and output parameters (ODBC)	SS2005	SS2008
How to profile driver performance data (ODBC)	SS2005	SS2008
ODBC Table-Valued Parameters	n/a	SS2008
UseDataAtExecutionColumns	SS2005	SS2008
UseDataAtExecutionParameters	SS2005	SS2008
ODBC Date Time	n/a	SS2008
ODBC_SparseCols	n/a	SS2008

OLE DB

Sample	SQL Server 2005	SQL Server 2008 & SQL Server 2008R2
Enhanced Date/Time Features in SQL Server 2008	n/a	SS2008
Execute stored procedure (using ODBC CALL syntax) and process return codes and output parameters (OLE DB)	SS2005	SS2008
Execute stored procedure (using RPC syntax) and process return codes and output parameters (OLE DB)	SS2005	SS2008
Execute user-defined function and process return code (OLE DB)	SS2005	SS2008
Fetching Columns Using IRow::GetColumns (OLE DB)	SS2005	SS2008
Fetching Columns Using IRow::GetColumns (or IRow::Open) and ISequentialStream	SS2005	SS2008
How to bulk copy data using IRowsetFastLoad (OLE DB)	SS2005	SS2008
How to enumerate OLE DB data sources (OLE DB)	SS2005	SS2008
How to fetch rows from a result set (OLE DB)	SS2005	SS2008
How to obtain FAST_FORWARD cursor	SS2005	SS2008
How to retrieve rows using bookmarks (OLE DB)	SS2005	SS2008
How to set large data (OLE DB)	SS2005	SS2008
Read filestream column to file using IBCPSession (OLE DB)	n/a	SS2008
Retrieve data from Filestream column using ISequentialStream (OLE DB)	n/a	SS2008
Send data to a filestream column using ISequentialStream bound to ICommandText parameter (OLE DB)	n/a	SS2008
Use IRowsetFastUpload interface to send data to a filestream column (OLE DB)	n/a	SS2008
Changing a SQL Server Authentication User Password (OLE DB)	n/a	SS2008
Displaying Column and Catalog Metadata for Sparse Columns (OLE DB)	n/a	SS2008
Integrated Kerberos Authentication Sample (OLE DB)	n/a	SS2008
Sending BLOB Data to SQL SERVER Using IROWSETFASTLOAD and ISEQUENTIALSTREAM	n/a	SS2008
Table-Valued Parameters	n/a	SS2008

Programmability

Sample	SQL Server 2005	SQL Server 2008 & SQL Server 2008R2
Change Data Capture for Specified Interval Package Sample	n/a	SS2008
Change Data Capture since Last Request Package	n/a	SS2008
Large UDT (OLEDB)	n/a	SS2008
Large UDT ODBC	n/a	SS2008
ODBC Spatial Storage	n/a	SS2008

Got questions? Want to contribute? Check out the SQL Server Community & Samples Discussion Forum!

Updated Wiki: SS2008!ODBC Spatial Storage

bonniefe — Sat, 14 Feb 2009 01:24:50 GMT

Readme for Spatial Storage

February 13, 2009

This sample works only with SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2008.
This sample inserts two rows into a table with a geography column from a WellKnownBinary (WKB) using 2 different bindings (SQLCCHAR and SQLCBINARY). Then it selects one row from that table and uses ::STAsText() to display it.
The WKB is 0x01010000000700ECFAD03A4C4001008000B5DF07C0 and the application prints to the console: POINT(56.4595 -2.9842).
This sample does not require an ODBC data source, but the sample runs, by default, on the local instance of SQL Server.
SQL Server samples and sample databases must be downloaded and installed before you can view or work with them. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.

Scenario

For more information about spatial storage, see Designing and Implementing Spatial Storage in SQL Server Books Online.

Languages

This sample uses Visual C++.

Prerequisites

Before running this sample, make sure that the following software is installed:

SQL Server or SQL Server Express, including Database Engine. You can download SQL Server Express from the Microsoft Download Center.
The SQL Server Database Engine samples that are available at the Microsoft SQL Server Developer Center.
.NET Framework SDK 2.0 (or later) or Microsoft Visual Studio 2005 (or later). You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework Documentation.
The source code for this sample. Click on the Releases tab above then click on either the appropriate installer for the computer you are using or click on the zip file for any machine architecture.

Building the Sample

This sample connects to your computer's default SQL Server instance. To connect to a non-default instance, change the Server attribute in odbc_spatial.cpp.
The sample requires you to execute the following Transact-SQL statements, which you can find in the sample's scripts directory

USE tempdb
GO
 
IF EXISTS (SELECT name FROM sysobjects WHERE name = 'SpatialSample')
   DROP TABLE SpatialSample
 
CREATE TABLE SpatialSample (Name varchar(10), Geog Geography)
GO

In SQL Server Management Studio, load and execute the Scripts\setup.sql script or execute the following command in a Command Prompt window:

sqlcmd -E -I -i Scripts\setup.sql

If you are using Visual Studio, load the odbc_spatial.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe at a command prompt, passing it the odbc_spatial.sln file:

MSBuild odbc_spatial.sln

Running the Sample

From Visual Studio, invoke Start Without Debugging (CTRL+F5).
If you built with MSBuild.exe, invoke odbc_spatial.exe. The sample outputs the following: POINT(56.4595 -2.9842).

Updated Wiki: SS2008!ODBC Spatial Storage

bonniefe — Sat, 14 Feb 2009 01:22:30 GMT

Readme for Spatial Storage

Scenario

For more information about spatial storage, see Designing and Implementing Spatial Storage in SQL Server Books Online.

Languages

This sample uses Visual C++.

Prerequisites

Before running this sample, make sure that the following software is installed:

SQL Server or SQL Server Express, including Database Engine. You can download SQL Server Express from the Microsoft Download Center.
The SQL Server Database Engine samples that are available at the Microsoft SQL Server Developer Center.
.NET Framework SDK 2.0 (or later) or Microsoft Visual Studio 2005 (or later). You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework Documentation.

Building the Sample

This sample connects to your computer's default SQL Server instance. To connect to a non-default instance, change the Server attribute in odbc_spatial.cpp.
The sample requires you to execute the following Transact-SQL statements, which you can find in the sample's scripts directory

USE tempdb
GO
 
IF EXISTS (SELECT name FROM sysobjects WHERE name = 'SpatialSample')
   DROP TABLE SpatialSample
 
CREATE TABLE SpatialSample (Name varchar(10), Geog Geography)
GO

In SQL Server Management Studio, load and execute the Scripts\setup.sql script or execute the following command in a Command Prompt window:

sqlcmd -E -I -i Scripts\setup.sql

If you are using Visual Studio, load the odbc_spatial.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe at a command prompt, passing it the odbc_spatial.sln file:

MSBuild odbc_spatial.sln

Running the Sample

From Visual Studio, invoke Start Without Debugging (CTRL+F5).
If you built with MSBuild.exe, invoke odbc_spatial.exe. The sample outputs the following: POINT(56.4595 -2.9842).

Updated Wiki: SS2008!ODBC Spatial Storage

bonniefe — Sat, 14 Feb 2009 01:21:44 GMT

Readme for Spatial Storage

Scenario

For more information about spatial storage, see Designing and Implementing Spatial Storage in SQL Server Books Online.

Languages

This sample uses Visual C++.

Prerequisites

Before running this sample, make sure that the following software is installed:

SQL Server or SQL Server Express, including Database Engine. You can download SQL Server Express from the Microsoft Download Center.
The SQL Server Database Engine samples that are available at the Microsoft SQL Server Developer Center.
.NET Framework SDK 2.0 (or later) or Microsoft Visual Studio 2005 (or later). You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework Documentation.

Building the Sample

This sample connects to your computer's default SQL Server instance. To connect to a non-default instance, change the Server attribute in odbc_spatial.cpp.
The sample requires you to execute the following Transact-SQL statements, which you can find in the sample's scripts directory

 
USE tempdb
GO
 
IF EXISTS (SELECT name FROM sysobjects WHERE name = 'SpatialSample')
   DROP TABLE SpatialSample
 
CREATE TABLE SpatialSample (Name varchar(10), Geog Geography)
GO

In SQL Server Management Studio, load and execute the Scripts\setup.sql script or execute the following command in a Command Prompt window:

sqlcmd -E -I -i Scripts\setup.sql

If you are using Visual Studio, load the odbc_spatial.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe at a command prompt, passing it the odbc_spatial.sln file:

MSBuild odbc_spatial.sln

Running the Sample

From Visual Studio, invoke Start Without Debugging (CTRL+F5).
If you built with MSBuild.exe, invoke odbc_spatial.exe. The sample outputs the following: POINT(56.4595 -2.9842).

Updated Wiki: SS2008!ODBC Spatial Storage

bonniefe — Sat, 14 Feb 2009 01:20:34 GMT

Readme for Spatial Storage

Scenario

For more information about spatial storage, see Designing and Implementing Spatial Storage in SQL Server Books Online.

Languages

This sample uses Visual C++.

Prerequisites

Before running this sample, make sure that the following software is installed:

SQL Server or SQL Server Express, including Database Engine. You can download SQL Server Express from the Microsoft Download Center.
The SQL Server Database Engine samples that are available at the Microsoft SQL Server Developer Center.
.NET Framework SDK 2.0 (or later) or Microsoft Visual Studio 2005 (or later). You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework Documentation.

Building the Sample

This sample connects to your computer's default SQL Server instance. To connect to a non-default instance, change the Server attribute in odbc_spatial.cpp.
The sample requires you to execute the following Transact-SQL statements, which you can find in the sample's scripts directory

 
USE tempdb
GO
 
IF EXISTS (SELECT name FROM sysobjects WHERE name = 'SpatialSample')
   DROP TABLE SpatialSample
 
CREATE TABLE SpatialSample (Name varchar(10), Geog Geography)
GO

In SQL Server Management Studio, load and execute the Scripts\setup.sql script or execute the following command in a Command Prompt window:

sqlcmd -E -I -i Scripts\setup.sql

If you are using Visual Studio, load the odbc_spatial.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe at a command prompt, passing it the odbc_spatial.sln file:

MSBuild odbc_spatial.sln

Running the Sample

From Visual Studio, invoke Start Without Debugging (CTRL+F5).
If you built with MSBuild.exe, invoke odbc_spatial.exe. The sample outputs the following: POINT(56.4595 -2.9842).

Updated Wiki: SS2008!ODBC Spatial Storage

bonniefe — Sat, 14 Feb 2009 01:20:02 GMT

ReadmeSpatialStorage

Scenario

For more information about spatial storage, see Designing and Implementing Spatial Storage in SQL Server Books Online.

Languages

This sample uses Visual C++.

Prerequisites

Before running this sample, make sure that the following software is installed:

SQL Server or SQL Server Express, including Database Engine. You can download SQL Server Express from the Microsoft Download Center.
The SQL Server Database Engine samples that are available at the Microsoft SQL Server Developer Center.
.NET Framework SDK 2.0 (or later) or Microsoft Visual Studio 2005 (or later). You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework Documentation.

Building the Sample

This sample connects to your computer's default SQL Server instance. To connect to a non-default instance, change the Server attribute in odbc_spatial.cpp.
The sample requires you to execute the following Transact-SQL statements, which you can find in the sample's scripts directory

 
USE tempdb
GO
 
IF EXISTS (SELECT name FROM sysobjects WHERE name = 'SpatialSample')
   DROP TABLE SpatialSample
 
CREATE TABLE SpatialSample (Name varchar(10), Geog Geography)
GO

In SQL Server Management Studio, load and execute the Scripts\setup.sql script or execute the following command in a Command Prompt window:

sqlcmd -E -I -i Scripts\setup.sql

If you are using Visual Studio, load the odbc_spatial.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe at a command prompt, passing it the odbc_spatial.sln file:

MSBuild odbc_spatial.sln

Running the Sample

From Visual Studio, invoke Start Without Debugging (CTRL+F5).
If you built with MSBuild.exe, invoke odbc_spatial.exe. The sample outputs the following: POINT(56.4595 -2.9842).

Updated Wiki: Home

ReedMe — Thu, 29 Jan 2009 23:02:02 GMT

ADO.NET

Sample	SQL Server 2005	SQL Server 2008
Large Binary Object (LOB) Handling using ADO.Net	SS2005	n/a
MARS	SS2005	n/a

ODBC

Sample	SQL Server 2005	SQL Server 2008
BulkCopyFormatAndData	SS2005	SS2008
How to bulk copy a SELECT result set (ODBC)	SS2005	SS2008
How to bulk copy data from program variables (ODBC)	SS2005	SS2008
How to bulk copy without a format file (ODBC)	SS2005	SS2008
How to create a bulk copy format file (ODBC)	SS2005	SS2008
How to log long-running queries (ODBC)	SS2005	SS2008
How to process ODBC errors (ODBC)	SS2005	SS2008
How to process return codes and output parameters (ODBC)	SS2005	SS2008
How to profile driver performance data (ODBC)	SS2005	SS2008
ODBC Table-Valued Parameters	n/a	SS2008
UseDataAtExecutionColumns	SS2005	SS2008
UseDataAtExecutionParameters	SS2005	SS2008
ODBC Date Time	n/a	SS2008
ODBC_SparseCols	n/a	SS2008

OLE DB

Sample	SQL Server 2005	SQL Server 2008
Enhanced Date/Time Features in SQL Server 2008	n/a	SS2008
Execute stored procedure (using ODBC CALL syntax) and process return codes and output parameters (OLE DB)	SS2005	SS2008
Execute stored procedure (using RPC syntax) and process return codes and output parameters (OLE DB)	SS2005	SS2008
Execute user-defined function and process return code (OLE DB)	SS2005	SS2008
Fetching Columns Using IRow::GetColumns (OLE DB)	SS2005	SS2008
Fetching Columns Using IRow::GetColumns (or IRow::Open) and ISequentialStream	SS2005	SS2008
How to bulk copy data using IRowsetFastLoad (OLE DB)	SS2005	SS2008
How to enumerate OLE DB data sources (OLE DB)	SS2005	SS2008
How to fetch rows from a result set (OLE DB)	SS2005	SS2008
How to obtain FAST_FORWARD cursor	SS2005	SS2008
How to retrieve rows using bookmarks (OLE DB)	SS2005	SS2008
How to set large data (OLE DB)	SS2005	SS2008
Read filestream column to file using IBCPSession (OLE DB)	n/a	SS2008
Retrieve data from Filestream column using ISequentialStream (OLE DB)	n/a	SS2008
Send data to a filestream column using ISequentialStream bound to ICommandText parameter (OLE DB)	n/a	SS2008
Use IRowsetFastUpload interface to send data to a filestream column (OLE DB)	n/a	SS2008
Changing a SQL Server Authentication User Password (OLE DB)	n/a	SS2008
Displaying Column and Catalog Metadata for Sparse Columns (OLE DB)	n/a	SS2008
Integrated Kerberos Authentication Sample (OLE DB)	n/a	SS2008
Sending BLOB Data to SQL SERVER Using IROWSETFASTLOAD and ISEQUENTIALSTREAM	n/a	SS2008
Table-Valued Parameters	n/a	SS2008

Programmability

Sample	SQL Server 2005	SQL Server 2008
Change Data Capture for Specified Interval Package Sample	n/a	SS2008
Change Data Capture since Last Request Package	n/a	SS2008
Large UDT (OLEDB)	n/a	SS2008
Large UDT ODBC	n/a	SS2008
ODBC Spatial Storage	n/a	SS2008

Got questions? Want to contribute? Check out the SQL Server Community & Samples Discussion Forum!

Updated Wiki: SS2008!ODBC Spatial Storage

bonniefe — Thu, 06 Nov 2008 23:03:43 GMT

ReadmeSpatialStorage

11/05/2008 21:36:06

This sample works only with SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2008.
This sample inserts two rows into a table with a geography column from a WellKnownBinary (WKB) using 2 different bindings (SQLCCHAR and SQLCBINARY). Then it selects one row from that table and uses ::STAsText() to display it.
The WKB is 0x01010000000700ECFAD03A4C4001008000B5DF07C0 and the application prints to the console: POINT(56.4595 -2.9842).
This sample does not require an ODBC data source, but the sample runs, by default, on the local instance of SQL Server.
SQL Server samples and sample databases must be downloaded and installed before you can view or work with them. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.

Scenario

For more information about spatial storage, see Designing and Implementing Spatial Storage in SQL Server Books Online.

Languages

This sample uses Visual C++.

Prerequisites

Before running this sample, make sure that the following software is installed:

SQL Server or SQL Server Express, including Database Engine. You can download SQL Server Express from the Microsoft Download Center.
The SQL Server Database Engine samples that are available at the Microsoft SQL Server Developer Center.
.NET Framework SDK 2.0 (or later) or Microsoft Visual Studio 2005 (or later). You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework Documentation.

Building the Sample

This sample connects to your computer's default SQL Server instance. To connect to a non-default instance, change the Server attribute in odbc_spatial.cpp.
The sample requires you to execute the following Transact-SQL statements, which you can find in the sample's scripts directory: * {" use tempdb

GO

IF EXISTS (SELECT name FROM sysobjects WHERE name = 'SpatialSample')
DROP TABLE SpatialSample

CREATE TABLE SpatialSample (Name varchar(10), Geog Geography)
GO "}* In SQL Server Management Studio, load and execute the Scripts\setup.sql script or execute the following command in a Command Prompt window: * sqlcmd -E -I -i Scripts\setup.sql *

If you are using Visual Studio, load the odbc_spatial.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe at a command prompt, passing it the odbc_spatial.sln file: * MSBuild odbc_spatial.sln *

Running the Sample

From Visual Studio, invoke Start Without Debugging (CTRL+F5).
If you built with MSBuild.exe, invoke odbc_spatial.exe. The sample outputs the following: POINT(56.4595 -2.9842).

Updated Wiki: SS2008!Readme Large UDT ODBC

bonniefe — Thu, 06 Nov 2008 23:03:28 GMT

ReadmeLargeUDT_ODBC

11/05/2008 21:36:06

This sample works only with SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2008.
This sample solution contains two projects. One project creates an assembly (DLL) from C# source code. This assembly contains the CLR type. A table will be added to the database. A column in the table will be of a type defined in the assembly, By default, this sample will use the master database. The second project is a native C++ application that reads data from the table.
SQL Server samples and sample databases must be downloaded and installed before you can view or work with them. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.

Scenario

For more information about large UDTs, see Large CLR User-Defined Types (ODBC) in SQL Server Books Online.

Languages

This sample uses Visual C++.

Prerequisites

Before running this sample, make sure the following software is installed:

SQL Server or SQL Server Express, including the Database Engine. You can download SQL Server Express from the Microsoft Download Center.
The SQL Server Database Engine samples that are available at the Microsoft SQL Server Developer Center.
The .NET Framework SDK 2.0 (or later) or Microsoft Visual Studio 2005 (or later). You can obtain the .NET Framework SDK free of charge. For more information, see Installing the .NET Framework Documentation.

Building the Sample

Build this sample as follows:

Build the C# project (LargeStringUDT). This project creates a DLL. The project has a post-build event that copies the DLL to the root directory of your C:\ drive. If your C:\ drive is not available when you run this sample, modify the post-build event to use a different drive.
Run the following Transact-SQL script: * {" USE [MASTER]

GO

CREATE ASSEMBLY LargeStringUDT
FROM 'C:\LargeStringUDT.dll'
WITh PERMISSION_SET=SAFE;
GO

CREATE TYPE dbo.LargeStringUDT
EXTERNAL NAME LargeStringUDT.LargeStringUDT;
GO

CREATE TABLE dbo.LargeStringUDTs
(ID int IDENTITY(1,1) PRIMARY KEY, LargeString LargeStringUDT)
GO

INSERT INTO dbo.LargeStringUDTs (LargeString) VALUES (CONVERT(LargeStringUDT, 'This is the first string'));
INSERT INTO dbo.LargeStringUDTs (LargeString) VALUES (CONVERT(LargeStringUDT, 'This is the second string'));
INSERT INTO dbo.LargeStringUDTs (LargeString) VALUES (Convert(LargeStringUDT, 'This is the third string'));
GO "}* This script references the DLL created by the C# project. So, if you modified the post-build event to change the directory location of the DLL, also modify this script.

Build the C++ project (FetchRowsWithLargeUDTTypes).

Running the Sample

From Visual Studio, invoke Start Without Debugging (CTRLF5) on the C+ project.
If you built with MSBuild.exe, invoke FetchRowsWithLargeUDTTypes.exe.

Updated Wiki: SS2008!Large UDT (OLEDB)

bonniefe — Thu, 06 Nov 2008 23:03:14 GMT

ReadmeLargeUDT_OLEDB

Scenario

For more information about large UDTs, see Large CLR User-Defined Types (OLE DB) in SQL Server Books Online.

Languages

This sample uses Visual C++.

Prerequisites

Before running this sample, make sure the following software is installed:

SQL Server or SQL Server Express, including the Database Engine. You can download SQL Server Express from the Microsoft Download Center.
The SQL Server Database Engine samples that are available at the Microsoft SQL Server Developer Center.
The .NET Framework SDK 2.0 (or later) or Microsoft Visual Studio 2005 (or later). You can obtain the .NET Framework SDK free of charge. For more information, see Installing the .NET Framework Documentation.

Building the Sample

Build this sample as follows:

Build the C# project (LargeStringUDT). This project creates a DLL. The project has a post-build event that copies the DLL to the root directory of your C:\ drive. If your C:\ drive is not available when you run this sample, modify the post-build event to use a different drive.
Run the following Transact-SQL script: * {" USE [MASTER]

Build the C++ project (FetchRowsWithLargeUDTTypes).

Running the Sample

From Visual Studio, invoke Start Without Debugging (CTRLF5) on the C+ project.
If you built with MSBuild.exe, invoke FetchRowsWithLargeUDTTypes.exe.

Updated Wiki: SS2008!Readme Change Data Capture since Last Request Package

bonniefe — Thu, 06 Nov 2008 23:02:56 GMT

Readme_Change Data Capture for Specified Interval Package Sample

11/05/2008 21:36:06

Note:
This sample works only with SQL Server 2008 Enterprise and SQL Server 2008 Developer. This sample will not work with any version of SQL Server earlier than SQL Server 2008, or on any edition other than SQL Server 2008 Enterprise or SQL Server 2008 Developer.

This sample illustrates how to incorporate change data capture technology into an extraction, transformation, and loading (ETL) process that uses Integration Services. This sample is a complete end-to-end sample that includes both workload generation and the initial load of target tables as part of the sample setup. After the initial load finishes, the master package runs periodically, gathers the changes that have occurred since the last request, and then updates the target replicas to reflect those changes.
The source database is the AdventureWorks2008 database. This sample uses existing tables in the AdventureWorks2008 database to populate comparable destination tables in the CDCSample schema in the AdventureWorksDW2008 database.

Note:
This sample uses datetime values to specify the range for the change data capture functions that request change data. To see how to use log sequence numbers (LSNs) to specify the query range when you query for change data, see Readme_Change Data Capture since Last Request Package Sample.

Important:
Samples are provided for educational purposes only. They are not intended to be used in a production environment and have not been tested in a production environment. Microsoft does not provide technical support for these samples.

Requirements

To run this sample package, the following requirements must be met:

The sample package and data files that the sample uses must be installed on the local hard disk drive. You can download the sample from Microsoft SQL Server Product Samples: Integration Services.
You must have installed and have administrative permissions on the AdventureWorks2008 OLTP and AdventureWorksDW2008 databases.
You must install SQL Server Database Engine to install support for the change data capture feature. You must also install Replication when you install SQL Server Database Engine.
If you intend only to run the sample from the command line, you must install Integration Services.
If you want to open and run the sample in SSIS Designer, you must install Business Intelligence Development Studio. For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.

Location of the Sample Files

This sample consists of the following files:

The solution file and Readme file.
The project files and packages.
The Transact-SQL script files.

Location of the Solution File and Readme File

The following folder is the default location of the solution file and Readme file for this sample:
<drive>:\Program Files\Microsoft SQL Server\100\Samples\Integration Services\Package Samples\Change Data Capture for Specified Interval Package Sample\
The following table provides the complete name and a short description of the files in this folder.

File	Description
Change Data Capture in Integration Services Sample.sln	The solution file for this sample.
Readme_ChangeDataCaptureforSpecifiedIntervalPackageSample.htm	The Readme file for this sample.

Location of the Project Files and Packages

The following folder is the default location of the project files and packages for this sample:
<drive>:\Program Files\Microsoft SQL Server\100\Samples\Integration Services\Package Samples\Change Data Capture for Specified Interval Package Sample\Change Data Capture in Integration Services Sample\
The following table provides the complete name and a short description of the files in this folder.

File	Description
Change Data Capture in Integration Services Sample.dtproj	The project file for this sample.

| SetupCDCSample.dtsx| The setup package and sample test harness.

Note:
If you did not install this sample to the default location, you will have to modify the package variables, SQLServerInstallPath and BasePath , to correspond to the appropriate installation path. The default value of the SQLServerInstallPath package variable is <drive>:\Program Files\Microsoft SQL Server\. The value of the BasePath package variable derives from the value of the SQLServerInstallPath package variable.

Note:

If you did not install this sample to the default location, you will have to modify the package variables, SQLServerInstallPath and BasePath , to correspond to the appropriate installation path. The default value of the SQLServerInstallPath package variable is <drive>:\Program Files\Microsoft SQL Server\. The value of the BasePath package variable derives from the value of the SQLServerInstallPath package variable.

MasterCDC.dtsx	The master package that performs an incremental load cycle.
CDCCustomerExtract.dtsx	The child package that gathers the changes to the Customer table for the extraction interval, and then applies those changes to the destination.
CDCCreditCardExtract.dtsx	The child package that gathers the changes to the CreditCard table for the extraction interval, and then applies those changes to the destination.
CDCWorkOrderExtract.dtsx	The child package that gathers the changes to the WorkOrder table for the extraction interval, and then applies those changes to the destination.

Location of the Transact-SQL Script Files

The following folder is the default location of the Transact-SQL script files for this sample:
<drive>:\Program Files\Microsoft SQL Server\100\Samples\Integration Services\Package Samples\Change Data Capture for Specified Interval Package Sample\Change Data Capture in Integration Services Sample\Scripts\
The following table provides the complete name and a short description of the files in this folder.

File	Description
CDCSetupTables.sql	The sample setup file.
CDCCustomerInsert.sql	The script that applies Inserts to the CDCSample.Customer table.
CDCCustomerModify.sql	The script that applies Updates to the CDCSample.Customer table.
CDCCreditCardInsert.sql	The script that applies Inserts to the CDCSample.CreditCard table.
CDCCreditCardModify.sql	The script that applies Updates to the CDCSample.CreditCard table.
CDCWorkOrderInsert.sql	The script that applies Inserts to the CDCSample.WorkOrder table.
CDCWOrkOrderModify.sql	The script that applies Updates to the CDCSample.WorkOrder table.

Running the Sample

To run the package, you can use either the dtexec command prompt utility (dtexec.exe) or BI Development Studio.
To run the package by using the dtexec utility Open a Command Prompt window.Use the Change Directory command, cd, to change the directory that contains the dtexec utility.The default location of the dtexec utility is <drive>:\Program Files\Microsoft SQL Server\100\DTS\Binn.At the command prompt, type the following command: dtexec /f "C:\Program Files\Microsoft SQL Server\100\Samples\Integration Services\Package Samples\Change Data Capture for Specified Interval Package Sample\Change Data Capture in Integration Services Sample\SetupCDCSample.dtsx"Press ENTER.For more information about how to use the dtexec utility run a package, see the topic, "dtexec Utility," in SQL Server Books Online. To run the package in Business Intelligence Development Studio In BI Development Studio, on the File menu, point to Open, and then click Project/Solution.For Files of type, select Integration Services Project Files (.dtproj). Then, locate the Change Data Capture for Specified Interval Package Sample* folder, and double-click the file, Change Data Capture in Integration Services Sample.dtproj.In Solution Explorer, in the SSIS Packages folder, right-click SetupCDCSample.dtsx, and then click Execute Package.

Sample Packages and Their Components

The sample consists of five packages:
The setup package—SetupCDCSampleThe setup package acts as a test harness for the sample. As a test harness, this package does the following processes: Performs all the required initialization. This includes creating a database snapshot. Generates a data manipulation language (DML) workload against the source tables while cycling the master package to perform an incremental load of the target tables for a given time period. Monitors the progress of the run, and stops the sample after all the DML workload has been processed and applied to the destination tables. Validates, at the end of the run, the content of the destination tables. The setup package compares the destination tables with the content of the source tables, and then records the results in the event log. The master package—MasterCDCThe master package performs an incremental load of the target tables for the interval provided as input. To determine whether to continue with the incremental load, the master package checks the endpoints of the interval: If both endpoints for the extraction interval are in range, the master package starts the three child packages, which perform the incremental loads for the individual tables. If the high endpoint of the interval is outside the interval, the master package delays processing. This enables the capture process to catch up. If the low endpoint is outside the interval where change data exists for a source table, the master package logs an error and stops the sample.After all the child packages have finished running, the master package logs a message to the event log that indicates the sample has finished for the interval. The master package then stops the sample. Three child packages—Extract Customer Data, Extract CreditCard Data and Extract WorkOrder DataThe structure of each of these child packages is identical: Each child package first creates the query that extracts the changed data. Then, the child package runs a data flow task that performs the incremental load of the changed data. The data flow task uses information in the result set that the query returns to split the returned rows. The data flow splits the rows into three distinct flows—insert, update, or delete—that correspond to the operation required to apply the row to the destination. The data flow task then runs the tasks that handle the various flows. The following sections describe the components found in each package.

SetupCDCSample Package Components

The SetupCDCSample package has several annotated functional groups:

Initialize Environment and Enable Change Data Capture
Generate Workload
Perform Initial Load for Target Tables
Prepare for Initial Extraction
Extract and Process Change Data
Validate Incremental Load and Report Run Status These groups help organize the content as described in the following sections.

Note:
To view the annotated functional groups, open the SetupCDCSample package in Business Intelligence Development Studio. To see a larger view of the package, click the four-way arrow in the lower-right corner of the Control Flow tab, and then position the view window over the package.

Initialize Environment and Enable Change Data Capture

This functional group contains a single Execute SQL task. The purpose of this task is to do the following:

Create the sample source tables from existing AdventureWorks2008 tables, and then enable change data capture for these tables.
Create the target tables in the AdventureWorks2008DW database.
Instantiate the change data capture wrapper functions, and the special functions that run during the initial extraction period. The following table lists the task that this functional group uses.

Name	Element	Purpose

| Create Tables and Enable Change Data Capture| Execute SQL task| Creates the sample source tables from existing AdventureWorks2008 tables:

Checks for any objects that were created in previous runs of the sample, and deletes these objects, if present.
Enables the AdventureWorks2008 database for change data capture.
Creates the CDCSample schema.
Creates the tables, CDCSample.Customer, CDCSample.CreditCard, and CDCSample.WorkOrder, in the CDCSample schema. (These tables mirror the comparable tables in the dbo schema.)
Creates two helper procedures, generate_wrappers and HexStrToVarbin. Creates the target tables in the AdventureWorks2008DW database :
Checks for any objects that were created in previous runs of the sample, and then deletes these objects, if present.
Creates the CDCSample schema.
Creates the target tables, Customer, CreditCard, and WorkOrder, in the CDCSample schema.
Initializes the tables, CDCSample.Customer, CDCSample.CreditCard, and CDCSample.WorkOrder, with a subset of the table data from their parent AdventureWorks2008 tables.
Enables change data capture on the parent AdventureWorks2008 tables. Instantiates datetime wrapper functions that query for change data.Defines customer wrapper functions that synchronize the first extraction interval to the initial load. |

Generate Workload

This functional group contains six Execute SQL tasks and a Script task:

Each of the three source tables has two Execute SQL tasks: one that generates insert activity against the table and one that generates update activity. Three of the six Execute SQL tasks run after change data capture has been enabled on the source tables. The remaining three run as each of the first three workload tasks finishes.
When all the Execute SQL tasks have run, the Script task runs. The Script task sets the package variables that indicate that the workload has finished. The following table lists the tasks that this functional group uses.

Name	Element	Purpose
Insert Customer Table	Execute SQL task	Applies inserts to the AdventureWorks2008.CDCSample.Customer table.
Modify Customer Table	Execute SQL task	Applies updates to the AdventureWorks2008.CDCSample.Customer table.
Insert CreditCard Table	Execute SQL task	Applies inserts to the AdventureWorks2008.CDCSample.CreditCard table.
Modify CreditCard Table	Execute SQL task	Applies updates to the AdventureWorks2008.CDCSample.CreditCard table.
Insert WorkOrder Table	Execute SQL task	Applies inserts to the AdventureWorks2008.CDCSample.WorkOrder table.
Modify WorkOrder Table	Execute SQL task	Applies updates to the AdventureWorks2008.CDCSample.WorkOrder table.

| Mark Workload Completion| Script task| Sets the following package variables:

The WorkloadCompleted package variable that indicates whether the workload has finished.
The WorkloadEndTime package variable that indicates the time at which the workload finished. This task uses Visual Basic. |

Perform Initial Load for Target Tables

This functional group contains one Script task and three Data Flow tasks:

The Script task, Create Database Snapshot, creates a database snapshot of the AdventureWorks2008 database. This snapshot provides the source tables for the initial load of the target tables.
The three data flow tasks then extract data from the snapshot tables and apply this data to the destination tables in the AdventureWorksDW2008 database. The following table summarizes these tasks.

Name	Element	Purpose
Create Database Snapshot	Script task	Creates a database snapshot of the AdventureWorks2008 database.This task uses Visual Basic.
Load Target Customer Table From Snapshot	Data Flow task	Uses an OLE DB source to extract data from the snapshot table, CDCSample.Customer, and then uses an OLE DB destination to apply the rows to the table, AdventureWorksDW2008.CDCSample.Customer.
Load CreditCard Table From Snapshot	Data Flow task	Uses an OLE DB source to extract data from the snapshot table, CDCSample.CreditCard, and then uses an OLE DB destination to apply the rows to the table, AdventureWorksDW2008.CDCSample.CreditCard.
Load WorkOrder Table From Snapshot	Data Flow task	Uses an OLE DB source to extract data from the snapshot table, CDCSample.WorkOrder, and then uses an OLE DB destination to apply the rows to the table, AdventureWorksDW2008.CDCSample.WorkOrder.

Prepare for Initial Extraction

This functional group contains two Execute SQL tasks and one Script task:

The first Execute SQL task, Verify Capture Process is Started, runs after all the initial loads of the target tables. This task verifies that the change data capture process has auto-started.
The second Execute SQL task, Determine Datetime Base for Initial Extraction Interval, runs if the change data capture process has started. This task determines an initial datetime value that serves as the base for generating extraction intervals for the incremental loads to follow.
The Script task, Log Capture Not Started Message, runs if the process has not started. This task logs an error in the event log that indicates that SQL Server Agent must be running for the change data capture process to auto-start. This task also stops the package. The following table summarizes these tasks.

Name	Element	Purpose
Verify Capture Process is Started	Execute SQL task	Examines the table, AdventureWorks2008.cdc.lsntimemapping, to determine whether the capture process has started gathering changes from the transaction log, and then sets the CaptureStarted package variable accordingly.
Determine Datetime Base for Initial Extraction Interval	Execute SQL task	Extracts the last log sequence number (LSN) that is included in the database snapshot from snapshot metadata, and then sets the LastLSN package variable to this value. It then delays until the capture process has processed through LastLSN in the transaction log. The datetime value of the entry in the mapping table with the smallest LSN greater than LastLSN is then chosen as the datetime base for computing extraction intervals for the run.
Log Capture Not Started Message	Script task	Runs if the CaptureStarted package variable is set to 0, which indicates that the capture process did not auto-start. This task logs an appropriate error message in the event log.

Extract and Process Change Data

This functional group contains a For Loop container that includes two tasks:

A Script task that computes the next extraction interval.
An Execute Package task that runs the package that gathers the change data for the current interval and applies the data to the target tables. The For Loop container maintains the package variable, IntervalID . The For Loop container initializes the IntervalID package variable to 0, and then increments this variable by 1 on each iteration of the loop. The loop continues to run until the following conditions are true:

The WorkloadCompleted package variable is set to 1.
The start time for the next iteration exceeds the recorded value for the WorkloadEndTime package variable. The following table summarizes the components in this functional group.

Name	Element	Purpose
Cycle Master at 10 second intervals	For Loop container	Runs a Script task that computes the new extraction interval, and then runs the package that gathers changes for the interval and applies those changes to the target tables. The container stops processing when all the changes in the generated workload have been applied to the destination tables.

| Set Extract Interval| Script task| Sets the package variables that delimit the time interval for the next extraction interval:

The ExtractStartTime variable sets the low endpoint for the interval
The ExtractEndTime variable sets the high endpoint for the interval. To calculate the extraction interval, the task uses the value of the ExtractEndTime package variable from the previous interval to set the ExtractStartTime package variable for the current interval. The task then adds 10 seconds to the value of the new ExtractStartTime package variable, and sets the value of the ExtractEndTime package variable to this computed value. |

Run Master to Extract Data

Execute Package task

Runs the MasterCDC package applies the incremental load for a given extraction interval to the destination tables.

Validate Incremental Load and Report Run Status

This functional group contains an Execute SQL task and a Script task:

The Execute SQL task, Check for Mismatch in Replicas, uses SQL CHECKSUM to compare the source tables with the replicas and sets package variables that indicate the run status.
At the end of the run, the Script task, Output Run Completion Status, uses the package variables to report the results of the table comparisons in the event log. The following table summarizes these tasks.

Name	Element	Purpose
Check for Mismatch in Replicas	Execute SQL task	Uses CHECKSUM to compare the replicas to the source tables. Based on this comparison, the task then sets the package variables, CustomerMismatch , CreditCardMismatch , and WorkOrderMismatch , accordingly.
Output Run Completion Status	Script task	Outputs a status message to the event log at the end of the run. (This message reports on the parity of the package variables, CustomerMismatch , CreditCardMismatch , and WorkOrderMismatch .) Then, sets the run status accordingly.

MasterCDC Package Components

When the SetupCDCSample package runs, five package configurations of type, "Parent package variable", enable the SetupCDCSample package to pass package variables to the MasterCDC package. The following table lists these package variables.

Parent	Child
User::ExtractEndTime	ExtractEndTime
User::ExtractStartTime	ExtractStartTime
User::IntervalID	IntervalID
User::LastLSN	LastLSN
User::BasePath	BasePath

The following table lists the tasks, containers, data sources, data destinations, and transformations that the master package uses.

Name	Element	Purpose

| Wait for Capture Process to Process Extraction Interval| For Loop container| Contains the following components:

An Execute SQL task that sets a package variable that indicates the status of the proposed extraction interval relative to the capture process.
A Script task that delays processing if the high endpoint of the interval is outside the interval. This delay enables the capture process to catch up.
A Script task that runs on either of the following conditions:
The low endpoint of the interval predates the interval for which there is valid data.
After repeated delays, the capture process has not caught up. If either of these conditions is true, the task generates an entry in the error log, and causes the package to stop running. If the interval is valid, this container also starts the Execute Packages tasks that run the child packages that apply the change data to the destination tables.After the child packages complete, this container also runs a Script task that records that the extraction interval has finished in the event log. |

| Check for Data| Execute SQL task| Sets the DataReady package variable to one of the following values:

0 = Need to wait for capture process
1 = Start time predates validity interval
2 = Ready for data query ( interval > 1)
3 = Ready for first data query
5 = Timeout ceiling reached waiting for capture process (This task runs in the For Loop container.) |

Delay	Script task	Delays processing for 10 seconds when the DataReady package variable is set to 0 and the TimeoutCount is not yet exhausted.(This task runs in the For Loop container, and uses Visual Basic.)
Log Extract Error	Script task	Logs an error to the event log when the DataReady package variable is set to either 1 or 5.(This task runs in the For Loop Container.)
Extract Customer Data	Execute Package task	Runs the CDCCustomerExtract package after the For Loop container finishes, and the DataReady package variable is set to either 2 or 3.
Extract CreditCard Data	Execute Package task	Runs the CDCCreditCardExtract package after the For Loop container finishes, and the DataReady package variable is set to either 2 or 3.
Extract WorkOrder Data	Execute Package task	Runs the CDCWorkOrderExtract package after the For Loop container finishes, and the DataReady package variable is set to 2 or 3.
Log Extraction Complete	Script task	Enters a message in the event log that indicates that the extraction interval has finished.This task runs after all child packages have finished.

CDCCustomerExtract Package Components

When the MasterCDC package runs, four package configurations of type, "Parent package variable", enable the MasterCDC package to pass package variables to the CDCCustomerExtract package. The following table lists these package variables.

Parent	Child
User::ExtractEndTime	EndTime
User::ExtractStartTime	StartTime
User::DataReady	DataReady
User::LastLSN	LastLSN

The following table lists the tasks, containers, data sources and destinations, and transformations that the CDCCustomerExtract package uses.

Name	Element	Purpose

| Generate SQL Data Query| Script task| Uses package variables to determine the type of query to run against the OLE DB source. There are two types of queries:

One query runs for the initial extraction interval. This query uses a custom wrapper function that uses an LSN value for the low endpoint and a datetime value for the high endpoint.
The other query runs for all other extraction intervals. For these intervals, the query uses the standard generated datetime wrappers. The CDCCustomerExtract package stores this query in the SQLDataQuery package variable. |

Process Change Data	Data Flow task	Uses an OLE DB source to query for change data. A data flow component then separates the returned rows into flows—insert, delete, and update—that correspond to the operation required to apply the row to the destination. An OLE DB destination handles the insert flow. Data Flow components that run SQL commands for each row handle the delete and update flows.
Query for Change Data	OLE DB source	Uses the query that the SQLDataQuery package variable supplies to extract change data. The query uses the connection manager, AdventureWorks2008.

| Filter Based on Operation| Conditional Split transformation| Divides the results set that the query returns into three different flows. The transformation uses the value of the _CDCOPERATION column in each returned row to divide the results set:

If the value is “I”, directs the row to the insert flow.
If the value is “UN”, directs the row to the update flow.
If the value is “D”, directs the row to the delete flow. |

Customer Inserts	OLE DB destination	Processes the insert flow. Uses the connection manager, AdventureWorksDW2008, to connect to the destination and then inserts the specified rows into the target Customer table.
Customer Deletes	OLE DB Command transformation	Processes the delete flow. Uses the connection manager, AdventureWorksDW2008, to connect to the destination and then deletes the specified rows from the target Customer table.
Customer Updates	OLE DB Command transformation	Processes the update flow. Uses the connection manager, AdventureWorksDW2008, to connect to the destination and then updates the specified rows in the target Customer table.

CDCCreditCardExtract PackageComponents

When the MasterCDC package runs, four package configurations of type, "Parent package variable", enable the MasterCDC package to pass package variables to the CDCCreditCardExtract package. The following table lists these package variables.

Parent	Child
User::ExtractEndTime	EndTime
User::ExtractStartTime	StartTime
User::DataReady	DataReady
User::LastLSN	LastLSN

The following table lists the tasks, containers, data sources, data destinations, and transformations that the CDCCreditCardExtract package uses.

Name	Element	Purpose
Generate SQL Data Query	Script task	Uses package variables to determine the type of query to run against the OLE DB source. There are two types of queries:One query synchronizes the package to the database during the initial extraction interval. This query uses a custom wrapper function that uses an LSN value for the low endpoint and a datetime value for the high endpoint. The other query runs for all other extraction intervals. For these intervals, the query uses the standard generated datetime wrappers. The CDCCreditCardExtract package stores this query in the SQLDataQuery package variable.
Process Change Data	Data Flow task	Uses an OLE DB source to query for change data. A data flow component then separates the returned rows into flows—insert, delete, and update—that correspond to the operation required to apply the row to the destination. An OLE DB destination handles the insert flow. Data Flow components that run SQL commands for each row handle the delete and update flows.
Query for Change Data	OLE DB source	Uses the query that the SQLDataQuery package variable supplies to extract change data. The query uses the connection manager, AdventureWorks2008.

| Filter Based on Operation| Conditional Split transformation| Divides the results set that the query returns into three different flows. This transformation uses the value of the _CDCOPERATION column in each returned row to divide the results set:

If the value is “I”, directs the row to the insert flow.
If the value is “UN”, directs the row to the update flow.
If the value is “D”, directs the row to the delete flow. |

CreditCard Inserts	OLE DB destination	Processes the insert flow. Uses the connection manager, AdventureWorksDW2008, to connect to the destination and then inserts the specified rows into the target CreditCard table.
CreditCard Deletes	OLE DB Command transformation	Processes the delete flow. Uses the connection manager, AdventureWorksDW2008, to connect to the destination and then deletes the specified rows from the target CreditCard table.
CreditCard Updates	OLE DB Command transformation	Processes the update flow. Uses the connection manager, AdventureWorksDW2008, to connect to the destination and then updates the specified rows in the target CreditCard table.

CDCWorkOrderExtract Package Components

When the MasterCDC package runs, four package configurations of type, "Parent package variable", enable the MasterCDC package to pass package variables to the CDCWorkOrderExtract Extract package. The following table lists these package variables.

Parent	Child
User::ExtractEndTime	EndTime
User::ExtractStartTime	StartTime
User::DataReady	DataReady
User::LastLSN	LastLSN

The following table lists the tasks, containers, data sources, data destinations, and transformations that the CDCWorkOrderExtract package uses.

Name	Element	Purpose

| Generate SQL Data Query| Script task| Uses package variables to determine the type of query to run against the OLE DB source. There are two types of queries:

One synchronizes the package to the database during the initial extraction interval. This query uses a custom wrapper function that uses an LSN value for the low endpoint and a datetime value for the high endpoint.
The other query runs for all other extraction intervals. For these intervals, the query uses the standard generated datetime wrappers. The CDCCustomerExtract package stores this query in the SQLDataQuery package variable. |

Process Change Data	Data Flow task	Uses an OLE DB source to query for change data. A data flow component then separates the returned rows into flows—insert, delete, and update—that correspond to the operation required to apply the row to the destination. An OLE DB destination handles the insert flow. Data Flow components that run SQL commands for each row handle the delete and update flows.
Query for Change Data	OLE DB source	Uses the query that the SQLDataQuery package variable supplies to extract change data. The query uses the connection manager, AdventureWorks2008.

If the value is “I”, directs the row to the insert flow.
If the value is “UN”, directs the row to the update flow.
If the value is “D”, directs the row to the delete flow. |

WorkOrder Inserts	OLE DB destination	Processes the insert flow. Uses the connection manager, AdventureWorksDW2008, to connect to the destination and then inserts the specified rows into the target WorkOrder table.
WorkOrder Deletes	OLE DB Command transformation	Processes the delete flow. Uses the connection manager, AdventureWorksDW2008, to connect to the destination and then deletes the specified rows from the target WorkOrder table.
WorkOrder Updates	OLE DB Command transformation	Processes the update flow. Uses the connection manager, AdventureWorksDW2008, to connect to the destination and then updates the specified rows in the target WorkOrder table.

Updated Wiki: SS2008!Readme Change Data Capture for Specified Interval Package Sample

bonniefe — Thu, 06 Nov 2008 23:02:37 GMT

Readme_Change Data Capture since Last Request Package Sample

11/05/2008 21:36:06

Note:
This sample works only with SQL Server 2008 Enterprise and SQL Server 2008 Developer. This sample will not work with any version of SQL Server earlier than SQL Server 2008, or on any edition other than SQL Server 2008 Enterprise or SQL Server 2008 Developer.

This sample shows how to incorporate change data capture technology into an extraction, transformation, and loading (ETL) environment that uses Integration Services. This sample is a complete end-to-end sample that includes both workload generation and the initial load of target tables as part of the sample setup. After the initial load finishes, the master package runs periodically to gather the changes that have occured since the last request. The master package then updates the target replicas to reflect those changes.
The source database is the AdventureWorks2008 database. This sample uses existing tables in the AdventureWorks2008 database to populate comparable destination tables in the CDCSample schema in the AdventureWorksDW2008 database.

Note:
This sample uses log sequence numbers (LSNs) to specify the range for the change data capture functions that request change data. To see how to use datetime values to specify the query range when you query for change data, see Readme_Change Data Capture for Specified Interval Package Sample.

Important:
Samples are provided for educational purposes only. They are not intended to be used in a production environment and have not been tested in a production environment. Microsoft does not provide technical support for these samples.

Requirements

To run this sample package, the following requirements must be met:

The sample package and data files that the sample uses must be installed on the local hard disk drive. You can download the sample from Microsoft SQL Server Product Samples: Integration Services.
You must have installed and have administrative permissions on the AdventureWorks2008 OLTP and AdventureWorksDW2008 databases.
You must install SQL Server Database Engine to install support for the change data capture feature. You must also install Replication when you install SQL Server Database Engine.
If you intend only to run the sample from the command line, you must install Integration Services.
If you want to open and run the sample in SSIS Designer, you must install Business Intelligence Development Studio. For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.

Location of the Sample Files

This sample consists of the following files:

The solution file and Readme file.
The project files and packages.
The Transact-SQL script files.

Location of the Solution File and Readme File

The following folder is the default location of the solution file and Readme file for this sample:
<drive>:\Program Files\Microsoft SQL Server\100\Samples\Integration Services\Package Samples\Change Data Capture Since Last Request Package Sample\
The following table provides the complete name and a short description of the files in this folder.

File	Description
Change Data Capture LSN Based Sample.sln	The solution file for this sample.
Readme_ChangeDataCapturesinceLastRequestPackageSample.htm	The Readme file for this sample.

Location of the Project Files and Packages

The following folder is the default location of the project files and packages for this sample:
<drive>:\Program Files\Microsoft SQL Server\100\Samples\Integration Services\Package Samples\Change Data Capture Since Last Request Package Sample\Change Data Capture LSN Based Sample\
The following table provides the complete name and a short description of the files in this folder.

File	Description
Change Data Capture LSN Based Sample.dtproj	The project file for this sample.

| SetupCDCSample.dtsx| The setup package and sample test harness.

Note:
If you did not install this sample to the default location, you will have to modify the package variables, SQLServerInstallPath and BasePath , to correspond to the appropriate installation path. The default value of the SQLServerInstallPath package variable is <drive>:\Program Files\Microsoft SQL Server\. The value of the BasePath package variable derives from the value of the SQLServerInstallPath package variable.

Note:

MasterCDC.dtsx	The master package that performs an incremental load cycle.
CDCCustomerExtract.dtsx	The child package that gathers the changes to the Customer table for the extraction interval, and then applies these changes to the destination.
CDCCreditCardExtract.dtsx	The child package that gathers the changes to the CreditCard table for the extraction interval, and then applies these changes to the destination.
CDCWorkOrderExtract.dtsx	The child package that gathers the changes to the WorkOrder table for the extraction interval, and apply these changes to the destination.

Location of the Transact-SQL Script Files

The following folder is the default location of the Transact-SQL script files for this sample:
<drive>:\Program Files\Microsoft SQL Server\100\Samples\Integration Services\Package Samples\Change Data Capture Since Last Request Package Sample\Change Data Capture LSN Based Sample\Scripts\
The following table provides the complete name and a short description of the files in this folder.

File	Description
CDCSetupTables.sql	The sample setup file.
CDCCustomerInsert.sql	The script that applies Inserts to CDCSample.Customer table.
CDCCustomerModify.sql	The script that applies Updates to CDCSample.Customer table.
CDCCreditCardInsert.sql	The script that applies Inserts to CDCSample.CreditCard table.
CDCCreditCardModify.sql	The script that applies Updates to CDCSample.CreditCard table.
CDCWorkOrderInsert.sql	The script that applies Inserts to CDCSample.WorkOrder table.
CDCWOrkOrderModify.sql	The script that applies Updates to CDCSample.WorkOrder table.
CDCCleanup.sql	The script that removes all objects that the sample creates.To apply this script, run sqlcmd –E –iCDCCleanup.sql .

Running the Sample

To run the package, you can use either the dtexec command prompt utility (dtexec.exe) or BI Development Studio.
To run the package by using the dtexec utility Open a Command Prompt window.Use the Change Directory command, cd, to change the directory that contains the dtexec utility.The default location of the dtexec utility is <drive>:\Program Files\Microsoft SQL Server\100\DTS\Binn.At the command prompt, type the following command: dtexec /f "C:\Program Files\Microsoft SQL Server\100\Samples\Integration Services\Package Samples\Change Data Capture Since Last Request Package Sample\Change Data Capture LSN Based Sample\SetupCDCSample.dtsx "Press ENTER.For more information about how to use the dtexec utility run a package, see the topic "dtexec Utility" in SQL Server Books Online. To run the package in Business Intelligence Development Studio In BI Development Studio, on the File menu, point to Open, and then click Project/Solution.For Files of type, select Integration Services Project Files (.dtproj). Then, locate the Change Data Capture Since Last Request Package Sample* folder, and double-click the file, Change Change Data Capture LSN Based Sample.dtproj.In Solution Explorer, in the SSIS Packages folder, right-click SetupCDCSample.dtsx, and then click Execute Package.

Sample Packages and Their Components

The sample consists of five packages:
The setup package—SetupCDCSampleThe setup package acts as a test harness for the sample. As a test harness, this package does the following processes: Performs all the required initialization. This includes creating a database snapshot. Generates a data manipulation language (DML) workload against the source tables while cycling the master package at 10 second intervals. The master package performs an incremental load of the target tables for all changes processed by the capture process since the last request. Monitors the progress of the run, and stops the sample after all the DML workload has been processed and applied to the destination tables. Validates, at the end of the run, the content of the destination tables. The setup package compares the destination tables with the content of the source tables, and then records the results in the event log. The master package—MasterCDCThe master package performs an incremental load of the target tables for the interval provided as input. To determine whether to continue with the incremental load, the master package checks the endpoints of the interval: If both endpoints for the extraction interval are in range, the master package starts the three child packages, which perform the incremental loads for the individual tables. If either the low or high endpoint is outside the interval where change data exists for a source table, the master package logs an error and stops the sample.After all the child packages have finished running, the master package logs a message to the event log that indicates the sample has finished for the interval. The master package then stops the sample. Three child packages—Extract Customer Data, Extract CreditCard Data and Extract WorkOrder DataThe structure of each of these child packages is identical: Each child package first creates the query that extracts the changed data. Then, the child package runs a data flow task that performs the incremental load of the changed data. The data flow task uses information in the result set that the query returns to split the returned rows. The data flow splits the rows into three distinct flows—insert, update, or delete—that correspond to the operation required to apply the row to the destination. The data flow task then runs the tasks that handle the various flows. The following sections describe the components found in each package.

SetupCDCSample Package Components

The SetupCDCSample package has several annotated functional groups:

Initialize Environment and Enable Change Data Capture
Generate Workload
Verify Capture Process is Running
Perform Initial Load for Target Tables
Prepare for Initial Extraction
Extract and Process Change Data
Validate Incremental Load and Report Run Status These groups help organize the content as described in the following sections.

Note:
To view the annotated functional groups, open the SetupCDCSample package in Business Intelligence Development Studio. To see a larger view of the package, click the four-way arrow in the lower-right corner of the Control Flow tab, and then position the view window over the package.

Initialize Environment and Enable Change Data Capture

This functional group contains a single Execute SQL task. The purpose of this task is to do the following:

Create the sample source tables from existing AdventureWorks2008 tables, and then enable change data capture for these tables.
Create the target tables in the AdventureWorks2008DW database. The following table lists the task that this functional group uses.

Name	Element	Purpose

| Create Tables and Enable Change Data Capture| Execute SQL task| Creates the sample source tables from existing AdventureWorks2008 tables:

Checks for any objects that were created in previous runs of the sample, and deletes these objects, if present.
Enables the AdventureWorks2008 database for change data capture.
Creates the CDCSample schema.
Creates the tables, CDCSample.Customer, CDCSample.CreditCard, and CDCSample.WorkOrder, in the CDCSample schema. (These tables mirror the comparable tables in the dbo schema.) Creates the target tables in the AdventureWorks2008DW database :
Checks for any objects that were created in previous runs of the sample, and then deletes these objects, if present.
Creates the CDCSample schema.
Creates the target tables, Customer, CreditCard, and WorkOrder, in the CDCSample schema.
Initializes the tables, CDCSample.Customer, CDCSample.CreditCard, and CDCSample.WorkOrder, with a subset of the table data from their parent AdventureWorks2008 tables.
Enables change data capture on the parent AdventureWorks2008 tables. |

Generate Workload

This functional group contains six Execute SQL tasks and a Script task:

Each of the three source tables has two Execute SQL tasks: one that generates insert activity against the table and one that generates update activity. Three of the six Execute SQL tasks run after change data capture has been enabled on the source tables. The remaining three run as each of the first three workload tasks finishes.
When all the Execute SQL tasks have run, the Script task runs. The Script task sets the package variables that indicate that the workload has finished. The following table lists the tasks that this functional group uses.

Name	Element	Purpose
Insert Customer Table	Execute SQL task	Applies inserts to the AdventureWorks2008.CDCSample.Customer table.
Modify Customer Table	Execute SQL task	Applies updates to the AdventureWorks2008.CDCSample.Customer table.
Insert CreditCard Table	Execute SQL task	Applies inserts to the AdventureWorks2008.CDCSample.CreditCard table.
Modify CreditCard Table	Execute SQL task	Applies updates to the AdventureWorks2008.CDCSample.CreditCard table.
Insert WorkOrder Table	Execute SQL task	Applies inserts to the AdventureWorks2008.CDCSample.WorkOrder table.
Modify WorkOrder Table	Execute SQL task	Applies updates to the AdventureWorks2008.CDCSample.WorkOrder table.

| Mark Workload Completion| Script task| Sets the following package variables:

The WorkloadCompleted package variable that indicates whether the workload has finished.
The WorkloadEndTime package variable that indicates the time at which the workload finished. This task uses Visual Basic. |

Verify Capture Process is Running

This functional group contains one Execute SQL tasks and one Script task.

The Execute SQL task runs after the environment has been initialized and the source tables have been enabled for change sata capture. This task verifies that the change data capture process has started automatically.
If the change data capture process has not automatically started, the Script task runs to log an error in the event log. This error message indicates that SQL Server Agent must be running for the capture process to automatically start. Then, the sample stops running. If the capture process is running, the Script task allows the database snapshot to continue in preparation for the initial load of the target tables.

Perform Initial Load for Target Tables

This functional group contains one Script task and three Data Flow tasks:

The Script task, Create Database Snapshot, creates a database snapshot of the AdventureWorks2008 database. This snapshot provides the source tables for the initial load of the target tables.
The three data flow tasks then extract data from the snapshot tables and apply this data to the destination tables in the AdventureWorksDW2008 database. The following table summarizes these tasks.

|| Name || Element
|| Purpose ||

Create Database Snapshot	Execute SQL task	Creates a database snapshot for AdventureWorks2008.
Load Target Customer Table from Snapshot	Data Flow task	Uses an OLE DB source to extract data from the snapshot table, CDCSample.Customer, and then uses an OLE DB destination to apply the rows to the table, AdventureWorksDW2008.CDCSample.Customer.
Load CreditCard Table from Snapshot	Data Flow task	Uses an OLE DB source to extract data from the snapshot table, CDCSample.CreditCard, and then uses an OLE DB destination to apply the rows to the table, AdventureWorksDW2008.CDCSample.CreditCard.
Load WorkOrder Table From Snapshot	Data Flow task	Uses an OLE DB source to extract data from the snapshot table, CDCSample.WorkOrder, and then uses an OLE DB destination to apply the rows to the table, AdventureWorksDW2008.CDCSample.WorkOrder.

Prepare for Initial Extraction

This functional group contains one Execute SQL task, which determines an appropriate LSN range to synchronize the first incremental load to the initial load.

Name	Element	Purpose
Get End-points for Initial Query Interval	Execute SQL task	Extracts the last LSN that is included in the database snapshot from snapshot metadata. Then, increments this value to serve as the low LSN value for the first incremental load that is applied after initialization. The task then delays until the capture process has processed through this LSN value in the transaction log. After this condition is true, the task identifies the current maximum LSN as the high LSN value for the initial query interval. The task uses the function, sys.fnvarbintohexstr, to convert the binary LSN values for the initial query interval to strings that are saved as the package variables, User::ExtractStartLSN and User::ExtractEndLSN . The task uses the cdc.lsntime_mapping table to associate an approximate datetime value with the low endpoint, which the task saves as the package variable, User::ExtractStartTime .

Extract and Process Change Data

This functional group contains a For Loop container that includes two tasks:

An Execute Package task that gathers and applies the change data that is associated with the current query interval to the target tables.
An Execute SQL task that first delays for 10 seconds, and then computes the LSN range for the next query interval. The For Loop container maintains the package variable, IntervalID . The For Loop container initializes the IntervalID package variable to 0, and then and increments this variable by 1 on each iteration of the loop. The loop continues to run until the following conditions are true:

The WorkloadCompleted package variable is set to 1.
The computed value for the ExtractionStartTime package variable, which will be used in the next iteration, exceeds the recorded value for the WorkloadEndTime package variable.

Name	Element	Purpose
Cycle Master at 10 second intervals	For Loop container	First runs the package to gather changes for the interval, and then applies these changes to the target tables. The container then runs the Execute SQL task that first delays for 10 seconds and then computes the new extraction interval.The container stops processing when all the changes in the generated workload have been applied to the destination tables.
Run Master to Extract Data	Execute Package task	Runs the MasterCDC package that applies the incremental load for a given extraction interval to the destination tables.
Delay 10 Seconds and Set New Query Interval	Execute SQL task	Uses the function, sys.fncdchexstrtobin, to convert the string representation of the high LSN value for the previous query to a binary(10) value. Then, uses the function, sys.fncdcincrementlsn, to increment this value to serve the low LSN value for the next query interval. After a delay of 10 seconds, uses the function, sys.fncdcgetmaxlsn, to obtain the current maximum LSN that has been processed by the capture process. This value serves as the high endpoint of the next query itnerval.If the low endpoint is greater than the maximum LSN, the task continues to delay for 10 seconds, and then obtains the current maximum LSN until the low endpoint does not exceed the maximum. The task uses the function, sys.fnvarbintohexstr, to convert the binary LSN values that act as the lower and upper bounds for the next query interval to strings. The task then saves these strings as the package variables, User::ExtractStartLSN and User::ExtractEndLSN . The task uses the cdc.lsntimemapping table i to associate an approximate datetime value with the low endpoint, which is saved as the package variable, User::ExtractStartTime .

Validate Incremental Load and Report Run Status

This functional group contains an Execute SQL task and a Script task:

The Execute SQL task, Check for Mismatch in Replicas, uses SQL CHECKSUM to compare the source tables with the replicas and sets package variables that indicate the run status.
At the end of the run, the Script task, Output Run Completion Status, uses the package variables to report the results of the table comparisons in the event log. The following table summarizes these tasks.

Name	Element	Purpose
Check for Mismatch in Replicas	Execute SQL task	Uses CHECKSUM to compare the replicas to the source tables. Based on this comparison, the task then sets the package variables, CustomerMismatch , CreditCardMismatch , and WorkOrderMismatch , accordingly.
Output Run Completion Status	Script task	Outputs a status message to the event log at the end of the run. (This message reports on the parity of the package variables, CustomerMismatch , CreditCardMismatch , and WorkOrderMismatch .) Then, sets the run status accordingly.

MasterCDC Package Components

Parent	Child
User::ExtractEndLSN	ExtractEndLSN
User::ExtractStartLSN	ExtractStartLSN
User::IntervalID	IntervalID
User::BasePath	BasePath

The following tables list the tasks, containers, data sources and destinations, and transformations that are used in the master package.

Name	Element	Purpose

| Wait for Capture Process to Process Extraction Interval| For Loop container| Contains the following components:

An Execute SQL task that sets a package variable that indicates the status of the proposed extraction interval relative to the capture process.
A Script task that generates an entry in the error log if the query interval is not valid, and causes the package to stop running. The query interval is not valid if either the low endpoint or the high endpoint do not lie in the change data capture validity interval for the database. If the interval is valid, this container also starts the Execute Packages tasks that run the child packages that apply the change data to the destination tables.After the child packages complete, this container also runs a Script task that records that the extraction interval has finished in the event log. |

| Check for Valid Interval| Execute SQL task| Sets the DataReady package variable to one of the following values:

0 = Query interval is not valid
1 = Query interval is valid (This task runs in the For Loop container.) |

Log Extract Error	Script task	Logs an error to the event log when the DataReady package variable is set to 0.(This task runs in the For Loop Container.)
Extract Customer Data	Execute Package task	Runs the CDCCustomerExtract package after the For Loop container finishes, and the DataReady package variable is set to 1
Extract CreditCard Data	Execute Package task	Runs the CDCCreditCardExtract package after the For Loop container finishes, and the DataReady package variable is set to 1.
Extract WorkOrder Data	Execute Package task	Runs the CDCWorkOrderExtract package after the For Loop container finishes, and the DataReady package variable is set to 1.
Log Extraction Complete	Script task	Enters a message in the event log that indicates that the extraction interval has finished.This task runs after all child packages have finished.

CDCCustomerExtract Package Components

When the MasterCDC package runs, two package configurations of type, "Parent package variable", enable the MasterCDC package to pass package variables to the CDCCustomerExtract package. The following table lists these package variables.

Parent	Child
User::ExtractEndLSN	EndLSN
User::ExtractStartLSN	StartLSN

The following table lists the tasks, containers, data sources and destinations, and transformations that the CDCCustomerExtract package uses.

Name	Element	Purpose
Generate SQL Data Query	Script task	Uses the package variables, StartLSN and EndLSN , to determine the LSN values to provide to the generated function that queries for change data. The query is deposited in the package variable, SQLDataQuery .
Process Change Data	Data Flow task	Uses an OLE DB source to query for change data. A data flow component then separates the returned rows into flows—insert, delete, and update—that correspond to the operation required to apply the row to the destination. An OLE DB destination handles the insert flow. Data Flow components that run SQL commands for each row handle the delete and update flows.
Query for Change Data	OLE DB source	Uses the query that the SQLDataQuery package variable supplies to extract change data. The query uses the connection manager, AdventureWorks2008.

| Filter Based on Operation| Conditional Split transformation| Divides the results set that the query returns into three different flows. The transformation uses the value of the __$operation column in each returned row to divide the results set:

If the value is 2, directs the row to the insert flow.
If the value is 4, directs the row to the update flow.
If the value is 1, directs the row to the delete flow. |

Customer Inserts	OLE DB destination	Processes the insert flow. Uses the connection manager, AdventureWorksDW2008, to connect to the destination and then inserts the specified rows into the target Customer table.
Customer Deletes	OLE DB Command transformation	Processes the delete flow. Uses the connection manager, AdventureWorksDW2008, to connect to the destination and then deletes the specified rows from the target Customer table.
Customer Updates	OLE DB Command transformation	Processes the update flow. Uses the connection manager, AdventureWorksDW2008, to connect to the destination and then updates the specified rows in the target Customer table.

CDCCreditCardExtract Package Components

When the MasterCDC package runs, two package configurations of type, "Parent package variable", enable the MasterCDC package to pass package variables to the CDCCreditCardExtract package. The following table lists these package variables.

Parent	Child
User::ExtractEndLSN	EndLSN
User::ExtractStartLSN	StartLSN

The following table lists the tasks, containers, data sources, data destinations, and transformations that the CDCCreditCardExtract package uses.

Name	Element	Purpose
Generate SQL Data Query	Script task	Uses the package variables StartLSN and EndLSN , to determine the LSN values to provide to the generated function call that queries for change data. The query is deposited in the package variable, SQLDataQuery .
Process Change Data	Data Flow task	Uses an OLE DB source to query for change data. A data flow component then separates the returned rows into flows—insert, delete, and update—that correspond to the operation required to apply the row to the destination. An OLE DB destination handles the insert flow. Data Flow components that run SQL commands for each row handle the delete and update flows.
Query for Change Data	OLE DB source	Uses the query that the SQLDataQuery package variable supplies to extract change data. The query uses the connection manager, AdventureWorks2008.

| Filter Based on Operation| Conditional Split transformation| Divides the results set that the query returns into three different flows. The transformation uses the value of the __$operation column in each returned row to divide the results set:

If the value is 2, directs the row to the insert flow.
If the value is 4, directs the row to the update flow.
If the value is 1, directs the row to the delete flow. |

CreditCard Inserts	OLE DB destination	Processes the insert flow. Uses the connection manager, AdventureWorksDW2008, to connect to the destination and then inserts the specified rows into the target CreditCard table.
CreditCard Deletes	OLE DB Command transformation	Processes the delete flow. Uses the connection manager, AdventureWorksDW2008, to connect to the destination and then deletes the specified rows from the target CreditCard table.
CreditCard Updates	OLE DB Command transformation	Processes the update flow. Uses the connection manager, AdventureWorksDW2008, to connect to the destination and then updates the specified rows in the target CreditCard table.

CDCWorkOrderExtract Package Components

When the MasterCDC package runs, two package configurations of type, "Parent package variable", enable the MasterCDC package to pass package variables to the CDCWorkOrderExtract Extract package. The following table lists these package variables.

Parent	Child
User::ExtractEndLSN	EndLSN
User::ExtractStartLSN	StartLSN

The following table lists the tasks, containers, data sources, data destinations, and transformations that the CDCWorkOrderExtract package uses.

Name	Element	Purpose
Generate SQL Data Query	Script task	Uses the package variables, StartLSN and EndLSN , to determine the LSN values to provide to the generated function call that queries for change data. The query is deposited in the package variable, SQLDataQuery .
Process Change Data	Data Flow task	Uses an OLE DB source to query for change data. A data flow component then separates the returned rows into flows—insert, delete, and update—that correspond to the operation required to apply the row to the destination. An OLE DB destination handles the insert flow. Data Flow components that run SQL commands for each row handle the delete and update flows.
Query for Change Data	OLE DB source	Uses the query that the SQLDataQuery package variable supplies to extract change data. The query uses the connection manager, AdventureWorks2008.

| Filter Based on Operation| Conditional Split transformation| Divides the results set that the query returns into three different flows. The transformation uses the value of the __$operation column in each returned row to divide the results set:

If the value is 2, directs the row to the insert flow.
If the value is 4, directs the row to the update flow.
If the value is 1, directs the row to the delete flow. |

WorkOrder Inserts	OLE DB destination	Processes the insert flow. Uses the connection manager, AdventureWorksDW2008, to connect to the destination and then inserts the specified rows into the target WorkOrder table.
WorkOrder Deletes	OLE DB Command transformation	Processes the delete flow. Uses the connection manager, AdventureWorksDW2008, to connect to the destination and then deletes the specified rows from the target WorkOrder table.
WorkOrder Updates	OLE DB Command transformation	Processes the update flow. Uses the connection manager, AdventureWorksDW2008, to connect to the destination and then updates the specified rows in the target WorkOrder table.

Updated Wiki: SS2008!Readme_ODBC_SparseCols

bonniefe — Thu, 06 Nov 2008 23:02:18 GMT

ReadmeODBCSparseCols

11/05/2008 21:36:06

This sample works only with SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2008.
This sample shows how to call SQLColumns on a table with sparse columns that were defined by using ODBC in SQL Server Native Client.
SQL Server samples and sample databases must be downloaded and installed before you can view or work with them. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.

Scenario

For more information about the sparse columns feature, see Sparse Columns Support in SQL Server Native Client in SQL Server Books Online.

Languages

This sample uses Visual C++.

Prerequisites

Before running this sample, make sure that the following software is installed:

SQL Server or SQL Server Express, including Database Engine. You can download SQL Server Express from the Microsoft Download Center.
The SQL Server Database Engine samples that are available at the Microsoft SQL Server Developer Center.
.NET Framework SDK 2.0 (or later) or Microsoft Visual Studio 2005 (or later). You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework Documentation.

Building the Sample

You must specify a server. In odbc_sparse.cpp, change "MyServer" to a valid server name.
Make sure your INCLUDE environment variable includes the directory that contains sqlncli.h.
If you are using Visual Studio, load the odbc_sparse.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe at a command prompt. Pass in the odbc_sparse.sln file, as follows: * MSBuild odbc_sparse.sln *

Running the Sample

From Visual Studio, invoke Start Without Debugging (CTRL+F5).
If you built with MSBuild.exe, invoke odbc_sparse.exe.

Updated Wiki: SS2008!Readme_ODBC Date Time

bonniefe — Thu, 06 Nov 2008 23:02:02 GMT

Readme_ODBC Date Time

11/05/2008 21:36:06

This sample works only with SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2008.
This sample shows how to initialize the date/time data structures that were added in SQL Server 2008. It then prepares the input values, binds parameters, and executes the query.
SQL Server samples and sample databases must be downloaded and installed before you can view or work with them. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.

Scenario

For more information about date/time enhancements in SQL Server 2008, see Date/Time Improvements.

Languages

This sample uses Visual C++.

Prerequisites

Before running this sample, make sure the following software is installed:

SQL Server or SQL Server Express, including Database Engine. You can download SQL Server Express from the Microsoft Download Center.
The SQL Server Database Engine samples that are available at the Microsoft SQL Server Developer Center.
.NET Framework SDK 2.0 (or later) or Microsoft Visual Studio 2005 (or later). You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework Documentation.
You also need an ODBC data source called DateTime. This data source must be based on the ODBC driver for SQL Server Native Client. The default database for DateTime should be tempdb. To build and run this sample as a 32-bit application on a 64-bit operating system, you must create the ODBC data source with the ODBC Administrator in %windir%\SysWOW64\odbcad32.exe.

Building the Sample

This sample connects to your computer's default SQL Server instance. To connect to a named instance, change the definition of the ODBC data source to specify the instance, using the following format: server\namedinstance_. By default, SQL Server Express installs to a named instance.
The sample requires you to execute the following Transact-SQL, which you can find in the scripts directory of the sample: * {" use tempdb

GO

IF EXISTS (SELECT name FROM sysobjects WHERE name = 'DateTimeTypes')
DROP TABLE DateTimeTypes
GO

CREATE TABLE DateTimeTypes (datecol date, time2col time(7), datetime2col datetime2(7), datetimeoffsetcol datetimeoffset(7))
GO "}* In SQL Server Management Studio, load and execute the Scripts\setup.sql script. Alternatively, you can execute the following command in a Command Prompt window: * sqlcmd -E -I -i Scripts\setup.sql *

If you are using Visual Studio, load the DateTime_ODBC.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe in a Command Prompt, passing it the DateTime_ODBC.sln file: * MSBuild DateTime_ODBC.sln *

Running the Sample

From Visual Studio, invoke Start Without Debugging (CTRL+F5).
If you built with MSBuild.exe, invoke DateTime_ODBC.exe.

Updated Wiki: SS2008!README UseDataAtExecutionParameters

bonniefe — Thu, 06 Nov 2008 23:01:48 GMT

Readme_UseDataAtExecutionParameters (ODBC)

11/05/2008 21:36:06

This sample works only with SQL Server 2005 and SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2005.
The sample shows how to read SQL_LONG variable character data using SQLParamData and SQLPutData. This sample is not supported on IA64.
SQL Server samples and sample databases must be downloaded and installed before you can view or work with them. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.

Languages

This sample uses Visual C++.

Prerequisites

Before running this sample, make sure the following software is installed:

SQL Server or SQL Server Express including Database Engine. You can download SQL Server Express from the Microsoft Download Center.
The AdventureWorks database that is available at the Microsoft SQL Server Developer Center.
The SQL Server Database Engine samples that are available at the Microsoft SQL Server Developer Center.
.NET Framework SDK 2.0 or Microsoft Visual Studio 2005. You can obtain .NET Framework SDK free of charge. See Installing the .NET Framework Documentation.
You will also need an ODBC data source called AdventureWorks, whose default database is the AdventureWorks sample database. If you will build and run this sample as a 32-bit application on a 64-bit operating system, you must create the ODBC data source with the ODBC Administrator in %windir%\SysWOW64\odbcad32.exe.

Building the Sample

This sample connects to your computer's default SQL Server instance. To connect to a named instance, change the definition of the ODBC data source to specify the instance using the following format: server\namedinstance_. By default, SQL Server Express installs to a named instance.
The sample requires you to execute the following stored procedure, which you can find in the sample's scripts directory: * {" use AdventureWorks

CREATE TABLE emp4 (NAME char(30), AGE int, BIRTHDAY datetime, Memo1 text) "}* In SQL Server Management Studio, load and execute the Scripts\setup.sql script or execute the following command in a Command Prompt window: * sqlcmd -E -I -i Scripts\setup.sql *

If you are using Visual Studio, load the UseDataAtExecutionParameters.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe at a command prompt, passing it the UseDataAtExecutionParameters.sln file: * MSBuild UseDataAtExecutionParameters.sln *

Running the Sample

From Visual Studio, invoke Start Without Debugging (CTRL+F5).
If you built with MSBuild.exe, invoke UseDataAtExecutionParameters.exe.

Updated Wiki: SS2005!README UseDataAtExecutionParameters

bonniefe — Thu, 06 Nov 2008 23:01:32 GMT

README UseDataAtExecutionParameters

Updated: 17 July 2006
The sample shows how to read SQL_LONG variable character data using SQLParamData and SQLPutData. This sample is not supported on IA64.

Languages

This sample uses Visual C++.

Prerequisites

Before running this sample, make sure the following software is installed:

SQL Server 2005 or SQL Server 2005 Express Edition (SQL Server Express) including Database Engine. You can download SQL Server Express from the Microsoft Download Center.
The AdventureWorks database which is included with SQL Server 2005, and is also available at the Microsoft SQL Server Developer Center.
The SQL Server 2005 Database Engine samples. These samples are included with SQL Server 2005. You can download the latest version of the samples at the Microsoft SQL Server Developer Center.
.NET Framework SDK 2.0 or Microsoft Visual Studio 2005. You can obtain .NET Framework SDK free of charge. See Installing the .NET Framework SDK.
You will also need an ODBC data source called AdventureWorks, whose default database is the AdventureWorks sample database.

Building the Sample

This sample connects to your computer's default SQL Server instance. To connect to a named instance, change the definition of the ODBC data source to specify the instance using the following format: server\namedinstance_. By default, SQL Server Express installs to a named instance.
The sample requires you to execute the following stored procedure, which you can find in the sample's scripts directory: * {" use AdventureWorks

If you are using Visual Studio, load the UseDataAtExecutionParameters.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe at a command prompt, passing it the UseDataAtExecutionParameters.sln file: * MSBuild UseDataAtExecutionParameters.sln *

Running the Sample

From Visual Studio, invoke Start Without Debugging (CTRL+F5).
If you built with MSBuild.exe, invoke UseDataAtExecutionParameters.exe.

Change History

Release	History
17 July 2006	Changed content: Clarified and updated prerequisites including the Web site for downloading the samples. New content: Added information on connecting to a named instance.

Updated Wiki: SS2008!README UseDataAtExecutionColumns

bonniefe — Thu, 06 Nov 2008 23:01:17 GMT

Readme_UseDataAtExecutionColumns (ODBC)

11/05/2008 21:36:06

This sample works only with SQL Server 2005 and SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2005.
The sample shows how to read a SQL_LONG variable character data using SQLGetData. This sample is not supported on IA64.
SQL Server samples and sample databases must be downloaded and installed before you can view or work with them. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.

Languages

This sample uses Visual C++.

Prerequisites

Before running this sample, make sure the following software is installed:

SQL Server or SQL Server Express including Database Engine. You can download SQL Server Express from the Microsoft Download Center.
The AdventureWorks database that is available at the Microsoft SQL Server Developer Center.
The SQL Server Database Engine samples that are available at the Microsoft SQL Server Developer Center.
.NET Framework SDK 2.0 or Microsoft Visual Studio 2005. You can obtain .NET Framework SDK free of charge. See Installing the .NET Framework Documentation.
You will also need an ODBC data source called AdventureWorks, whose default database is the AdventureWorks sample database. If you will build and run this sample as a 32-bit application on a 64-bit operating system, you must create the ODBC data source with the ODBC Administrator in %windir%\SysWOW64\odbcad32.exe.

Building the Sample

This sample connects to your computer's default SQL Server instance. To connect to a named instance, change the definition of the ODBC data source to specify the instance using the following format: server\namedinstance_. By default, SQL Server Express installs to a named instance.
This sample requires you to run the following Transact-SQL, which you can find in the sample's scripts directory: * {" use AdventureWorks

CREATE TABLE emp3 (NAME char(30), AGE int, BIRTHDAY datetime, Memo1 text)
INSERT INTO emp3 (NAME, AGE, Memo1) VALUES ('Name1', '12', 'This is the first employee')
INSERT INTO emp3 (NAME, AGE, Memo1) VALUES ('Name2', '18', 'This is the second employee') "}* In SQL Server Management Studio, load and execute the Scripts\setup.sql script or execute the following command in a Command Prompt window: * sqlcmd -E -I -I Scripts\setup.sql *

If you are using Visual Studio, load the BulkCopyFormatAndData.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe at a command prompt, passing it the UseDataAtExecutionColumns.sln file: * MSBuild UseDataAtExecutionColumns.sln *

Running the Sample

From Visual Studio, invoke Start Without Debugging (CTRL+F5).
If you built with MSBuild.exe, invoke UseDataAtExecutionColumns.exe.

MSFTDPProdSamples Wiki & Documentation Rss Feed

New Comment on "SS2008!Readme_Displaying Column and Catalog Metadata for Sparse Columns (OLE DB)"

New Comment on "SS2008!Readme_Displaying Column and Catalog Metadata for Sparse Columns (OLE DB)"

New Comment on "SS2008!Readme_Displaying Column and Catalog Metadata for Sparse Columns (OLE DB)"

Updated Wiki: Home

ADO.NET

ODBC

OLE DB

Programmability

Updated Wiki: SS2008!ODBC Spatial Storage

Readme for Spatial Storage

Scenario

Languages

Prerequisites

Building the Sample

Running the Sample

See Also

Concepts

Help and Information

Updated Wiki: SS2008!ODBC Spatial Storage

Readme for Spatial Storage

Scenario

Languages

Prerequisites

Building the Sample

Running the Sample

See Also

Concepts

Help and Information

Updated Wiki: SS2008!ODBC Spatial Storage

Readme for Spatial Storage

Scenario

Languages

Prerequisites

Building the Sample

Running the Sample

See Also

Concepts

Help and Information

Updated Wiki: SS2008!ODBC Spatial Storage

Readme for Spatial Storage

Scenario

Languages

Prerequisites

Building the Sample

Running the Sample

See Also

Concepts

Help and Information

Updated Wiki: SS2008!ODBC Spatial Storage

ReadmeSpatialStorage

Scenario

Languages

Prerequisites

Building the Sample

Running the Sample

See Also

Concepts

Help and Information

Updated Wiki: Home

ADO.NET

ODBC

OLE DB

Programmability

Updated Wiki: SS2008!ODBC Spatial Storage

ReadmeSpatialStorage

Scenario

Languages

Prerequisites

Building the Sample

Running the Sample

See Also

Concepts

Help and Information

Updated Wiki: SS2008!Readme Large UDT ODBC

ReadmeLargeUDT_ODBC

Scenario

Languages

Prerequisites

Building the Sample