MSFTEngProdSamples Wiki & Documentation Rss Feed

Updated Wiki: Home

bonniefe — Tue, 08 Dec 2009 23:52:36 GMT

SQL Server Samples Portal Page > SQL Server Database Engine Product Samples

The Microsoft SQL Server Database Engine is the core service for storing, processing and securing data. The Database Engine provides controlled access and rapid transaction processing to meet the requirements of the most demanding data consuming applications within your enterprise. The Database Engine also provides rich support for sustaining high availability.

This project contains Engine samples released with Microsoft SQL Server product. Below is the list of these samples. If you are interested in contributing Engine 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.

Sample	SQL Server 2005	SQL Server 2008 & SQL Server 2008R2
Data Warehouse Tuning Techniques Sample	n/a	SS2008
Grouping Sets Report	n/a	SS2008

CLR

Sample	SQL Server 2005	SQL Server 2008 & SQL Server 2008R2
AdventureWorks Cycles CLR Layer	SS2005	SS2008
Array Parameter Sample	SS2005	SS2008
Assembly Cleanup Sample	n/a	SS2008
Calendar-Aware Date/Time UDTs	SS2005	SS2008
Currency Web Service Sample	SS2005	SS2008
Hello World Ready Sample	SS2005	SS2008
Hello World Sample	SS2005	SS2008
Impersonation Sample	SS2005	n/a
In-Process Data Access Sample	SS2005	SS2008
Large Binary Object (LOB) Handling	SS2005	SS2008
Oracle TVF Sample	SS2005	SS2008
Result Set Sample	SS2005	SS2008
Send DataSet Sample	SS2005	SS2008
Spatial Sample	SS2005	SS2008
String Split Table-Valued Function (TVF)	SS2005	SS2008
Supplementary-Aware String Manipulation	SS2005	SS2008
System.Transactions Sample	SS2005	SS2008
Time Series Sample	n/a	SS2008
UDT Utilities	SS2005	SS2008
User-Defined Data Type (UDT) Sample	SS2005	SS2008
UTF8 String User-Defined Data Type (UDT)	SS2005	SS2008

Full Text Search

Sample	SQL Server 2005	SQL Server 2008 & SQL Server 2008R2
Item Finder Sample	SS2005	SS2008

SMO

Sample	SQL Server 2005	SQL Server 2008 & SQL Server 2008R2
BackRest	SS2005	SS2008
CheckIdentityValues	SS2005	SS2008
CreateSPs	SS2005	SS2008
DatabaseDefrag	SS2005	SS2008
DatabaseSpace	SS2005	SS2008
DependencyExplorer	SS2005	SS2008
IndexSizes	SS2005	SS2008
LoadRegAssembly	SS2005	SS2008
ManageDatabases	SS2005	SS2008
ManageDatabaseUsers	SS2005	SS2008
ManageTables	SS2005	SS2008
RebuildAllIndexes	SS2005	SS2008
ScriptTable	SS2005	SS2008
ServerConnect	SS2005	SS2008
ServerInfo	SS2005	SS2008
ServiceBrokerConfiguration	SS2005	SS2008
SmoBrowser	SS2005	SS2008
SmoCompare	SS2005	SS2008
SmoEvents	SS2005	SS2008
SMOPing	SS2005	SS2008
SmoScripter	SS2005	SS2008
SqlServerList	SS2005	SS2008
SqlService	SS2005	SS2008
Tracer	SS2005	SS2008
UtilityConversion	SS2005	SS2008
VerifyBackup	SS2005	SS2008

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

Updated Wiki: SS2005!Currency Web Service Sample

bonniefe — Mon, 24 Aug 2009 21:55:41 GMT

Currency Web Service Sample

The Currency Web Service sample for SQL Server 2005 demonstrates how to invoke a Web service from server-side common language runtime code. Suppose that there is a Web server available somewhere which can supply current currency exchange information. This sample demonstrates how to expose the result of calling that Web service as a common language runtime-based table valued function (TVF). This table valued function could be used, for example, to periodically insert new rows into the Sales.CurrencyRate rate table in the AdventureWorks database. A simple implementation of the Web service is provided to demonstrate the complete scenario, but the data used in the sample is fictitious.
The default installation directory is drive:\Program Files\Microsoft SQL Server\90\Samples\Engine\Programmability\CLR\CurrencyWebService.

Scenario

A developer wants invoke a Web service from server-side common language runtime code and use the results returned by invoking the Web service.

Languages

Transact-SQL and Visual C#.

Features

The Currency Web Service sample uses the following features of SQL Server:

Application Area	Features
Overall	Invoking Web services; common language runtime table valued functions; SOAP

Prerequisites

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

SQL Server 2005 or SQL Server 2005 Express Edition (SQL Server Express). You can obtain SQL Server Express free of charge from the SQL Server 2005 Express Edition Documentation and Samples Web site
The AdventureWorks database which is included with SQL Server 2005, and is also available at the SQL Server Developer Web site.
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 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 SDK.

Building the Sample

If you have not already created the strong-name key file ExternalSampleKey.snk, generate the key file by using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft Visual Studio 2005, point to Visual Studio Tools, and then click Visual Studio 2005 Command Prompt.—Or—Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
At the command prompt, use the change directory (CD) command to change the current folder of the command prompt window to the Samples folder. Note: To determine the folder where samples are located, click Start, point to All Programs, point to Microsoft SQL Server 2005, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <systemdrive_>:\Program Files\Microsoft SQL Server\90\Samples.
At the command prompt, run the following command to generate the key file: sn -k ExternalSampleKey.snk ** Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.To build the sample, do the following:

Build the sample

If you haven't already done so using Windows Explorer click right on the CS\CurrencyWebService directory and enable web sharing for that directory.
If you want to see how the client web service proxy in CS\CurrencyWebClient\service.cs file was created using the WSDL.exe tool, look at the scripts\RebuildWebReference.cmd file.
Compile the sample by using Visual Studio 2005 and the provided Visual Studio solution, or by using Microsoft MSBuild, which is included in the .NET Framework SDK 2.0. Run a command similar to the following at the command prompt: msbuild /nologo /verbosity:quiet /property:Configuration=Debug CS\CurrencyWebService.sln This solution compiles both the web server code and the web client code.
Make sure that the AdventureWorks database is installed.
At the command prompt CD to the CS\CurrencyWebClient\bin\debug directory and execute the scripts\sgen.cmd batch file. This creates the CurrencyWebClient.XmlSerializers.dll library necessary to avoid dynamically generating the serializers used during the invocation of the web service. By creating this assembly and registering it with SQL Server it is possible to invoke a web service using only External Access rather than Unsafe permissions which is highly desirable.
If you did not install the SQL Server Database Engine samples in the default location, modify the path in the CREATE ASSEMBLY part of the script in Scripts\InstallCS.sql and Scripts\InstallVB.sql to refer to location where the samples were installed.
If you are not an administrator for the SQL Server instance you are using, you must have an administrator grant you CreateAssembly permission to complete the installation.
Open the scripts\installDB.sql file in SQL Server Management Studio. Run the script that is contained in the file, or run a command similar to the following at the command prompt: sqlcmd -E -I -i Scripts\InstallDB.sql This script creates the AdventureWorksCurrency database which contains the fictitious currency conversion data used by the currency web service.
Open the scripts\installCS.sql. Run the script that is contained in the file, or run a command similar to the following at the command prompt: sqlcmd -E -I -i Scripts\InstallCS.sql This script does the following:
Removes any stored procedures and functions that are about to be defined, if they exist.
Drops the assembly registration, if it already exists.
Ensures that the strong name used to sign the assemblies has the appropriate external access permissions.
Registers the assembly with the web service client.
Registers the assembly with the static serializers needed to avoid dynamically creating the serializers during the invocation of the web service.
Registers the CLR table valued function which invokes the web service.
Creates a Transact-SQL stored procedure called by the web service.

Running the Sample

To run the sample, do the following:

Run the sample

Open the scripts\test.sql file in Management Studio and run the script that is contained in the file. Or, run the following command at the command prompt: sqlcmd -E -I -i Scripts\test.sql

Removing the Sample

To remove the sample, do the following:

Remove the sample

Open the scripts\cleanup.sql file in Management Studio and run the script that is contained in the file. Or, run the following command at the command prompt: sqlcmd -E -I -i Scripts\cleanup.sql

Comments

Normally for security reasons it is better to invoke Web services in the middle tier of an application. One reasonable reason to invoke Web services from the data tier would be to exchange data between SQL Server 2005 and an application running on some non-Microsoft server such as an IBM mainframe which might only be conveniently accessible via Web services. The security concerns can be mitigated by having both servers behind two layers of firewall. Web services that transmit sensitive information should use the https protocol instead of the http protocol.
The common language runtime for SQL Server 2005 or SQL Server 2005 Express Edition must be enabled for this sample to work correctly.
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. Sample applications and assemblies should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.
© 2007 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Currency Web Service Sample

