Microsoft SQL Server Product Samples: Data Programming

Source code checked in, #11622

ReedMe — Wed, 11 Jun 2008 05:42:45 GMT

Adding 'Katmai:June 2008 RC0'

Updated Wiki: Home

ReedMe — Tue, 10 Jun 2008 23:48:23 GMT

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

SQL Server 2008 RC0 product samples are now available.

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
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

RELEASED: SQL Server 2008 RC0 (Jun 10, 2008)

Tue, 10 Jun 2008 23:20:34 GMT

This release contains the SQL Server 2008 RC0 product samples for Data Programming.

UPDATED RELEASE: SQL Server 2008 RC0 (Jun 10, 2008)

Tue, 10 Jun 2008 23:20:34 GMT

This release contains the SQL Server 2008 RC0 product samples for Data Programming.

Updated Wiki: SS2008!Readme_ODBC_SparseCols

bonniefe — Tue, 10 Jun 2008 23:00:06 GMT

ReadmeODBCSparseCols

6/10/2008 1:32:27 AM

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. These samples are included with SQL Server. You can download the latest version of the samples 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 — Tue, 10 Jun 2008 22:59:44 GMT

Readme_ODBC Date Time

6/10/2008 1:32:27 AM

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. These samples are included with SQL Server. You can download the latest version of the samples 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 — Tue, 10 Jun 2008 22:59:21 GMT

Readme_UseDataAtExecutionParameters (ODBC)

6/10/2008 1:32:27 AM

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 which is included with SQL Server, and is also available at the Microsoft SQL Server Developer Center.
The SQL Server Database Engine samples. These samples are included with SQL Server. 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 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 — Tue, 10 Jun 2008 22:59:05 GMT

README UseDataAtExecutionParameters

6/10/2008 3:14:30 PM

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 — Tue, 10 Jun 2008 22:58:45 GMT

Readme_UseDataAtExecutionColumns (ODBC)

6/10/2008 1:32:27 AM

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 which is included with SQL Server, and is also available at the Microsoft SQL Server Developer Center.
The SQL Server Database Engine samples. These samples are included with SQL Server. 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 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.

Updated Wiki: SS2005!README UseDataAtExecutionColumns

bonniefe — Tue, 10 Jun 2008 22:58:28 GMT

README UseDataAtExecutionColumns

6/10/2008 3:14:30 PM

Updated: 17 July 2006
The sample shows how to read a SQL_LONG variable character data using SQLGetData. 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.
This sample requires you to run the following Transact-SQL, which you can find in the sample's scripts directory: * {" use AdventureWorks

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.

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 ODBC Table-Valued Parameters

bonniefe — Tue, 10 Jun 2008 22:58:09 GMT

Readme_Table-Valued Parameters (ODBC)

6/10/2008 1:32:27 AM

This sample depends on features that were introduced in SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2008.
This sample shows how to use table-valued parameters to insert multiple rows, with multiple columns, with one call to the 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 on this sample, see Table-Valued Parameters (SQL Server Native Client) in 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 Database Engine. You can download SQL Server Express from the Microsoft Download Center.
The AdventureWorks database which is included with SQL Server, and is also available at the Microsoft SQL Server Developer Center.
The SQL Server Database Engine samples. These samples are included with SQL Server. You can download the latest version of the samples 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. See Installing the .NET Framework Documentation.
You will also need an ODBC data source called TVPDemo. This data source must be based on the ODBC driver for SQL Server Native Client. The default database for TVPDemo can be any test database on your computer. 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.
If you are using Visual Studio, load the TableValuedParameters_ODBC.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe in a Command Prompt, passing it the ProcessODBCErrors.sln file: * MSBuild TableValuedParameters_ODBC.sln *

Running the Sample

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

Updated Wiki: SS2008!README How to profile driver performance data (ODBC)

bonniefe — Tue, 10 Jun 2008 22:57:53 GMT

Readme_Profiling Driver Performance Data (ODBC)

6/10/2008 1:32:27 AM

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.
This sample shows the SQL Server ODBC driver-specific options to record performance statistics. The sample creates one file: odbcperf.log.
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 on this sample, see How to: Profile Driver Performance Data (ODBC) in 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 Database Engine. You can download SQL Server Express from the Microsoft Download Center.
The AdventureWorks database which is included with SQL Server, and is also available at the Microsoft SQL Server Developer Center.
The SQL Server Database Engine samples. These samples are included with SQL Server. 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 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.
If you are using Visual Studio, load the CreateAndDisplayPerformanceLog.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe in a Command Prompt, passing it the CreateAndDisplayPerformanceLog.sln file: * MSBuild CreateAndDisplayPerformanceLog.sln *

Running the Sample

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

Updated Wiki: SS2005!README How to profile driver performance data (ODBC)

bonniefe — Tue, 10 Jun 2008 22:57:27 GMT

README How to profile driver performance data (ODBC)

6/10/2008 3:14:30 PM

Updated: 17 July 2006
This sample shows the SQL Server ODBC driver-specific options to record performance statistics. The sample creates one file: odbcperf.log.

Scenario