bonniefe — Mon, 24 Aug 2009 21:54:34 GMT

Readme_Currency Web Service Sample

8/24/2000

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 Currency Web Service sample for SQL Server demonstrates how to invoke a Web service from server-side common language runtime code. Suppose that there is a Web server available somewhere which can supply current currency exchange information. This sample demonstrates how to expose the result of calling that Web service as a common language runtime-based table valued function (TVF). This table valued function could be used, for example, to periodically insert new rows into the Sales.CurrencyRate rate table in the AdventureWorks database. A simple implementation of the Web service is provided to demonstrate the complete scenario, but the data used in the sample is fictitious.

Note:
When you compile samples that use SQL Server's CLR integration, the path of the version of the Microsoft .NET Framework compiler that was distributed with SQL Server must be the first Framework directory in the PATH environment variable. The location of the compiler that is included with SQL Server will be either drive:\WINNT\Microsoft.NET\Framework\v2.0.xxxxx or drive:\Windows\Microsoft.NET\Framework\v2.0.xxxxx, where drive is the installation drive and xxxxx is the version number of the .NET Framework that was included with SQL Server.

Note:

When you compile samples that use SQL Server's CLR integration, the path of the version of the Microsoft .NET Framework compiler that was distributed with SQL Server must be the first Framework directory in the PATH environment variable. The location of the compiler that is included with SQL Server will be either drive:\WINNT\Microsoft.NET\Framework\v2.0.xxxxx or drive:\Windows\Microsoft.NET\Framework\v2.0.xxxxx, where drive is the installation drive and xxxxx is the version number of the .NET Framework that was included with SQL Server.

The default installation directory is C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\CLR\CurrencyWebService.
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

A developer wants to invoke a Web service from server-side common language runtime code and use the results returned by invoking the Web service.

Languages

Transact-SQL and Visual C#.

Features

The Currency Web Service sample uses the following features of SQL Server:

Application Area	Features
Overall	Invoking Web services; common language runtime table valued functions; SOAP

Prerequisites

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

SQL Server. This sample is not supported for SQL Server Express.
The AdventureWorks database that is available at the SQL Server Developer Web site.
The SQL Server Database Engine samples that are available 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.
Internet Information Service (IIS), include all necessary components of IIS which are necessary for ASP.NET applications.

Building the Sample

Before you build the sample, you must create the strong-name key file ExternalSampleKey.snk, as follows:

Open a Microsoft Visual Studio or .NET Framework command prompt.
Change directories to C:\Program Files\Microsoft SQL Server\100\Samples.
Type the following command: * sn -k ExternalSampleKey.snk *To build the sample, do the following:

Build the sample

For Windows XP and Windows 2003, if you haven't already done so using Windows Explorer click right on the CS\CurrencyWebService directory and enable web sharing for that directory.
For Windows Vista if you haven't already done so set up the web application for the web service using the following steps:
Click Start / Control Panel / Administrative Tools / Internet Information Services (IIS) Manager.
In the Connections tree control open up the local machine and then the Web Sites folder. Click right on Default Web Site and click Add Application... Specify CurrencyWebService for the Alias, and specify the full (absolute) path to the CS\CurrencyWebService directory for the Physical path. Click OK.
Grant the NETWORK SERVICE account the default permissions (Read & execute, List folder contents, and Read) for the CS\CurrencyWebService directory.
If you want to see how the client web service proxy in CS\CurrencyWebClient\service.cs file was created using the WSDL.exe tool, look at the scripts\RebuildWebReference.cmd file.
Compile the sample by using Visual Studio 2005 and the provided Visual Studio solution, or by using Microsoft MSBuild, which is included in the .NET Framework SDK 2.0. Run a command similar to the following at the command prompt: msbuild /nologo /verbosity:quiet /property:Configuration=Debug CS\CurrencyWebService.sln This solution compiles both the web server code and the web client code.
Make sure that the AdventureWorks database is installed.
At the command prompt change to the CS\CurrencyWebClient\bin\debug directory and execute the scripts\sgen.cmd batch file. This creates the CurrencyWebClient.XmlSerializers.dll library necessary to avoid dynamically generating the serializers used during the invocation of the web service. By creating this assembly and registering it with SQL Server it is possible to invoke a web service using only External Access rather than Unsafe permissions which is highly desirable.
If you did not install the SQL Server Database Engine samples in the default location, modify the path in the CREATE ASSEMBLY part of the script in Scripts\InstallCS.sql to refer to location where the samples were installed. Also do this for Scripts\InstallDB.sql.
If you are not an administrator for the SQL Server instance you are using, you must have an administrator grant you CreateAssembly permission to complete the installation.
Open the scripts\installDB.sql file in SQL Server Management Studio. Run the script that is contained in the file, or run a command similar to the following at the command prompt: sqlcmd -E -I -i Scripts\InstallDB.sql This script creates the AdventureWorksCurrency database which contains the fictitious currency conversion data used by the currency web service.
Open the scripts\installCS.sql. Run the script that is contained in the file, or run a command similar to the following at the command prompt: sqlcmd -E -I -i Scripts\InstallCS.sql This script does the following:
Removes any stored procedures and functions that are about to be defined, if they exist.
Drops the assembly registration, if it already exists.
Ensures that the strong name used to sign the assemblies has the appropriate external access permissions.
Registers the assembly with the web service client.
Registers the assembly with the static serializers needed to avoid dynamically creating the serializers during the invocation of the web service.
Registers the CLR table valued function which invokes the web service.
Creates a Transact-SQL stored procedure called by the web service.

Running the Sample

To run the sample, do the following:

Run the sample

Open the scripts\test.sql file in Management Studio and run the script that is contained in the file. Or, run the following command at the command prompt: sqlcmd -E -I -i Scripts\test.sql

Removing the Sample

To remove the sample, do the following:

Remove the sample

Open the scripts\cleanup.sql file in Management Studio and run the script that is contained in the file. Or, run the following command at the command prompt: sqlcmd -E -I -i Scripts\cleanup.sql

Comments

Normally for security reasons it is better to invoke Web services in the middle tier of an application. One reasonable reason to invoke Web services from the data tier would be to exchange data between SQL Server and an application running on some non-Microsoft server such as an IBM mainframe which might only be conveniently accessible via Web services. The security concerns can be mitigated by having both servers behind two layers of firewall. Web services that transmit sensitive information should use the https protocol instead of the http protocol.
The common language runtime for SQL Server must be enabled for this sample to work correctly.
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. Sample applications and assemblies should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

Updated Wiki: SS2008!Data Warehouse Tuning Techniques Sample

libinzhao — Thu, 13 Aug 2009 09:25:34 GMT

Readme_Data Warehouse Tuning Techniques Sample

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.
This sample demonstrates techniques for tuning data warehouse queries to improve query performance. In most cases, the query optimizer creates high-quality query plans. However, for specific query patterns, you can improve the query plan by manually tuning the query. Here, we present three such scenarios and their tuning techniques.
The run times cited below were recorded by using an AMD Athlon 64 X2 Dual-Core 4200 CPU with 4 GB of RAM, running Windows Server 2008 and SQL Server 2008. The queries were run from SQL Server Management Studio.

Languages

Transact-SQL

Prerequisites

Before you run this sample, install the following software.

SQL Server 2008 and the following components:
The Database Engine
SQL Server Management Studio
Database Engine samples for SQL Server 2008. The default installation directory is C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Query Processing\Data Warehouse Tuning Techniques.
AdventureWorksDW2008 sample database for SQL Server 2008. For example, if you are using the x64 architecture, you can download SQL2008.AdventureWorksAllDatabases.x64.msi to install AdventureWorksDW2008 . For more information about installing the samples, see Considerations for Installing SQL Server Samples and Sample Databases in SQL Server 2008 Books Online.

Running the Sample

Prepare the Database

The examples included with the Data Warehouse Tuning sample are designed to operate on a modified version of AdventureWorksDW2008 . The original sample database has small fact tables in comparison to data warehousing sizes. Execute the following step one time to create the new FactInternetSalesBig fact table. This is approximately 1000 times larger than FactInternetSales .

Run Prepare.sql. Note that, depending on your machine performance, this might take around one hour or more (run time on test machine was 54 minutes). Note that the extended database will need around 25 GB of drive space.

Example 1: Tune Join Into Semi-Join

This example tunes a query by converting the original join into an explicit semi-join using an EXISTS subquery. Note that the DatesRange common expression returns a single row and uses the fact table only to check whether sales exist for specific dates. A join is not needed to achieve the correct query results; a semi-join is sufficient. However, the query optimizer does not replace this join with a semi-join because the replacement does not apply in all scenarios. Some aggregates (for example, SUM) allow the replacement and some aggregates (for example, COUNT) do not.
Using EXISTS will avoid the expensive inner join, so that for each date row, only the existence of a single fact row will be checked. To demonstrate this, follow these steps:

Open SemiJoin.sql in SQL Server Management Studio.
Execute Original Query. Notice the time it takes to execute the query. On the test machine, the query took 2 minutes, 8 seconds.
Execute Tuned Query. Notice the time it takes to execute the query. The execution time should be significantly less than that of the original query. On the test machine, the query took 1 minute, 1 second.

Example 2: Split Distinct Aggregates

The Original Query of this sample generates a query plan with a multi-consumer spool, shared by the aggregate function and by the distinct operator. A spool is expensive and can be avoided by breaking up the query into a plan with two SELECT statements. This results in serial GROUP BY operators and avoids the spool and join. To demonstrate this, follow these steps:

Open CountDistinct.sql in SQL Server Management Studio.
Execute Original Query. Notice the time it takes to execute the query. On the test machine, the query took 3 minutes, 5 seconds.
Execute Tuned Query. Notice the time it takes to execute the query. The execution time should be significantly less than that of the original query. On the test machine, the query took 1 minute, 18 seconds.

Example 3: Reuse Common Expressions

The original query of this sample generates a query plan with equivalent sub-branches due to the reuse of common expressions. To avoid such duplicate plan branches, a temporary table can be used to store the intermediate result of the common expression. To demonstrate this, follow these steps:

Open CommonExpression.sql in SQL Server Management Studio.
Execute Original Query. Notice the time it takes to execute the query. On the test machine, the query took 2 minutes, 10 seconds.
Execute Tuned Query. Notice the time it takes to execute the query. The execution time should be significantly less than the original query. On the test machine, the query took 1 minute, 18 seconds. © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Readme_ServiceBrokerConfiguration

libinzhao — Thu, 13 Aug 2009 09:16:37 GMT

Readme_ServiceBrokerConfiguration Sample

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.
This sample shows how to create Service Broker objects by using SQL Server Management Objects (SMO). The sample is implemented because several Windows User Controls and classes necessary to create Service Broker objects.
The sample is targeted at a Microsoft .NET Framework developer who wants to learn how to use Service Broker SMO and learn how to create Windows User Controls to manage SQL Server objects. The core scenario is a Microsoft .NET Framework developer who is creating a custom Service Broker management application.
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. Sample applications and assemblies should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

Requirements

This sample requires that the following components are installed.

.NET Framework SDK 2.0. You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework Documentation.
SQL Server Database Engine.

Location

If the code sample was installed to the default location, the sample is located in the following directory:
C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\SMO\ServiceBrokerConfiguration
The C# solution for the code sample is located in the CS directory.

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start* button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.*
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

If you are using the Microsoft .NET Framework SDK, do the following:

Build the Visual Studio Solution

Click Start, point to All Programs, point to Microsoft .NET Framework SDK v2.0, and then click SDK Command Prompt.
Locate the root folder of the sample. Type the following command for the default location:

cd ..\Samples\Engine\Programmability\SMO\ServiceBrokerConfiguration\CS\

msbuild ConfigurationComponent.sln

Or, if you are using Visual Studio 2005, do the following:

Open the \CS\ConfigurationComponent.sln solution file.
Press F6 to build the solution.

Set up SQL Server sample database and sample XML schemas

Locate the \CS\Script folder.
Open and run setup.sql from within SQL Server Management Studio.If you are setting up Remote Service Binding:

Set up SQL Server master keys (optional)

Locate the \CS\Script folder.
Open masterkey.sql from within SQL Server Management Studio.
Enter a password for the master database key in the CREATE MASTER KEY ENCRYPTION BY PASSWORD = statement.
Enter a password for the ssb_ConfigurationSample database key in the CREATE MASTER KEY ENCRYPTION BY PASSWORD = statement.
Run masterkey.sql.

Running the Sample

To run the sample

The default location for the C# version is C:\Program Files\Microsoft SQL Server\100\Samples\SMO\ServiceBrokerConfiguration\CS\SampleApplication\bin\Debug\SampleApplication.exe.

To connect to a local SQL Server instance

Enter a server name in the Server Name field, or accept the default (local) server name.
Click Connect.

To configure the sample for a new database.

Click Options on the Objects tab.
Enter a ScriptPath, or accept the default path. The ScriptPath is used to export a script to a file.
Click Create. The Create button configures the sample, including setting the BaseUrn.

To create MessageTypes

Click New, and then click MessageType.**
Enter ShippingRequest for the MessageType name.
Click Create to create the new MessageType, click New, and then click Message Type.
Enter ShippingAccept for the MessageType name.
Click Create to create the new MessageType, click New, and then click Message Type.
Enter ShippingComplete for MessageType name.
Click Create to create the new MessageType.

To create a contract

Click New, and then click Contract.
Select the MessageTypeMappings drop-down menu.
Select all MessageTypes created above.
Select Target for ShippingAccept and ShippingComplete MessageSource.
Close the MessageTypeMappings drop-down menu.
Enter Shipping for the contract name.
Click Create to create a new contact.

To create queues

Click New, and then click Queue.
Enter ClientQueue for the queue name.
Click Create to create the new queue, click New, and then click Queue.
Enter ServerQueue for queue name.
Click Create to create the new queue.

To create services without RemoteServiceBinding enabled

Click New, and then click Service.
Enter ClientService for the service name.
Select the ContractNames drop-down menu and select the Shipping contract.
Select the QueueName drop-down menu and select the ClientQueue queue.
Enter or select a ServiceOwnerName.
Click Create to create the new service, and then click New.
Enter ServerService for the service name.
Select the ContractNames drop-down and select the Shipping contract.
Select the QueueName drop-down menu and select the ServerQueue queue.
Enter or select a ServiceOwnerName.
Click Create to create the new service.

To create services with RemoteServiceBinding enabled

Click New, and then click Service.
Enter RemoteService for the service name.
Select the ContractNames drop-down menu and select the Shipping contract.
Set EnableRemoteService to true.
Select the QueueName drop-down menu and select the ClientQueue queue.
Enter or select a ServiceOwnerName.
Click Create to create the new service.

To enable anonymous access for a Remote Service

Select RemoteService within the object tree.
Set AllowAnonymous to True.
Click Alter to alter the service.

To create a Target Instance Endpoint

Click New, and then click Target Instance Endpoint.
Enter a name, or accept the default name.
Click Create.

To set a script export path

Click the Object tab if this tab is not already active.
Click Options.
Enter a valid ScriptPath.
Click Create.

To export an object

Select an object within the objects tree.
Click Script then Export.
The object is exported to the ScriptPath set in Application Configuration.

To export a Service definition to a file

Select a service from within the Objects tree.
Click Script, and then click Export.
The service script is exported to the ScriptPath set in Application Configuration.

To drop an object

Select the object in the TreeView.
Click either Drop or Edit, Drop {ObjectName}.

To alter an object

Click the object in the Objects tree that you want to modify.
Modify the properties of that object.
Click Alter to alter the object.

To query data describing an object

Each object can output data describing the object to a Textbox and/or DataGrid.
Select an object in the TreeView.
Click Query.

Removing the Sample

To drop services

Click the ClientService node.
Drop the object.
Click the ServerService node.
Drop the object.
Click the RemoteService node.
Drop the object.

To drop queues

Click the ClientQueue node.
Drop the object.
Click the ServerQueue node.
Drop the object.

To drop contracts

Click the Shipping contract node.
Drop the object.

To drop MessageTypes

Click the ShippingRequest MessageType node.
Drop the object.
Click the ShippingAccept MessageType node.
Drop the object.
Click the ShippingComplete MessageType node.
Drop the object.

To drop a Target Instance Endpoint

Click a Target Instance Endpoint node.
Drop the object. © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Large Binary Object (LOB) Handling

libinzhao — Thu, 02 Apr 2009 03:11:41 GMT

Readme_Large Object (LOB) Handling Sample

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 HandlingLOBUsingCLR sample for SQL Server demonstrates transferring large objects (LOBs) between SQL Server and a file system that is available to the server by using common language runtime (CLR) stored procedures. This sample demonstrates how to access files in server-side code, and then invoke both dynamic queries and stored procedures from CLR-based stored procedures. It also demonstrates how to unregister and register CLR methods and assemblies by using Transact-SQL.