For more information on this sample, see How to: Profile Driver Performance Data (ODBC) in Books Online.

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.
If you are using Visual Studio, load the CreateAndDisplayPerformanceLog.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe in a Command Prompt, passing it the CreateAndDisplayPerformanceLog.sln file: * MSBuild CreateAndDisplayPerformanceLog.sln *

Running the Sample

From Visual Studio, invoke Start Without Debugging (CTRL+F5).
If you built with MSBuild.exe, invoke CreateAndDisplayPerformanceLog.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 How to process return codes and output parameters (ODBC)

bonniefe — Tue, 10 Jun 2008 22:57:02 GMT

Readme_Processing Return Codes and Output Parameters (ODBC)

6/10/2008 1:32:27 AM

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.
This sample shows processing a return code and output parameter. 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.

Scenario

For more information on this sample, see How to: Process Return Codes and Output Parameters (ODBC) in 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 Database Engine. You can download SQL Server Express from the Microsoft Download Center.
The AdventureWorks database which is included with SQL Server, and is also available at the Microsoft SQL Server Developer Center.
The SQL Server Database Engine samples. These samples are included with SQL Server. 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 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

IF EXISTS (SELECT name FROM sysobjects WHERE name = 'TestParm')
DROP PROCEDURE TestParm
GO

CREATE PROCEDURE TestParm
@OutParm int OUTPUT
AS
SELECT Name FROM Purchasing.Vendor
SELECT @OutParm = 88
RETURN 99
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 ProcessReturnCodes.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe in a Command Prompt, passing it the ProcessReturnCodes.sln file: * MSBuild ProcessReturnCodes.sln *

Running the Sample

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

Updated Wiki: SS2005!README How to process return codes and output parameters (ODBC)

bonniefe — Tue, 10 Jun 2008 22:56:22 GMT

README How to process return codes and output parameters (ODBC)

6/10/2008 3:14:30 PM

Updated: 17 July 2006
This sample shows processing a return code and output parameter. This sample is not supported on IA64.

Scenario

For more information on this sample, see How to: Process Return Codes and Output Parameters (ODBC) in Books Online.

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

DROP PROCEDURE TestParm
GO
CREATE PROCEDURE TestParm
@OutParm int OUTPUT
AS
SELECT Name FROM Purchasing.Vendor
SELECT @OutParm = 88
RETURN 99
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 ProcessReturnCodes.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe in a Command Prompt, passing it the ProcessReturnCodes.sln file: * MSBuild ProcessReturnCodes.sln *

Running the Sample

From Visual Studio, invoke Start Without Debugging (CTRL+F5).
If you built with MSBuild.exe, invoke ProcessReturnCodes.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 How to process ODBC errors (ODBC)

bonniefe — Tue, 10 Jun 2008 22:55:51 GMT

Readme_How to process ODBC errors (ODBC)

6/10/2008 1:32:27 AM

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 a simple error handler that calls SQLGetDiagRec for the standard ODBC information. It then tests for a valid connection, and if there is, it calls SQLGetDiagField for the Microsoft® SQL Server™ ODBC driver-specific diagnostic fields. 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.

Scenario

For more information on this sample, see How to: Process ODBC Errors (ODBC) in 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 Database Engine. You can download SQL Server Express from the Microsoft Download Center.
The AdventureWorks database which is included with SQL Server, and is also available at the Microsoft SQL Server Developer Center.
The SQL Server Database Engine samples. These samples are included with SQL Server. 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 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

IF EXISTS (SELECT name FROM sysobjects WHERE name = 'BadOne')
DROP PROCEDURE BadOne

Go

CREATE PROCEDURE BadOne
AS
SELECT * FROM Purchasing.Vendor
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 ProcessODBCErrors.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe in a Command Prompt, passing it the ProcessODBCErrors.sln file: * MSBuild ProcessODBCErrors.sln *

Running the Sample

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

Updated Wiki: SS2005!README How to process ODBC errors (ODBC)

bonniefe — Tue, 10 Jun 2008 22:55:23 GMT

README How to process ODBC errors (ODBC)

6/10/2008 3:14:30 PM

Updated: 17 July 2006
The sample shows a simple error handler that calls SQLGetDiagRec for the standard ODBC information. It then tests for a valid connection, and if there is, it calls SQLGetDiagField for the Microsoft® SQL Server™ ODBC driver-specific diagnostic fields. This sample is not supported on IA64.

Scenario

For more information on this sample, see How to: Process ODBC Errors (ODBC) in Books Online.

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

DROP PROCEDURE BadOne
GO

CREATE PROCEDURE BadOne
AS
SELECT * FROM Purchasing.Vendor
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 ProcessODBCErrors.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe in a Command Prompt, passing it the ProcessODBCErrors.sln file: * MSBuild ProcessODBCErrors.sln *

Running the Sample

From Visual Studio, invoke Start Without Debugging (CTRL+F5).
If you built with MSBuild.exe, invoke ProcessODBCErrors.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 How to log long-running queries (ODBC)

bonniefe — Tue, 10 Jun 2008 22:54:40 GMT

Readme_Logging Long-Running Queries (ODBC)