Note:
When you compile SQLCLR samples, the path of the version of the .NET Framework compiler that was distributed with SQL Server must be the first Framework directory in the PATH environment variable. The location of the compiler that is included with SQL Server will be either drive:\WINNT\Microsoft.NET\Framework\v2.0.xxxxx or drive:\Windows\Microsoft.NET\Framework\v2.0.xxxxx, where drive is the installation drive and xxxxx is the version number of the .NET Framework that was included with SQL Server.

Note:

When you compile SQLCLR samples, the path of the version of the .NET Framework compiler that was distributed with SQL Server must be the first Framework directory in the PATH environment variable. The location of the compiler that is included with SQL Server will be either drive:\WINNT\Microsoft.NET\Framework\v2.0.xxxxx or drive:\Windows\Microsoft.NET\Framework\v2.0.xxxxx, where drive is the installation drive and xxxxx is the version number of the .NET Framework that was included with SQL Server.

The default installation directory is C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\CLR\HandlingLOBUsingCLR.
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

A developer wants to copy images between SQL Server and the file system on the server.

Languages

Transact-SQL, Visual C#, and Visual Basic.

Features

The HandlingLOBUsingCLR sample uses the following features of SQL Server:

Application Area	Features
Overall	CLR stored procedures; calling Transact-SQL stored procedures from CLR stored procedures; the VARBINARY(MAX) data type.

Prerequisites

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

SQL Server or SQL Server Express. You can obtain SQL Server Express free of charge from the SQL Server Express Documentation and Samples Web site
The AdventureWorks database that is available at the SQL Server Developer Web site.
The SQL Server Database Engine samples that are available 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.

Building the Sample

If you have not already created the strong-name key file ExternalSampleKey.snk, generate the key file using the following instructions.

To generate a strong name key file

Open a Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft Visual Studio 2005, point to Visual Studio Tools, and then click Visual Studio 2005 Command Prompt.—Or—Open a.NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
At the command prompt, use the change directory (CD) command to change the current folder of the command prompt window to the Samples folder. Note: To determine the folder where samples are located, click Start, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <systemdrive_>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k ExternalSampleKey.snk ** Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.To build the sample, do the following:

Build the sample

Compile the sample by using Visual Studio 2005 and the provided Visual Studio solution, or by using MSBuild, which is included in the .NET Framework SDK 2.0. Run a command similar to the following at the command prompt: msbuild /nologo /verbosity:quiet /property:Configuration=Debug CS\HandlingLOBUsingCLR.sln
Make sure that the AdventureWorks database is installed.
If you did not install the SQL Server Database Engine samples in the default location, modify the path in the CREATE ASSEMBLY part of the script in Scripts\InstallCS.sql and Scripts\InstallVB.sql to refer to location where the samples were installed.
If you are not an administrator for the SQL Server instance you are using, you must have an administrator grant you CreateAssembly permission to complete the installation.
Open the scripts\installCS.sql or scripts\installVB.sql file, depending on whether you compiled the Visual C# project or the Visual Basic project, in SQL Server Management Studio. Run the script that is contained in the file, or run a command similar to the following at the command prompt:

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

This script does the following:

Removes any stored procedures that are about to be defined, if they exist.
Drops the assembly registration, if it already exists.
Registers the assembly.
Registers the CLR stored procedures.
Creates the Transact-SQL stored procedure called by one of the CLR stored procedures.

Running the Sample

To run the sample, do the following:

Run the sample

To read an image from the database, invoke a script similar to the following: exec GetPhotoFromDB 70, 'C:\Temp\', 'test6.gif' go Make sure the directory you specify exists.
To write an image into the database, invoke a script similar to the following: exec PutPhotoIntoDB 70, 'C:\Temp\', 'test1.gif' go Any errors will be reported to the error.log file in the directory that you specify. For scripts that are similar to the ones in this procedure, see the Scripts\test.sql file.

Removing the Sample

To remove the sample, do the following:

Remove the sample

Open the scripts\cleanup.sql file in Management Studio and run the script that is contained in the file. Or, run the following command at the command prompt: sqlcmd -E -I -i Scripts\cleanup.sql

Comments

The CLR for SQL Server or SQL Server Express must be enabled for this sample to work correctly.
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. Sample applications and assemblies should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

Updated Wiki: SS2008!Readme_ServiceBrokerConfiguration

cmslydia — Thu, 02 Apr 2009 02:52:05 GMT

Readme_ServiceBrokerConfiguration Sample

Requirements

This sample requires that the following components are installed.

.NET Framework SDK 2.0. You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework Documentation.
SQL Server Database Engine.

Location

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

If you are using the Microsoft .NET Framework SDK, do the following:

Build the Visual Studio Solution

Click Start, point to All Programs, point to Microsoft .NET Framework SDK v2.0, and then click SDK Command Prompt.
Locate the root folder of the sample. Type the following command for the default location:

cd ..\Samples\Engine\Programmability\SMO\ServiceBrokerConfiguration\CS\
 
msbuild ConfigurationComponent.sln

Or, if you are using Visual Studio 2005, do the following:

Open the \CS\ConfigurationComponent.sln solution file.
Press F6 to build the solution.

Set up SQL Server sample database and sample XML schemas

Locate the \CS\Script folder.
Open and run setup.sql from within SQL Server Management Studio.If you are setting up Remote Service Binding:

Set up SQL Server master keys (optional)

Locate the \CS\Script folder.
Open masterkey.sql from within SQL Server Management Studio.
Enter a password for the master database key in the CREATE MASTER KEY ENCRYPTION BY PASSWORD = statement.
Enter a password for the ssb_ConfigurationSample database key in the CREATE MASTER KEY ENCRYPTION BY PASSWORD = statement.
Run masterkey.sql.

Running the Sample

To run the sample

The default location for the C# version is C:\Program Files\Microsoft SQL Server\100\Samples\SMO\ServiceBrokerConfiguration\CS\SampleApplication\bin\Debug\SampleApplication.exe.

To connect to a local SQL Server instance

Enter a server name in the Server Name field, or accept the default (local) server name.
Click Connect.

To configure the sample for a new database.

Click Options on the Objects tab.
Enter a ScriptPath, or accept the default path. The ScriptPath is used to export a script to a file.
Click Create. The Create button configures the sample, including setting the BaseUrn.

To create MessageTypes

Click New, and then click MessageType.**
Enter ShippingRequest for the MessageType name.
Click Create to create the new MessageType, click New, and then click Message Type.
Enter ShippingAccept for the MessageType name.
Click Create to create the new MessageType, click New, and then click Message Type.
Enter ShippingComplete for MessageType name.
Click Create to create the new MessageType.

To create a contract

Click New, and then click Contract.
Select the MessageTypeMappings drop-down menu.
Select all MessageTypes created above.
Select Target for ShippingAccept and ShippingComplete MessageSource.
Close the MessageTypeMappings drop-down menu.
Enter Shipping for the contract name.
Click Create to create a new contact.

To create queues

Click New, and then click Queue.
Enter ClientQueue for the queue name.
Click Create to create the new queue, click New, and then click Queue.
Enter ServerQueue for queue name.
Click Create to create the new queue.

To create services without RemoteServiceBinding enabled

Click New, and then click Service.
Enter ClientService for the service name.
Select the ContractNames drop-down menu and select the Shipping contract.
Select the QueueName drop-down menu and select the ClientQueue queue.
Enter or select a ServiceOwnerName.
Click Create to create the new service, and then click New.
Enter ServerService for the service name.
Select the ContractNames drop-down and select the Shipping contract.
Select the QueueName drop-down menu and select the ServerQueue queue.
Enter or select a ServiceOwnerName.
Click Create to create the new service.

To create services with RemoteServiceBinding enabled

Click New, and then click Service.
Enter RemoteService for the service name.
Select the ContractNames drop-down menu and select the Shipping contract.
Set EnableRemoteService to true.
Select the QueueName drop-down menu and select the ClientQueue queue.
Enter or select a ServiceOwnerName.
Click Create to create the new service, and then click New.

To enable anonymous access for a Remote Service

Select RemoteService within the object tree.
Set AllowAnonymous to True.
Click Alter to alter the service.

To create a Target Instance Endpoint

Click New, and then click Target Instance Endpoint.
Enter a name, or accept the default name.
Click Create.

To set a script export path

Click the Object tab if this tab is not already active.
Click Options.
Enter a valid ScriptPath.
Click Create.

To export an object

Select an object within the objects tree.
Click Script then Export.
The object is exported to the ScriptPath set in Application Configuration.

To export a Service definition to a file

Select a service from within the Objects tree.
Click Script, and then click Export.
The service script is exported to the ScriptPath set in Application Configuration.

To drop an object

Select the object in the TreeView.
Click either Drop or Edit, Drop {ObjectName}.

To alter an object

Click the object in the Objects tree that you want to modify.
Modify the properties of that object.
Click Alter to alter the object.

To query data describing an object

Each object can output data describing the object to a Textbox and/or DataGrid.
Select an object in the TreeView.
Click Query.

Removing the Sample

To drop services

Click the ClientService node.
Drop the object.
Click the ServerService node.
Drop the object.
Click the RemoteService node.
Drop the object.

To drop queues

Click the ClientQueue node.
Drop the object.
Click the ServerQueue node.
Drop the object.

To drop contracts

Click the Shipping contract node.
Drop the object.

To drop MessageTypes

Click the ShippingRequest MessageType node.
Drop the object.
Click the ShippingAccept MessageType node.
Drop the object.
Click the ShippingComplete MessageType node.
Drop the object.

To drop a Target Instance Endpoint

Click a Target Instance Endpoint node.
Drop the object. © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Large Binary Object (LOB) Handling

libinzhao — Thu, 02 Apr 2009 02:48:47 GMT

Readme_Large Object (LOB) Handling Sample

Note:
When you compile SQLCLR samples, the path of the version of the .NET Framework compiler that was distributed with SQL Server must be the first Framework directory in the PATH environment variable. The location of the compiler that is included with SQL Server will be either drive:\WINNT\Microsoft.NET\Framework\v2.0.xxxxx or drive:\Windows\Microsoft.NET\Framework\v2.0.xxxxx, where drive is the installation drive and xxxxx is the version number of the .NET Framework that was included with SQL Server.

Note:

Scenario

A developer wants to copy images between SQL Server and the file system on the server.

Languages

Transact-SQL, Visual C#, and Visual Basic.

Features

The HandlingLOBUsingCLR sample uses the following features of SQL Server:

Application Area	Features
Overall	CLR stored procedures; calling Transact-SQL stored procedures from CLR stored procedures; the VARBINARY(MAX) data type.

Prerequisites

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

SQL Server or SQL Server Express. You can obtain SQL Server Express free of charge from the SQL Server Express Documentation and Samples Web site
The AdventureWorks database that is available at the SQL Server Developer Web site.
The SQL Server Database Engine samples that are available 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.

Building the Sample

If you have not already created the strong-name key file ExternalSampleKey.snk, generate the key file using the following instructions.

To generate a strong name key file

Open a Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft Visual Studio 2005, point to Visual Studio Tools, and then click Visual Studio 2005 Command Prompt.—Or—Open a.NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
At the command prompt, use the change directory (CD) command to change the current folder of the command prompt window to the Samples folder. Note: To determine the folder where samples are located, click Start, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <systemdrive_>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k ExternalSampleKey.snk ** Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.To build the sample, do the following:

Build the sample

Compile the sample by using Visual Studio 2005 and the provided Visual Studio solution, or by using MSBuild, which is included in the .NET Framework SDK 2.0. Run a command similar to the following at the command prompt: msbuild /nologo /verbosity:quiet /property:Configuration=Debug CS\HandlingLOBUsingCLR.sln
Make sure that the AdventureWorks database is installed.
If you did not install the SQL Server Database Engine samples in the default location, modify the path in the CREATE ASSEMBLY part of the script in Scripts\InstallCS.sql and Scripts\InstallVB.sql to refer to location where the samples were installed.
If you are not an administrator for the SQL Server instance you are using, you must have an administrator grant you CreateAssembly permission to complete the installation.
Open the scripts\installCS.sql or scripts\installVB.sql file, depending on whether you compiled the Visual C# project or the Visual Basic project, in SQL Server Management Studio. Run the script that is contained in the file, or run a command similar to the following at the command prompt: sqlcmd -E -I -i Scripts\InstallCS.sql
Removes any stored procedures that are about to be defined, if they exist.
Drops the assembly registration, if it already exists.
Registers the assembly.
Registers the CLR stored procedures.
Creates the Transact-SQL stored procedure called by one of the CLR stored procedures.

Running the Sample

To run the sample, do the following:

Run the sample

To read an image from the database, invoke a script similar to the following: exec GetPhotoFromDB 70, 'C:\Temp\', 'test6.gif' go Make sure the directory you specify exists.
To write an image into the database, invoke a script similar to the following: exec PutPhotoIntoDB 70, 'C:\Temp\', 'test1.gif' go Any errors will be reported to the error.log file in the directory that you specify. For scripts that are similar to the ones in this procedure, see the Scripts\test.sql file.

Removing the Sample

To remove the sample, do the following:

Remove the sample

Open the scripts\cleanup.sql file in Management Studio and run the script that is contained in the file. Or, run the following command at the command prompt: sqlcmd -E -I -i Scripts\cleanup.sql

Comments

Updated Wiki: SS2008!Readme_VerifyBackup

leilu — Fri, 27 Mar 2009 02:35:56 GMT

Readme_VerifyBackup Sample

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.
This sample demonstrates techniques for verifying a backup on a backup device to ensure the data can be used to restore the appropriate databases. By using SQL Server Management Object (SMO) capabilities of Microsoft SQL Server, this application lets users select the backup device and verify the contents of the selected backup. This sample provides a user interface that lets the user specify the SQL Server instance to connect to and whether to use Windows Authentication. The user can then select which database and backup file location and name.
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. Sample applications and assemblies should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

Requirements

This sample requires that the following components are installed.

.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.
The sample package and data files that it uses must be installed on the local hard disk drive.
The AdventureWorks database must be installed.
You must have administrative permissions on the AdventureWorks database.
You must compile the ServerConnect component first, because this sample has a dependency on the ServerConnect sample.
Run the script "CreateDevicesAndBackups.sql" to create Devices And Backups.

Location

If the code sample was installed to the default location, the sample is located in the following directory:
C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\SMO\VerifyBackup
The C# solution for the code sample is located in the CS directory, and the Visual Basic solution is located in the VB directory.

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

Building and using the sample using the Command Line Compiler

Open a .NET Framework or Microsoft Visual Studio 2005 command prompt. Use the change directory (CD) command to change the current directory of the command prompt window to the solution directory that you want to work in.
Type the following command to build either the C# or the Visual Basic version of the sample: for /r %f in (*.sln) do msbuild.exe "%f"

Building and using the sample from Microsoft Visual Studio 2005 (optional)

From the File menu in Microsoft Visual Studio 2005, click Open, click Project, and then open VerifyBackup.sln in the solution directory that you want to work in.
Press F5, or click Start on the Debug menu to compile and run the project. © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Readme_UtilityConversion

cmslydia — Fri, 20 Mar 2009 02:57:14 GMT

Readme_UtilityConversion Sample

08/06/2008 01:27:32

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 demonstrates techniques for implementing assembly functions (SQLCLR) in database applications. By using SQL Server common language runtime (CLR) capabilities of Microsoft SQL Server, this application lets users run CLR assembly code from within SQL Server. This sample provides sample code to perform various datatype conversions.
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. Sample applications and assemblies should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

Requirements

This sample requires that the following components are installed.

.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.
Integration Services.
The sample package and data files that it uses must be installed on the local hard disk drive.
The AdventureWorks OLTP database must be installed.
The AdventureWorks database must be attached.
You must have administrative permissions on the AdventureWorks database.
This sample is used by the LoadRegAssembly.exe from the LoadRegAssembly project. For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.

Location

If the code sample was installed to the default location, the sample is located in the following directory:
C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\SMO\UtilityConversion
The C# solution for the code sample is located in the CS directory, and the Visual Basic solution is located in the VB directory.

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

Building and using the sample using the Command Line Compiler

Open a .NET Framework or Microsoft Visual Studio 2005 command prompt. Use the change directory (CD) command to change the current directory of the command prompt window to the solution directory that you want to work in.
Type the following command to build either the C# or the Visual Basic version of the sample: for /r %f in (*.sln) do msbuild.exe "%f"

Building and using the sample from Microsoft Visual Studio 2005 (optional)

From the File menu in Microsoft Visual Studio 2005, click Open, click Project, and then open UtilityConversion.sln in the solution directory that you want to work in.
Press Ctrl+Shift+B, or click Build Solution on the Build menu to compile the sample. © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Readme_ServerConnect

cmslydia — Fri, 20 Mar 2009 02:51:24 GMT

Readme_ServerConnect Sample

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.
This sample demonstrates techniques for implementing SQL Server listing and login capabilities into database applications. By using SQL Server Management Object (SMO) capabilities of Microsoft SQL Server, this application lets users log on to the selected database. This sample provides a user interface that permits specifying the SQL Server instance to connect to and whether to use Windows Authentication.
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. Sample applications and assemblies should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

Requirements

This sample requires that the following components are installed.

.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.
The sample package and data files that it uses must be installed on the local hard disk drive.

For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.

Location