6/10/2008 1:32:27 AM

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.
This sample shows the SQL Server ODBC driver-specific options to log long-running queries. When run, creates Odbcqry.log, which contains a list of queries whose execution exceeds an interval set by the application. 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.

Scenario

For more information on this sample, see How to: Log Long-Running Queries (ODBC) in 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 Database Engine. You can download SQL Server Express from the Microsoft Download Center.
The AdventureWorks database which is included with SQL Server, and is also available at the Microsoft SQL Server Developer Center.
The SQL Server Database Engine samples. These samples are included with SQL Server. 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 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.
If you are using Visual Studio, load the LogLongRunningQuery.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe in a Command Prompt, passing it the LogLongRunningQuery.sln file: * MSBuild LogLongRunningQuery.sln *

Running the Sample

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

Updated Wiki: SS2005!README How to log long-running queries (ODBC)

bonniefe — Tue, 10 Jun 2008 22:54:17 GMT

README How to log long-running queries (ODBC)

6/10/2008 3:14:30 PM

Updated: 17 July 2006
This sample shows the SQL Server ODBC driver-specific options to log long-running queries. When run, creates Odbcqry.log, which contains a list of queries whose execution exceeds an interval set by the application. This sample is not supported on IA64.

Scenario

For more information on this sample, see How to: Log Long-Running Queries (ODBC) in Books Online.

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.
If you are using Visual Studio, load the LogLongRunningQuery.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe in a Command Prompt, passing it the LogLongRunningQuery.sln file: * MSBuild LogLongRunningQuery.sln *

Running the Sample

From Visual Studio, invoke Start Without Debugging (CTRL+F5).
If you built with MSBuild.exe, invoke LogLongRunningQuery.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 How to create a bulk copy format file (ODBC)

bonniefe — Tue, 10 Jun 2008 22:53:45 GMT

Readme_How to create a bulk copy format file (ODBC)

6/10/2008 1:32:27 AM

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.
This sample shows how to create a bulk copy format file.
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 on this sample, see How to: Create a Bulk Copy Format File (ODBC) in 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 Database Engine. You can download SQL Server Express from this Microsoft Web site.
The AdventureWorks database which is included with SQL Server, and is also available at the SQL Server Developer Web site.
The SQL Server Database Engine samples. These samples are included with SQL Server. You can download the latest version of the samples at the SQL Server Developer Web site.
.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. This data source must be based on the ODBC driver that is supplied by the operating system (the driver name is "SQL Server"). 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 Transact-SQL statements, which you can find in the sample's scripts directory: * {" use AdventureWorks

CREATE TABLE BCPDate (cola int, colb datetime)
insert BCPDate(cola) values(1)
insert BCPDate(cola) values(2)
insert BCPDate(cola) values(3)
insert BCPDate(cola) values(4) "}* 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 BulkCopyWithFormat.sln file and build it.
If you are using MSBuild.exe, invoke MSBuild.exe in a Command Prompt, passing it the BulkCopyWithFormat.sln file: * MSBuild BulkCopyWithFormat.sln *

Running the Sample

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

Microsoft SQL Server Product Samples: Data Programming

Source code checked in, #11622

Updated Wiki: Home

ADO.NET

ODBC

OLE DB

RELEASED: SQL Server 2008 RC0 (Jun 10, 2008)

UPDATED RELEASE: SQL Server 2008 RC0 (Jun 10, 2008)

Updated Wiki: SS2008!Readme_ODBC_SparseCols

ReadmeODBCSparseCols

Scenario

Languages

Prerequisites

Building the Sample

Running the Sample

See Also

Concepts

Help and Information

Updated Wiki: SS2008!Readme_ODBC Date Time

Readme_ODBC Date Time

Scenario

Languages

Prerequisites

Building the Sample

Running the Sample

See Also

Concepts

Help and Information

Updated Wiki: SS2008!README UseDataAtExecutionParameters

Readme_UseDataAtExecutionParameters (ODBC)

Languages

Prerequisites

Building the Sample

Running the Sample

See Also

Concepts

Help and Information

Updated Wiki: SS2005!README UseDataAtExecutionParameters

README UseDataAtExecutionParameters

Languages

Prerequisites

Building the Sample

Running the Sample

Change History

See Also

Concepts

Help and Information

Updated Wiki: SS2008!README UseDataAtExecutionColumns

Readme_UseDataAtExecutionColumns (ODBC)

Languages

Prerequisites

Building the Sample

Running the Sample

See Also

Concepts

Help and Information

Updated Wiki: SS2005!README UseDataAtExecutionColumns

README UseDataAtExecutionColumns

Languages

Prerequisites

Building the Sample

Running the Sample

Change History

See Also

Concepts

Help and Information

Updated Wiki: SS2008!README ODBC Table-Valued Parameters

Readme_Table-Valued Parameters (ODBC)

Scenario

Languages

Prerequisites

Building the Sample

Running the Sample

See Also

Concepts

Help and Information

Updated Wiki: SS2008!README How to profile driver performance data (ODBC)

Readme_Profiling Driver Performance Data (ODBC)

Scenario

Languages