If the code sample was installed to the default location, the sample is located in the following directory:
C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\SMO\ServerConnect
The C# solution for the code sample is located in the CS directory, and the Visual Basic solution is located in the VB directory.

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

Building and using the sample using the Command Line Compiler

Open a .NET Framework or Microsoft Visual Studio 2005 command prompt. Use the change directory (CD) command to change the current directory of the command prompt window to the solution directory that you want to work in.
Type the following command to build either the C# or the Visual Basic version of the sample: for /r %f in (*.sln) do msbuild.exe "%f"

Building and using the sample from Microsoft Visual Studio 2005 (optional)

From the File menu in Microsoft Visual Studio 2005, click Open, click Project, and then open ServerConnect.sln in the solution directory that you want to work in.
Press Ctrl+Shift+B, or click Build Solution on the Build menu to compile the sample. © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Readme_ServerConnect

cmslydia — Fri, 20 Mar 2009 02:50:25 GMT

Readme_ServerConnect Sample

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.
This sample demonstrates techniques for implementing SQL Server listing and login capabilities into database applications. By using SQL Server Management Object (SMO) capabilities of Microsoft SQL Server, this application lets users log on to the selected database. This sample provides a user interface that permits specifying the SQL Server instance to connect to and whether to use Windows Authentication.
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. Sample applications and assemblies should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

Requirements

This sample requires that the following components are installed.

.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.
The sample package and data files that it uses must be installed on the local hard disk drive.

For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.

Location

If the code sample was installed to the default location, the sample is located in the following directory:
C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\SMO\ServerConnect
The C# solution for the code sample is located in the CS directory, and the Visual Basic solution is located in the VB directory.

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

Building and using the sample using the Command Line Compiler

Open a .NET Framework or Microsoft Visual Studio 2005 command prompt. Use the change directory (CD) command to change the current directory of the command prompt window to the solution directory that you want to work in.
Type the following command to build either the C# or the Visual Basic version of the sample: for /r %f in (*.sln) do msbuild.exe "%f"

Building and using the sample from Microsoft Visual Studio 2005 (optional)

From the File menu in Microsoft Visual Studio 2005, click Open, click Project, and then open ServerConnect.sln in the solution directory that you want to work in.
Press Ctrl{Shift}B, or click Build Solution on the Build menu to compile the sample. © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Readme_ServerConnect

cmslydia — Fri, 20 Mar 2009 02:49:10 GMT

Readme_ServerConnect Sample

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.
This sample demonstrates techniques for implementing SQL Server listing and login capabilities into database applications. By using SQL Server Management Object (SMO) capabilities of Microsoft SQL Server, this application lets users log on to the selected database. This sample provides a user interface that permits specifying the SQL Server instance to connect to and whether to use Windows Authentication.
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. Sample applications and assemblies should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

Requirements

This sample requires that the following components are installed.

.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.
The sample package and data files that it uses must be installed on the local hard disk drive.

For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.

Location

If the code sample was installed to the default location, the sample is located in the following directory:
C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\SMO\ServerConnect
The C# solution for the code sample is located in the CS directory, and the Visual Basic solution is located in the VB directory.

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

Building and using the sample using the Command Line Compiler

Open a .NET Framework or Microsoft Visual Studio 2005 command prompt. Use the change directory (CD) command to change the current directory of the command prompt window to the solution directory that you want to work in.
Type the following command to build either the C# or the Visual Basic version of the sample: for /r %f in (*.sln) do msbuild.exe "%f"

Building and using the sample from Microsoft Visual Studio 2005 (optional)

From the File menu in Microsoft Visual Studio 2005, click Open, click Project, and then open ServerConnect.sln in the solution directory that you want to work in.

Updated Wiki: SS2008!Readme_Tracer

cmslydia — Fri, 20 Mar 2009 02:25:33 GMT

Readme_Tracer Sample

11/05/2008 21:36:06

This sample demonstrates techniques for implementing profile trace from the local instance of SQL Server to the output console. Using SQL Server Trace Management objects (TMO), this console application can be used to display trace information from the local instance of SQL Server. This sample is not supported on a 64-bit platform.
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. Sample applications and assemblies should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

Requirements

This sample requires that the following components are installed.

.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.
Integration Services.
The sample package and data files that it uses must be installed on the local hard disk drive.
The AdventureWorks OLTP database must be installed.
The AdventureWorks database must be attached.
You must have administrative permissions on the AdventureWorks database. For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.

Location

If the code sample was installed to the default location, the sample is located in the following directory:
C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\SMO\Tracer
The C# solution for the code sample is located in the CS directory, and the Visual Basic solution is located in the VB directory.

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

Building and using the sample using the Command Line Compiler

Open a .NET Framework or Microsoft Visual Studio 2005 command prompt. Use the change directory (CD) command to change the current directory of the command prompt window to the solution directory that you want to work in.
Type the following command to build either the C# or the Visual Basic version of the sample: for /r %f in (*.sln) do msbuild.exe "%f"

Building and using the sample from Microsoft Visual Studio 2005 (optional)

From the File menu in Microsoft Visual Studio 2005, click Open, click Project, and then open Tracer.sln in the solution directory that you want to work in.

Updated Wiki: SS2008!Readme_LoadRegAssembly

cmslydia — Fri, 20 Mar 2009 02:15:56 GMT

Readme_LoadRegAssembly Sample

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.
This sample demonstrates techniques for implementing assembly registration capabilities into database applications. By using SQL Server Management Object (SMO) capabilities of Microsoft SQL Server, this application lets users register the assembly and create functions that call the assembly code. This sample provides a user interface that lets the user specify the SQL Server instance to connect to and whether to use Windows Authentication.
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. Sample applications and assemblies should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

Requirements

This sample requires that the following components are installed.

.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.
Integration Services.
The sample package and data files that it uses must be installed on the local hard disk drive.
The AdventureWorks OLTP database must be installed.
The AdventureWorks database must be attached.
You must have administrative permissions on the AdventureWorks database. For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.

Location

If the code sample was installed to the default location, the sample is located in the following directory:
C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\SMO\LoadRegAssembly
The C# solution for the code sample is located in the CS directory, and the Visual Basic solution is located in the VB directory.

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

Building and using the sample using the Command Line Compiler

Open a .NET Framework or Microsoft Visual Studio 2005 command prompt. Use the change directory (CD) command to change the current directory of the command prompt window to the solution directory that you want to work in.
Type the following command to build either the C# or the Visual Basic version of the sample: for /r %f in (*.sln) do msbuild.exe "%f"

Building and using the sample from Microsoft Visual Studio 2005 (optional)

From the File menu in Microsoft Visual Studio 2005, click Open, click Project, and then open LoadRegAssembly.sln in the solution directory that you want to work in.

Updated Wiki: SS2008!Readme_VerifyBackup

libinzhao — Thu, 19 Mar 2009 10:01:45 GMT

Readme_VerifyBackup Sample

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.
This sample demonstrates techniques for verifying a backup on a backup device to ensure the data can be used to restore the appropriate databases. By using SQL Server Management Object (SMO) capabilities of Microsoft SQL Server, this application lets users select the backup device and verify the contents of the selected backup. This sample provides a user interface that lets the user specify the SQL Server instance to connect to and whether to use Windows Authentication. The user can then select which database and backup file location and name.
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. Sample applications and assemblies should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

Requirements

This sample requires that the following components are installed.

.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.
Integration Services.
The sample package and data files that it uses must be installed on the local hard disk drive.
The AdventureWorks OLTP database must be installed.
The AdventureWorks database must be attached.
You must have administrative permissions on the AdventureWorks database.
You must compile the ServerConnect component first, because this sample has a dependency on the ServerConnect sample.
Run the script "CreateDevicesAndBackups.sql" to create Devices And Backups.

For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.

Location

If the code sample was installed to the default location, the sample is located in the following directory:
C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\SMO\VerifyBackup
The C# solution for the code sample is located in the CS directory, and the Visual Basic solution is located in the VB directory.

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

Building and using the sample using the Command Line Compiler

Open a .NET Framework or Microsoft Visual Studio 2005 command prompt. Use the change directory (CD) command to change the current directory of the command prompt window to the solution directory that you want to work in.
Type the following command to build either the C# or the Visual Basic version of the sample: for /r %f in (*.sln) do msbuild.exe "%f"

Building and using the sample from Microsoft Visual Studio 2005 (optional)

From the File menu in Microsoft Visual Studio 2005, click Open, click Project, and then open VerifyBackup.sln in the solution directory that you want to work in.

Updated Wiki: SS2008!Readme_BackRest

libinzhao — Thu, 19 Mar 2009 09:43:12 GMT

Readme_BackRest Sample

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.
This sample demonstrates techniques for implementing backup and restore capabilities in database applications. By using SQL Server Management Object (SMO) capabilities of Microsoft SQL Server, this application lets users backup and restore the selected database to a specific file on a user's hard disk drive. This sample provides a user interface that permits specifying the SQL Server instance to connect to and whether to use Windows Authentication. The user can then select the appropriate database and backup file location and name.
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. Sample applications and assemblies should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

Requirements

This sample requires that the following components are installed.

.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.
The sample package and data files that it uses must be installed on the local hard disk drive.
The AdventureWorks OLTP database must be installed.
The AdventureWorks database must be attached.
You must have administrative permissions on the AdventureWorks database.
You must compile the ServerConnect component first, because this sample has a dependency on the ServerConnect sample. For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.

Location

If the code sample was installed to the default location, the sample is located in the following directory:
C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\SMO\BackRest
The C# solution for the code sample is located in the CS directory, and the Visual Basic solution is located in the VB directory.

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

Building and using the sample using the Command Line Compiler

Open a .NET Framework or Microsoft Visual Studio 2005 command prompt. Use the change directory (CD) command to change the current directory of the command prompt window to the solution directory that you want to work in.
Type the following command to build either the C# or the Visual Basic version of the sample: for /r %f in (*.sln) do msbuild.exe "%f"

Building and using the sample from Microsoft Visual Studio 2005 (optional)

From the File menu, click Open, click Project, and then open BackRest.sln in the desired solution directory.

Updated Wiki: SS2008!Grouping Sets Report

cmslydia — Thu, 19 Mar 2009 06:52:58 GMT

Readme_Grouping Sets Report Sample

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.
This sample illustrates how to combine the SQL Server 2008 GROUPING SETS feature of Transact-SQL with the new Tablix capabilities of SQL Server 2008 Reporting Services to display the output of a GROUPING SETS query in a pivot-table-style format.
The GROUPING SETS feature allows you to write a single query which groups by multiple different sets of grouping columns, with complete control over what columns to group by. This can make the query easier to write and allow it to run faster than in prior SQL Server releases. Of course, it is desirable to render the output of a query in an appealing report format, and SQL Server Reporting Services is the tool of choice for that.
For more information, see Using GROUP BY with ROLLUP, CUBE, and GROUPING SETS in SQL Server 2008 Books Online.

Scenario

The goal of this sample is to produce a pivot-table-style report that looks like this:
The report shows the number of distinct products sold per country for each quarter. It also shows the total number of distinct products sold for all countries for each quarter, as well as the total number of distinct products per country for six quarters. The distinct counts are based on results from the following query.


{" USE AdventureWorksDW2008;GOSELECT D.CalendarYear, D.CalendarQuarter, T.SalesTerritoryCountry, COUNT(DISTINCT F.ProductKey) AS DistinctProductCountFROM dbo.FactResellerSales F INNER JOIN dbo.DimDate D ON F.OrderDateKey = D.DateKey INNER JOIN dbo.DimSalesTerritory T ON F.SalesTerritoryKey = T.SalesTerritoryKey WHERE D.CalendarYear IN ('2003', '2004') GROUP BY GROUPING SETS ( (D.CalendarYear, D.CalendarQuarter, T.SalesTerritoryCountry), (D.CalendarYear, D.CalendarQuarter), (T.SalesTerritoryCountry),());GO "}

{" USE AdventureWorksDW2008;GOSELECT D.CalendarYear, D.CalendarQuarter, T.SalesTerritoryCountry, COUNT(DISTINCT F.ProductKey) AS DistinctProductCountFROM dbo.FactResellerSales F INNER JOIN dbo.DimDate D ON F.OrderDateKey = D.DateKey INNER JOIN dbo.DimSalesTerritory T ON F.SalesTerritoryKey = T.SalesTerritoryKey WHERE D.CalendarYear IN ('2003', '2004') GROUP BY GROUPING SETS ( (D.CalendarYear, D.CalendarQuarter, T.SalesTerritoryCountry), (D.CalendarYear, D.CalendarQuarter), (T.SalesTerritoryCountry),());GO "}

The approach used in this sample is best for non-additive aggregates like COUNT(DISTINCT…) , STDEV , and AVG, whose aggregate results do not support commutative and associative properties. For example, given the set (1, 1, 2, 2), COUNT ( DISTINCT (1, 1) ) + COUNT ( DISTINCT (2, 2) ) = 2, but COUNT ( DISTINCT (1, 2) ) + COUNT ( DISTINCT ( 1, 2 ) ) = 4.
If you are using a grouping query that uses an additive aggregate (e.g. COUNT , SUM , MIN , or MAX ), you can use a query similar to the one below, which uses COUNT without grouping sets, and use the Tablix control in SQL Server 2008 Reporting Services to produce row and column aggregates and an overall aggregate.


{" USE AdventureWorksDW2008;GOSELECT D.CalendarYear, D.CalendarQuarter, T.SalesTerritoryCountry, COUNT(F.SalesAmount) as SalesAmountFROM dbo.FactResellerSales F INNER JOIN dbo.DimDate D ON F.OrderDateKey = D.DateKey INNER JOIN dbo.DimSalesTerritory T ON F.SalesTerritoryKey = T.SalesTerritoryKeyWHERE D.CalendarYear IN ('2003', '2004')GROUP BY D.CalendarYear, D.CalendarQuarter, T.SalesTerritoryCountry;GO "}

{" USE AdventureWorksDW2008;GOSELECT D.CalendarYear, D.CalendarQuarter, T.SalesTerritoryCountry, COUNT(F.SalesAmount) as SalesAmountFROM dbo.FactResellerSales F INNER JOIN dbo.DimDate D ON F.OrderDateKey = D.DateKey INNER JOIN dbo.DimSalesTerritory T ON F.SalesTerritoryKey = T.SalesTerritoryKeyWHERE D.CalendarYear IN ('2003', '2004')GROUP BY D.CalendarYear, D.CalendarQuarter, T.SalesTerritoryCountry;GO "}

It is easiest to compute aggregates for (Year,Quarter), (Country) and () groupings inside Reporting Services in this situation, rather than modify the query to use GROUPING SETS.

Languages

Transact-SQL

Prerequisites

Before you run this sample, install the following software.

SQL Server 2008 and the following components:
Database Engine
Reporting Services
Business Intelligence Development Tools
Visual Studio
samples for SQL Server 2008. The default installation directory is C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Query Processing\Grouping Sets Report.
AdventureWorksDW2008 sample database for SQL Server 2008. You can obtain this from the SQL Server Samples site on Codeplex Web site. For example, if you are using the x64 architecture, you can download SQL2008.AdventureWorksDWBI_v2008.x64.msi to install AdventureWorksDW2008. For more information, see Considerations for Installing SQL Server Samples and Sample Databases in SQL Server 2008 Books Online.

Running the Sample

The following steps show how to run the Grouping Sets Matrix Sample.rdl script to see the report based on the AdventureWorksDW 2008 sample database.

From the Start menu, open My Computer and navigate to the installation directory, C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Query Processing\Grouping Sets Report.
Double-click "Grouping Sets Report Project.sln" to open the project in Visual Studio.
Expand Shared Data Sources, double-click AdventureWorksDW1.rds and adjust the settings in the dialog box so that you can connect to your AdventureWorksDW 2008 database.
In Solution Explorer, expand the Reports folder, and double-click Grouping Sets Matrix Sample.rdl.
Click the preview tab to see the report. Note the following interesting things about the sample: A new column group and row group have been added outside the default groups. These are named STCountry2 and CY2.

If you right-click these in the above location, click Edit Group, and then edit the filters for the groups, you will see that source query rows with NULL grouping keys are filtered in different ways to produce the column, row, and overall distinct counts.

Summary

This sample showed how to create a pivot table report over a GROUPING SETS query using SQL Server 2008 Reporting Services (SSRS). Use this approach for non-additive aggregates such as COUNT(DISTINCT…), AVG, and STDEV. For additive aggregates such as SUM and COUNT, compute the row, column, and grand totals in Reporting Services instead, and do not use GROUPING SETS in your Transact-SQL query.
© 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Supplementary-Aware String Manipulation

leilu — Thu, 19 Mar 2009 05:54:54 GMT

Readme_Supplementary-Aware String Manipulation Sample

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 StringManipulate sample for Microsoft SQL Server demonstrates supplementary character aware string processing. This sample shows the implementation of five Transact-SQL string functions that provide the same string manipulation functions as the built-in functions, but with additional supplementary character-aware capability to handle both Unicode and supplementary character strings. The five functions are lens(), lefts(), rights(), subs() and replace_s() which are equivalent to the built-in functions LEN(), LEFT(), RIGHT(), SUBSTRING() and REPLACE() string functions.

Note:
When compiling common language runtime (CLR) integration samples, the path of the version of the Microsoft .NET Framework compiler that was included with SQL Server must be the first Framework directory in the PATH environment variable. The location of the compiler that was included with SQL Server is either drive:\WINNT\Microsoft.NET\Framework\v2.0.xxxxx or _ drive:\Windows\Microsoft.NET\Framework\v2.0.xxxxx_, where _ drive_ is the installation drive and xxxxx is the version of the .NET Framework that was included with SQL Server.

Note:

When compiling common language runtime (CLR) integration samples, the path of the version of the Microsoft .NET Framework compiler that was included with SQL Server must be the first Framework directory in the PATH environment variable. The location of the compiler that was included with SQL Server is either drive:\WINNT\Microsoft.NET\Framework\v2.0.xxxxx or _ drive:\Windows\Microsoft.NET\Framework\v2.0.xxxxx_, where _ drive_ is the installation drive and xxxxx is the version of the .NET Framework that was included with SQL Server.

Default Location:__C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\CLR\StringManipulate
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

A developer wants to accurately manipulate Unicode strings that contain supplementary characters.

Languages

Transact-SQL, Visual C# and Visual Basic.

Features

The StringManipulate sample uses the following features of Microsoft SQL Server.

Application Area	Features
Overall	CLR user-defined function

Prerequisites

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

Microsoft SQL Server or Microsoft SQL Server Express. You can obtain SQL Server Express free of charge from the SQL Server Express Documentation and Samples Web site
The AdventureWorks database that is available at the SQL Server Developer Web site.
The SQL Server Database Engine samples that are available 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.
Ext-B font must be installed on the computer for the correct characters to appear in the SQL Server Management Studio results window. To change the font in the results window, in Management Studio, on the Tools menu, click Options, expand Environment, and then click Fonts and Colors. Set the font to MingLiU_ExtB for Text Results and/or Grid Results. You must close and then reopen Management Studio for the changes to take effect.

Building the Sample

If you have not already created the strong-name key file ExternalSampleKey.snk, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft Visual Studio 2005, point to Visual Studio Tools, and then click Visual Studio 2005 Command Prompt.—Or—Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
At the command prompt, use the change directory (CD) command to change the current folder of the command prompt window to the Samples folder. Note: To determine the folder where samples are located, click Start, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <systemdrive_>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k ExternalSampleKey.snk ** Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.To build the sample, do the following:

Build the sample

Compile the sample by using Visual Studio 2005 and the provided Visual Studio solution, or by using Microsoft MSBuild, which is included in the .NET Framework SDK 2.0. Run a command similar to the following at the command prompt: msbuild /nologo /verbosity:quiet /property:Configuration=Debug CS\StringManipulate.sln
Make sure that the AdventureWorks database is installed, or, if necessary, create the database in which you want to install the samples.
If you did not install the SQL Server Database Engine samples in the default location, modify the path in the CREATE ASSEMBLY part of the script in Scripts\InstallCS.sql and Scripts\InstallVB.sql to refer to location where the samples were installed.
Open the scripts\installCS.sql or scripts\installVB.sql file, depending on whether you compiled the Visual C# project or the Visual Basic project, in Management Studio. Run the script that is contained in the file, or run a command similar to the following at the command prompt: sqlcmd -E -I -i Scripts\InstallCS.sql This file contains script to install and register the sample CLR objects into SQL Server.

Running the Sample

To run the sample, do the following:

Run the sample

Open the scripts\test.sql file in SQL Server Management Studio. Run the script that is contained in the file, or run the following at the command prompt: sqlcmd -E -I -i Scripts\test.sql This script invokes the string manipulation sample from Transact-SQL.

Removing the Sample

To remove the StringManipulate sample, do the following:

Remove the sample

Open the scripts\cleanup.sql file in SQL Server Management Studio. Run the script that is contained in the file, or run the following at the command prompt: sqlcmd -E -I -i Scripts\cleanup.sql This script removes the sample.

Comments

The CLR for SQL Server 2008 or SQL Server Express must be enabled for this sample to work correctly.
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. Sample applications and assemblies should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.
© 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Data Warehouse Tuning Techniques Sample

cmslydia — Thu, 19 Mar 2009 05:53:38 GMT

Readme_Data Warehouse Tuning Techniques Sample

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.
This sample demonstrates techniques for tuning data warehouse queries to improve query performance. In most cases, the query optimizer creates high-quality query plans. However, for specific query patterns, you can improve the query plan by manually tuning the query. Here, we present three such scenarios and their tuning techniques.
The run times cited below were recorded by using an AMD Athlon 64 X2 Dual-Core 4200 CPU with 4 GB of RAM, running Windows Server 2008 and SQL Server 2008. The queries were run from SQL Server Management Studio.

Languages

Transact-SQL

Prerequisites

Before you run this sample, install the following software.

SQL Server 2008 and the following components:
The Database Engine
SQL Server Management Studio
Database Engine samples for SQL Server 2008. The default installation directory is C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Query Processing\Data Warehouse Tuning Techniques.
AdventureWorksDW2008 sample database for SQL Server 2008. For example, if you are using the x64 architecture, you can download SQL2008.AdventureWorksDWBI_v2008.x64.msi to install AdventureWorksDW2008 . For more information about installing the samples, see Considerations for Installing SQL Server Samples and Sample Databases in SQL Server 2008 Books Online.

Running the Sample

Prepare the Database

Run Prepare.sql. Note that, depending on your machine performance, this might take around one hour or more (run time on test machine was 54 minutes). Note that the extended database will need around 25 GB of drive space.

Example 1: Tune Join Into Semi-Join

Open SemiJoin.sql in SQL Server Management Studio.
Execute Original Query. Notice the time it takes to execute the query. On the test machine, the query took 2 minutes, 8 seconds.
Execute Tuned Query. Notice the time it takes to execute the query. The execution time should be significantly less than that of the original query. On the test machine, the query took 1 minute, 1 second.

Example 2: Split Distinct Aggregates

Open CountDistinct.sql in SQL Server Management Studio.
Execute Original Query. Notice the time it takes to execute the query. On the test machine, the query took 3 minutes, 5 seconds.
Execute Tuned Query. Notice the time it takes to execute the query. The execution time should be significantly less than that of the original query. On the test machine, the query took 1 minute, 18 seconds.

Example 3: Reuse Common Expressions

Open CommonExpression.sql in SQL Server Management Studio.
Execute Original Query. Notice the time it takes to execute the query. On the test machine, the query took 2 minutes, 10 seconds.
Execute Tuned Query. Notice the time it takes to execute the query. The execution time should be significantly less than the original query. On the test machine, the query took 1 minute, 18 seconds. © 2008 Microsoft Corporation. All rights reserved.

MSFTEngProdSamples Wiki & Documentation Rss Feed

Updated Wiki: Home

CLR

Full Text Search

SMO

Updated Wiki: SS2005!Currency Web Service Sample

Currency Web Service Sample

Scenario

Languages

Features

Prerequisites

Building the Sample

To generate a strong name key file

Build the sample

Running the Sample

Run the sample

Removing the Sample

Remove the sample

Comments

Updated Wiki: SS2008!Currency Web Service Sample

Readme_Currency Web Service Sample

Scenario

Languages

Features

Prerequisites

Building the Sample

Build the sample

Running the Sample

Run the sample

Removing the Sample

Remove the sample

Comments

See Also

Concepts

Other Resources

Help and Information

Updated Wiki: SS2008!Data Warehouse Tuning Techniques Sample

Readme_Data Warehouse Tuning Techniques Sample

Languages

Prerequisites

Running the Sample

Prepare the Database

Example 1: Tune Join Into Semi-Join

Example 2: Split Distinct Aggregates

Example 3: Reuse Common Expressions

Updated Wiki: SS2008!Readme_ServiceBrokerConfiguration

Readme_ServiceBrokerConfiguration Sample

Requirements

Location

Building the Sample

To generate a strong name key file

Build the Visual Studio Solution

Set up SQL Server sample database and sample XML schemas

Set up SQL Server master keys (optional)

Running the Sample

To run the sample

To connect to a local SQL Server instance

To configure the sample for a new database.

To create MessageTypes

To create a contract

To create queues

To create services without RemoteServiceBinding enabled

To create services with RemoteServiceBinding enabled

To enable anonymous access for a Remote Service

To create a Target Instance Endpoint

To set a script export path

To export an object

To export a Service definition to a file

To drop an object

To alter an object

To query data describing an object

Removing the Sample

To drop services

To drop queues

To drop contracts

To drop MessageTypes

To drop a Target Instance Endpoint

Updated Wiki: SS2008!Large Binary Object (LOB) Handling

Readme_Large Object (LOB) Handling Sample

Scenario