Microsoft SQL Server Product Samples: End to End

Source code checked in, #11622

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

Adding 'Katmai:June 2008 RC0'

Updated Wiki: SS2008!Service Broker Ordering Service Sample

bonniefe — Wed, 11 Jun 2008 00:44:46 GMT

Readme_Service Broker Ordering Service Sample

6/10/2008 1:32:27 AM

This sample works only with SQL Server 2005 and SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2005.
The Adventure Works Storefront sample accepts an online order and returns a predefined ship date in the order status screen. This sample adds backend order processing capabilities to Adventure Works Storefront.
This sample illustrates the fundamental concepts of Service Broker and allows you to view the Transact-SQL scripts used to run the sample, and the results of executing that script in the Service Broker tables.

Note:
This sample requires the Adventure Works Storefront sample. For more information about installing the Storefront sample, see Readme_Storefront.

Scenario

A developer wants to implement a backend order processing system for an e-commerce Web site.

Languages

Transact-SQL, XML, XSD, and Visual C#.

Prerequisites

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

SQL Server, including the following components:
SQL Server Database Engine
SQL Server Management Studio
AdventureWorks sample database
Database Engine Samples
Adventure Works Storefront sample
.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

The C# source code is built with the Storefront sample. To create the SQL Server portion of the sample, follow the steps below.
All Service Broker applications are composed of a collection of SQL Server objects that provide the service functionality. In this step, you will create the Service Broker environment, consisting of the XML schema collections, message types, contracts, queues, and services required to operate it.

Set up the Service Broker environment

Run the Transact-SQL script to set up Service Broker. You can run installorderingservice.cmd, or you can run the individual scripts.
Run installorderingservice.cmd. The default folder is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\Storefront.
Alternatively, you can run the individual scripts in the following order:
OrderingServiceScripts\Setup.sql
OrderingServiceScripts\SetupOrderingServiceProgram.sql
OrderingServiceScripts\SetupPurchasingServiceProgram.sql
OrderingServiceScripts\SetupManufacturingServiceProgram.sql
OrderingServiceScripts\SetupShippingServiceProgram.sql
Configure the Storefront.
Edit the web.config file, located in the directory C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\Storefront\CS\StoreCSVS. Find the ExtendedOrderProcessing attribute, and change the value to true. After making the change, this element should look like the element below: <add key="ExtendedOrderProcessing" value="true"/>

Running the Sample

In this exercise, you will go to the Adventure Works Web site and order an in-stock item. Because the item is in stock, the Ordering Service sends a Shipping Request message to the Shipping Service, and the Shipping Service responds back to the Ordering Service with a Shipping Accept message. Follow the steps in this exercise to see this process in SQL Server Management Studio.

Order an in-stock item

In Internet Explorer, open http://localhost/storeCSVS/ .
In the left pane, expand Accessories, and then expand Helmets. Select Sports-100 Helmet, Red, and then click Add to Cart. On the Shopping Cart page, click Final Check Out. On the next page, click Submit.
In SQL Server Management Studio, run AdministrationAndTroubleShooting.sql. The default folder is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\Storefront\OrderingServiceScripts. The result shows the processing flow, including Server Broker queue tables, ordering state, and audit logs.
Run purge.sql to clean up contents in queues and tables before continuing on to the next exercise.

Order an out-of-stock buy item

In Internet Explorer, open http://localhost/storeCSVS/ .
In the left menu, expand Clothing. Click the submenu item Tights. Pick Women’s Tights, M, and then click Add to Cart. In the next page, click Final Check Out. In the next page, click Submit.
In SQL Server Management Studio, run AdministrationAndTroubleShooting.sql. The default folder is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\Storefront\OrderingServiceScripts. The result shows the processing flow, including Server Broker queue tables, ordering state, and audit logs.
Run purge.sql to clean up contents in queues and tables before continuing on to the next exercise.

Order an out-of-stock make item ready for manufacturing

In Internet Explorer, open http://localhost/storeCSVS/ .
On the left menu, expand Components. Click Mountain Frames, select HL Mountain Frame – Black, 38, and then click Add to Cart. On the next page, click Final Check Out. On the next page, click Submit.
In SQL Server Management Studio, run AdministrationAndTroubleShooting.sql. The default folder is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\Storefront\OrderingServiceScripts. The result shows the processing flow, including Server Broker queue tables, ordering state, and audit logs.
Run purge.sql to clean up contents in queues and tables before continuing on to the next exercise.

Remove the sample

Run uninstallorderingservice.cmd. The default folder is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\Storefront. © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2005!Service Broker Ordering Service Sample

bonniefe — Wed, 11 Jun 2008 00:44:19 GMT

Service Broker Ordering Service Sample

6/10/2008 4:38:07 PM

The Adventure Works Storefront sample accepts an online order and returns a predefined ship date in the order status screen. This sample adds backend order processing capabilities to Adventure Works Storefront.
This sample illustrates the fundamental concepts of Service Broker. It lets you view the Transact-SQL scripts that are used to run the sample, and the results of executing that script in the Service Broker tables.

Note:
This sample requires the Adventure Works Storefront sample. For more information about installing the Storefront sample, see Readme_Storefront. By default, the Adventure Works Storefront sample is installed at C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\\Storefront.

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.

Scenario

A developer wants to implement a backend order processing system for an e-commerce Web site.

Languages

Transact-SQL, XML, XSD, and Visual C#.

Prerequisites

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

SQL Server 2005, including the following components:
SQL Server Database Engine
SQL Server Management Studio
AdventureWorks sample database
Database Engine Samples
Adventure Works Storefront sample
.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

Set up the Service Broker environment

Run the Transact-SQL script to set up Service Broker. You can run installorderingservice.cmd, or you can run the individual scripts.
Run installorderingservice.cmd. The default folder is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\\Storefront.
Alternatively, you can run the individual scripts in the following order:
OrderingServiceScripts\Setup.sql
OrderingServiceScripts\SetupOrderingServiceProgram.sql
OrderingServiceScripts\SetupPurchasingServiceProgram.sql
OrderingServiceScripts\SetupManufacturingServiceProgram.sql
OrderingServiceScripts\SetupShippingServiceProgram.sql
Configure the Storefront.
Edit the web.config file, located in the directory C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\\Storefront\CS\StoreCSVS. Find the ExtendedOrderProcessing attribute, and change the value to true. After making the change, this element should look like the element below: <add key="ExtendedOrderProcessing" value="true"/>

Running the Sample

In this exercise, you will visit the Adventure Works Web site and order an in-stock item. Because the item is in stock, the Ordering Service sends a Shipping Request message to the Shipping Service. The Shipping Service then responds to the Ordering Service with a Shipping Accept message. Follow the steps in this exercise to see this process in SQL Server Management Studio.

Order an in-stock item

In Internet Explorer, open http://localhost/storeCSVS/ .
In the left pane, expand Accessories, and then expand Helmets. Select Sports-100 Helmet, Red, and then click Add to Cart. On the Shopping Cart page, click Final Check Out. On the next page, click Submit.
In SQL Server Management Studio, run AdministrationAndTroubleShooting.sql. The default folder is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\\Storefront\OrderingServiceScripts. The result shows the processing flow, including Service Broker queue tables, ordering state, and audit logs.
Run purge.sql to clean up contents in queues and tables before continuing on to the next exercise.

Order an out-of-stock buy item

In Internet Explorer, open http://localhost/storeCSVS/ .
In the left menu, expand Clothing. Click the submenu item Tights. Pick Women’s Tights, M, and then click Add to Cart. In the next page, click Final Check Out. In the next page, click Submit.
In SQL Server Management Studio, run AdministrationAndTroubleShooting.sql. The default folder is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\\Storefront\OrderingServiceScripts. The result shows the processing flow, including Service Broker queue tables, ordering state, and audit logs.
Run purge.sql to clean up contents in queues and tables before continuing on to the next exercise.

Order an out-of-stock make item ready for manufacturing

In Internet Explorer, open http://localhost/storeCSVS/ .
On the left menu, expand Components. Click Mountain Frames, select HL Mountain Frame – Black, 38, and then click Add to Cart. On the next page, click Final Check Out. On the next page, click Submit.
In SQL Server Management Studio, run AdministrationAndTroubleShooting.sql. The default folder is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\\Storefront\OrderingServiceScripts. The result shows the processing flow, including Service Broker queue tables, ordering state, and audit logs.
Run purge.sql to clean up contents in queues and tables before continuing on to the next exercise.

Remove the sample

Run uninstallorderingservice.cmd. The default folder is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\\Storefront. © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Readme_Storefront

bonniefe — Wed, 11 Jun 2008 00:43:48 GMT

Readme_Storefront

6/10/2008 1:32:27 AM

This sample works only with SQL Server 2005 and SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2005.
The Storefront sample for the Adventure Works Cycles sample database in SQL Server demonstrates how to build a simple Internet retail application by using SQL Server, ADO.NET, and ASP.NET. This document describes how to install the SQL Server version of the sample application.
This sample works with the AdventureWorks sample database, which is included with SQL Server. Updates for both the database and this sample are available to download at the CodePlex Web site.
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.
The default installation directory is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\Storefront\.

Scenario

A developer wants to implement an e-commerce Web site. The Web site should offer additional product recommendations based on the contents of the shopping cart (product up sell).

Languages

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

Features

The Storefront sample uses the following features of SQL Server:

Application Area	Features
Demographics	XML, XSD
Globalization	Common language runtime user-defined function, common language runtime user-defined type
Overall	ADO.NET, Transact-SQL, AdventureWorks sample database

Prerequisites

Before running this sample, make sure that SQL Server is installed, including the following components:

SQL Server Database Engine
SQL Server Management Studio
AdventureWorks SP1 sample database
Database Engine Samples
The AdventureWorks CLR sample. By default, this is placed in C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\CLR\AdventureWorks when you install Database Engine Samples. See the readme file for this sample for additional installation instructions.
.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 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.

To build the sample, do the following:

Step 1: Install the sample and configure IIS

Alter the permissions of the folder where this sample is installed so it may be accessed by the user under which IIS runs. See the default installation directory above for the location of this folder. By default IIS runs under machinename\ASPNET for IIS 5.1 (Windows XP) and Network Service for IIS 6.0 (Windows 2003).
If you intend to compile by using MSBuild instead of Visual Studio, create the StoreCSVS v-root if it does not already exist by performing the following steps:

#
Right-click the StoreCSVS folder in C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\Storefront\CS\ and select Properties.

In the StoreCSVS Properties page, go to the Web Sharing tab and select Share this folder.
On the Edit Alias page, make sure Read is selected as the default Access permission and Script is selected as the default Application permission, and then click OK.
If you have not already enabled the Default.aspx page on this server, you can do so by performing the following steps:
Open Internet Information Services (IIS) Manager and expand the local computer in the explorer in the left pane.
Right-click StoreCSVS and click Properties. StoreCSVS should be listed under Default Web Site in Web Sites. If you have left IIS Manager open from a previous step, you might need to click Action and then click Refresh to see the newly added v-root.
Ensure that the ASP.NET version selected for the StoreCSVS virtual directory is 2.0.xxxxx where xxxxx is the build version.
On the StoreCSVS Properties page, click the Documents tab, and then select Enable default content page. If Default.aspx is not listed as a content page, click Add.
On the Add Content page, type Default.aspx, click OK, and then click OK again.

Step 2: Build the sample

In Visual Studio
Open the CS\StoreCSVS.sln solution file.
On the Build menu, click Rebuild Solution.
If you do not have Visual Studio, you can use MSBuild, which is distributed with the .NET Framework SDK 2.0
Open a .NET Framework SDK 2.0 command prompt window.
Change the directory to the Storefront sample directory.
Run this command: msbuild /property:configuration=debug CS\StoreCSVS.sln

Step 3: Configure SQL Server

Install the Storefront sample stored procedures by running the AWStore.sql script file. You can do this either by using Management Studio or by using the sqlcmd utility. The script file is located in the Scripts directory.
To run the script file by using Management Studio, on the File menu, click Open, locate the Scripts folder, select the AWStore.sql file, and then run the contents of the file.
To run the script file by using the sqlcmd utility, at the command prompt, change the directory to the folder where the AWStore.sql file is located, and then run the following command: sqlcmd -E -I -i awstore.sql

Step 4: Enable the OLAP-based product upsell scenario

Open the Analysis Services project in <drive>:\Program Files\Microsoft SQL Server\100\Tools\Samples\AdventureWorks Analysis Services Project\Adventure Works.sln.
Deploy the project.
In Management Studio, click Connect in Object Explorer, and then click Analysis Server.
Click Connect in the dialog box that appears.
Right-click the new top level Analysis Server node that is displayed in the Object Explorer tree control. The node will be similar to COMPUTERNAME. In Analysis Services, the node will be similar to Domain\User.
Click Properties.
Click the *Security *page.
Click Add.
Type NETWORK SERVICE .
Click OK twice.

Running the Sample

To run the sample, do the following:

Step 1: Browse the Web site

Open Internet Explorer and type http://localhost/storecsvs in the address bar. With this application, you can perform a variety of real-world Web application tasks, including the following:
Browse the tree control of the product categories.
Find out what products are offered and available.
Register a fictitious user on the system, including adding fictitious demographic information.
Add items to your shopping cart.
Go through the checkout process.
View previously completed orders using the account icon.
Use the Services icon to browse Web services, or the Search text box to find products.

Step 2: Modify the installed sample and recompile (Optional)

Remove the reference to the StoreClientComponents DLL and PDB files from the bin folder for the Web site.
Add the reference to the StoreClientComponents DLL by selecting the Web site project, and then using the Web Site/References menu item.
Save the project.
Delete the StoreCSVS folder and its contents from the Temporary ASP.NET Files folder by using the following procedure:
Exit Visual Studio 2005.
Stop IIS.
Delete the StoreCSVS folder from the drive:\WINNT\Microsoft.NET\Framework\v2.0.xxxxx\Temporary ASP.NET Files folder.
Empty the Recycle Bin.
Start IIS. It is not necessary to recompile the sample to run it.

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 contents of the file.

Comments

The common language runtime for SQL Server must be enabled for this sample to run correctly.

Updated Wiki: SS2005!Readme_Storefront

bonniefe — Wed, 11 Jun 2008 00:43:09 GMT

Readme_Storefront

6/10/2008 4:38:07 PM

Updated: 14 April 2006
The Storefront sample for the Adventure Works Cycles sample database in SQL Server 2005 demonstrates how to build a simple Internet retail application by using SQL Server, ADO.NET, and ASP.NET. This document describes how to install the SQL Server 2005 version of the sample application.
This sample works with the AdventureWorks sample database, which is included with SQL Server 2005. Updates for both the database and this sample are available to download at the CodePlex Web site.
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.
The default installation directory is drive:\Program Files\Microsoft SQL Server\90\Samples\Integrated Samples\Storefront\.

Scenario

A developer wants to implement an e-commerce Web site. The Web site should offer additional product recommendations based on the contents of the shopping cart (product up sell).

Languages

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

Features

The Storefront sample uses the following features of SQL Server 2005:

Application Area	Features
Demographics	XML, XSD
Globalization	Common language runtime user-defined function, common language runtime user-defined type
Overall	ADO.NET, Transact-SQL, AdventureWorks sample database

Prerequisites

Before running this sample, make sure that SQL Server 2005 SP1 is installed, including the following components:

SQL Server Database Engine
SQL Server Management Studio
AdventureWorks SP1 sample database
Database Engine Samples
The AdventureWorks CLR sample. By default, this is placed in C:\Program Files\Microsoft SQL Server\90\Samples\Engine\Programmability\CLR\AdventureWorks when you install Database Engine Samples. See the readme file for this sample for additional installation instructions.
.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 files SampleKey.snk and UnsafeSampleKey.snk, generate the key files by using the following procedure.

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 .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 commands to generate the key files: sn -k SampleKey.snk ** sn -k UnsafeSampleKey.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:

Step 1: Install the sample and configure IIS

Alter the permissions of the folder where this sample is installed so it may be accessed by the user under which IIS runs. See the default installation directory above for the location of this folder. By default IIS runs under machinename\ASPNET for IIS 5.1 (Windows XP) and Network Service for IIS 6.0 (Windows 2003).
If you intend to compile by using MSBuild instead of Visual Studio, create the StoreCSVS v-root if it does not already exist by performing the following steps:
Right-click the StoreCSVS folder in drive:\Program Files\Microsoft SQL Server\90\Samples\Integrated Samples\Storefront\CS\ and select Properties.
In the StoreCSVS Properties page, go to the Web Sharing tab and select Share this folder.
On the Edit Alias page, make sure Read is selected as the default Access permission and Script is selected as the default Application permission, and then click OK.
If you have not already enabled the Default.aspx page on this server, you can do so by performing the following steps:
Open Internet Information Services (IIS) Manager and expand the local computer in the explorer in the left pane.
Right-click StoreCSVS and click Properties. StoreCSVS should be listed under Default Web Site in Web Sites. If you have left IIS Manager open from a previous step, you might need to click Action and then click Refresh to see the newly added v-root.
Ensure that the ASP.NET version selected for the StoreCSVS virtual directory is 2.0.xxxxx where xxxxx is the build version.
On the StoreCSVS Properties page, click the Documents tab, and then select Enable default content page. If Default.aspx is not listed as a content page, click Add.
On the Add Content page, type Default.aspx, click OK, and then click OK again.

Step 2: Build the sample

In Visual Studio
Open the CS\StoreCSVS.sln solution file.
On the Build menu, click Rebuild Solution.
If you do not have Visual Studio, you can use MSBuild, which is distributed with the .NET Framework SDK 2.0
Open a .NET Framework SDK 2.0 command prompt window.
Change the directory to the Storefront sample directory.
Run this command: msbuild /property:configuration=debug CS\StoreCSVS.sln

Step 3: Configure SQL Server

Install the Storefront sample stored procedures by running the AWStore.sql script file. You can do this either by using Management Studio or by using the sqlcmd utility. The script file is located in the Scripts directory.
To run the script file by using Management Studio, on the File menu, click Open, locate the Scripts folder, select the AWStore.sql file, and then run the contents of the file.
To run the script file by using the sqlcmd utility, at the command prompt, change the directory to the folder where the AWStore.sql file is located, and then run the following command: sqlcmd -E -I -i awstore.sql

Step 4: Enable the OLAP-based product upsell scenario

Open the Analysis Services project in drive:\Program Files\Microsoft SQL Server\90\Tools\Samples\AdventureWorks Analysis Services Project\Adventure Works.sln.
Deploy the project.
In Management Studio, click Connect in Object Explorer, and then click Analysis Server.
Click Connect in the dialog box that appears.
Right-click the new top level Analysis Server node that is displayed in the Object Explorer tree control. The node will be similar to COMPUTERNAME. In Microsoft Analysis Server 9.0, the node will be similar to Domain\User.
Click Properties.
Click the *Security *page.
Click Add.
Type NETWORK SERVICE .
Click OK twice.

Running the Sample

To run the sample, do the following:

Step 1: Browse the Web site

Open Internet Explorer and type http://localhost/storecsvs in the address bar. With this application, you can perform a variety of real-world Web application tasks, including the following:
Browse the tree control of the product categories.
Find out what products are offered and available.
Register a fictitious user on the system, including adding fictitious demographic information.
Add items to your shopping cart.
Go through the checkout process.
View previously completed orders using the account icon.
Use the Services icon to browse Web services, or the Search text box to find products.

Step 2: Modify the installed sample and recompile (Optional)

Remove the reference to the StoreClientComponents DLL and PDB files from the bin folder for the Web site.
Add the reference to the StoreClientComponents DLL by selecting the Web site project, and then using the Web Site/References menu item.
Save the project.
Delete the StoreCSVS folder and its contents from the Temporary ASP.NET Files folder by using the following procedure:
Exit Visual Studio 2005.
Stop IIS.
Delete the StoreCSVS folder from the drive:\WINNT\Microsoft.NET\Framework\v2.0.xxxxx\Temporary ASP.NET Files folder.
Empty the Recycle Bin.
Start IIS. It is not necessary to recompile the sample to run it.

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 contents of the file.

Comments

The common language runtime for SQL Server 2005 must be enabled for this sample to run correctly.

Change History

Release	History
5 December 2005	Changed content: Changed instructions for generating a key file, including the name and location of the key file.
14 April 2006	Changed content: Changed instruction for generating a key file to include a second key file. Changed prerequisites to indicate that SP1 is required because of AdventureWorks database changes.

Updated Wiki: SS2008!Readme_ReviewWatcher

bonniefe — Wed, 11 Jun 2008 00:42:37 GMT

Readme_ReviewWatcher

6/10/2008 1:32:27 AM

This sample works only with SQL Server 2005 and SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2005.
The Adventure Works Cycles ReviewWatcher sample for SQL Server demonstrates how to use query notifications. This sample is used in conjunction with the Adventure Works Cycles Storefront e-commerce sample application. This document describes how to install the SQL Server version of the ReviewWatcher sample application.
This sample requires administrator privileges on the server to run correctly.
The default installation directory is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\Storefront\CS\ReviewWatcher\.

Scenario

A developer is trying to build an application that displays changes to the database as they happen, without polling the database.

Languages

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

Features

The ReviewWatcher sample uses the following features of SQL Server.

Application Area	Features
Overall	SqlDependency

Prerequisites

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

SQL Server, including the following components:
SQL Server Database Engine
SQL Server Management Studio
AdventureWorks sample database which is available at the CodePlex Web site.
Database Engine Samples which are available at the CodePlex 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

To build the sample, do the following:

Build the sample

Follow the steps in the readme.htm file for the Storefront sample application.
Note that in SQL Server, Service Broker is disabled in the AdventureWorks database. It must be enabled by using the following script for this sample to operate correctly: ALTER DATABASE AdventureWorks SET ENABLE_BROKER
Build the application in the solution file in the CS folder using Microsoft Visual Studio 2005 or MSBuild.

Running the Sample

To run the sample, do the following:

Run the sample

Browse to the Adventure Works Cycles Storefront sample by starting your Web browser and typing http://localhost/StoreCSVS/ in the Address bar.
Using the category/subcategory tree control menu on the left, browse to a subcategory of a product, and then select the subcategory.
Click a product in the list of products displayed.
Using a file browser, locate and execute the ReviewWatcher.exe application, which is typically installed in bin\debug.
Switch back to your Web browser, locate a particular product, and then click Review this Product.
Fill in the text boxes and click Submit.
A summary of the review should appear in the left pane in the ReviewWatcher application.
Selecting the summary line in the left pane displays the contents of the review in the right pane.

Removing the Sample

To remove the sample, do the following:

Remove the sample

Follow the instructions for removing the Storefront sample located in the Readme file for that sample.

Comments

The common language runtime for SQL Server must be enabled for this sample to work correctly.

Updated Wiki: SS2005!Readme_ReviewWatcher

bonniefe — Wed, 11 Jun 2008 00:41:56 GMT

Readme_ReviewWatcher

6/10/2008 4:38:07 PM

The Adventure Works Cycles ReviewWatcher sample for SQL Server 2005 demonstrates how to use query notifications. This sample is used in conjunction with the Adventure Works Cycles Storefront e-commerce sample application. This document describes how to install the SQL Server 2005 version of the ReviewWatcher sample application.
This sample works with the SQL Server 2005 version of the AdventureWorks sample database.
This sample requires administrator privileges on the server to run correctly.
The default installation directory is drive:\Program Files\Microsoft SQL Server\90\Samples\Integrated Samples\Storefront\CS\ReviewWatcher\.

Scenario

A developer is trying to build an application that displays changes to the database as they happen, without polling the database.

Languages

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

Features

The ReviewWatcher sample uses the following features of SQL Server 2005.

Application Area	Features
Overall	SqlDependency

Prerequisites

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

SQL Server 2005, including the following components:
SQL Server Database Engine
SQL Server Management Studio
AdventureWorks sample database available at the CodePlex web site.
Database Engine Samples available at the CodePlex 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

To build the sample, do the following:

Build the sample

Follow the steps in the readme.htm file for the Storefront sample application.
Note that in SQL Server 2005, Service Broker is disabled in the AdventureWorks database. It must be enabled by using the following script for this sample to operate correctly: ALTER DATABASE AdventureWorks SET ENABLE_BROKER
Build the application in the solution file in the CS folder using Microsoft Visual Studio 2005 or MSBuild.

Running the Sample

To run the sample, do the following:

Run the sample

Browse to the Adventure Works Cycles Storefront sample by starting your Web browser and typing http://localhost/StoreCSVS/ in the Address bar.
Using the category/subcategory tree control menu on the left, browse to a subcategory of a product, and then select the subcategory.
Click a product in the list of products displayed.
Using a file browser, locate and execute the ReviewWatcher.exe application, which is typically installed in bin\debug.
Switch back to your Web browser, locate a particular product, and then click Review this Product.
Fill in the text boxes and click Submit.
A summary of the review should appear in the left pane in the ReviewWatcher application.
Selecting the summary line in the left pane displays the contents of the review in the right pane.

Removing the Sample

To remove the sample, do the following:

Remove the sample

Follow the instructions for removing the Storefront sample located in the Readme file for that sample.

Comments

The common language runtime for SQL Server 2005 must be enabled for this sample to work correctly.

Updated Wiki: SS2008!Readme_HRResume

bonniefe — Wed, 11 Jun 2008 00:41:26 GMT

Readme_HRResume

6/10/2008 1:32:27 AM

This sample works only with SQL Server 2005 and SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2005.
The HRResume sample demonstrates how to build a simple multi-tier intranet Microsoft Windows Forms application. The sample demonstrates how to use full-text search on XML documents that are written in several different languages, and combine those results with other relational queries. The sample also demonstrates the use of XQueries on the server. The sample has been designed so that it can be easily localized.
The default installation directory is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\HRResume.
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.

Scenario

A developer wants to implement a resume processing system that is easy to localize and takes advantage of full-text search.

Languages

Transact-SQL, XML, XSD, XSLT, Visual C#, and Visual Basic.

Features

The HRResume sample uses the following features of SQL Server.

Application Area	Features
Overall	XML, XQuery, Full-text search

Prerequisites

Before running this sample, make sure SQL Server is installed, including the following components:

SQL Server Database Engine
SQL Server Management Studio
AdventureWorks sample database available at the CodePlex Web site.
Database Engine Samples available at the CodePlex 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 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.

To build the sample, do the following:

Build the sample

Ensure that the AdventureWorks sample database is installed.
In Management Studio, load and run the Scripts\installCS.sql script to install essential server-side stored procedures and functions.
In Windows Explorer, right-click the CS\HRWebService folder, click Properties, click the Web Sharing tab, click Share this folder, and then click OK twice. This creates an IIS virtual folder for the sample that will enable the application to work correctly.
Build the application in the solution file in the CS folder by using Visual Studio 2005 or Microsoft MSBuild.

Running the Sample

To run the sample, do the following:

Run the sample

Run CS\HR\bin\Debug\HR.exe.
Click the Resume table. Enter various search criteria, select whether you want to search for items that match all the criteria or any of them, and then, optionally, select the language you want to use for the full-text search. Click one of the calendar buttons to use a graphical method of inputting either the start modified date, the end modified date, or both by selecting a range of dates in the calendar control.
After using the calendar form to select one or more dates, click OK to accept the new dates, or click Cancel to close the form without changing any dates. Click Search to initiate the search. A summary of the results is shown in a grid. Selecting a row in the grid displays the resume associated with the person mentioned in that row.

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 contents of the file.

Comments

Updated Wiki: SS2008!Readme_DB3D

bonniefe — Wed, 11 Jun 2008 00:40:17 GMT

Readme_DB3D

6/10/2008 1:32:27 AM

This sample works only with SQL Server 2005 and SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2005.
DB3D is an example application that stores, visualizes and manipulates tri-dimensional wireframe models by using SQL Server and .NET Framework.
The default installation directory is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\DB3D

Scenario

The DB3D application illustrates how to take advantage of various SQL Server 2005 features to handle several common application needs.
The application can load tri-dimensional wireframe models from a file or from a database. It can also upload new wireframe models into a database by using various techniques that show different performance characteristics.
Wireframe models are represented by using triangles in space. Triangles are directly stored in the database as user-defined types and also used by the client application to manipulate the rendered wireframes.
Once in the database, wireframe models can be manipulated interactively on the client, or through Transact-SQL in the server by using the SQL-CLR methods included in the sample library. The application also supports reporting on the wireframes that are contained in the database, for which it uses custom aggregates to perform computation close to the data and avoids data-shipping costs.

Languages

Transact-SQL and Visual C#.

Features

The DB3D sample uses the new features of SQL Server as shown in the following table:

Application Area	Features
Representing wireframe model data	Use of SQL Server user-defined types to appropriately represent pieces of information of the problem domain of the application. In the case of DB3D, two user-defined types are defined, "Triangle" and "Point3D". The example shows how to use the types both from within SQL Server and from a client application through ADO.NET 2.0.
Manipulating wireframe models	The "Triangle" and "Point3D" user-defined types include, in addition to their persistent state, a rich set of methods to manipulate them (for example to rotate a triangle in space). Those methods can be used both from the client and from within SQL Server itself to interact and change models.
Computing summary information for wireframe models	Use of SQL Server user-defined aggregates to perform processing close to the data (in the database) using custom algorithms. The sample can compute the surface of a given model by using a custom aggregate. This lets the system perform the computation in an efficient environment (CLR) without having to ship the data to another tier.
Uploading wireframe data quickly into the database	The application includes two strategies for uploading data: one based on regular INSERT statements and the other uses the new SqlBulkCopy class included in ADO.NET 2.0. Both are available so their performance characteristics can be compared.
Connect-to-database dialog box	The new SqlConnectionStringBuilder class is used to construct a connection string that is based on user-input in a safe way, that helps protect the application from connection-string-injection attacks.
Connect-to-database dialog box	The new SqlDataSourceEnumerator class is used to obtain the list of the instances of SQL Server that are available in the network.
Connect-to-database dialog box	The new database schema access API is used to retrieve the list of available databases from a connection.

Prerequisites

Before running this sample, make sure that 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 SQL Server Database Engine samples. These samples are included with SQL Server. You can download the latest version of the samples at the CodePlex 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 SampleKey.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 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.To build the sample, do the following:

To 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\db3d.sln
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.
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 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 performs the following actions:
Drops the old db3d database if it exists.
Registers the db3dsql assembly.
Registers some CLR UDTs and an aggregate.

Running the Sample

To run the sample, do the following:

Step 1: Loading models from files

The first time to run the application, it will not have any models or "wireframes" in the database. You must load them from files. The "models" subdirectory contains several model files you can use.
Click File, click Open and select one of the models from the "models" subdirectory. The model will display in the screen, and you can use the X, Y and Z sliders to rotate the model. You can see the user-defined types being used in the client to represent triangle information and to perform the transformations in the Triangle.cs and Point3D.cs files in the db3dsql project.

Step 2: Connecting to a database

To connect to a database, click Database and then click Connect. A dialog box will pop up where you can enter the name of the server, the database and authentication information. You should specify db3d as the name of the database to use. Once you are done click OK to connect. You can see how to build a connection string that is based on user input in the see the connectToolStripMenuItem_Click method in the MainFrm.cs file in the db3dwin project.
If you want, you can use the server and the database combo-boxes to browse the available servers and databases. You can see how to obtain the list of servers and/or databases in the file ConnectDlg.cs in the db3dwin project.
NOTE: the list of servers will include only those servers in the network that are currently available and that have been specifically enabled for discoverability.

Step 3: Uploading a model to the database

Once connected, you can upload a model
With a model loaded from a file from step 1, and after you connect to the database as described in step 2, click Database and then click Copy wireframe. This will prompt for a name and upload the triangle information to the database. You can also decide whether to enable "fast upload" using bulk-copy. You can experiment with the difference between doing many inserts one by one and using SqlBulkCopy for it. See the WireframeDbStorage.cs file in the db3dlib project.
You can repeat this operation with several other models (or even several copies of the same one with different names), so that you have a database that has many models in it.

Step 4: Viewing more model information

The application has a second tab that lets you see a list of all the wireframes in the database. You can also see the number of triangles they are made of and the total surface of the model. The interesting thing about this is that the surface is computed in the server without having to ship the data to the client by using a user-defined aggregate. You can see the user-defined aggregate implementation in the surface.cs file in the db3dsql project. Also see step 6 for information about how to use it in Transact-SQL.
To see this information, click the Wireframe Information tab.

Step 5: Rotating a model using Transact-SQL

When you use the slider controls in the client to rotate a wireframe, the application calls the "rotate" methods in each of the triangle objects that make up the model. Because these methods are part of the user-defined type that is registered in SQL Server, they can be used directly in the server.
Let's say that you can to rotate a model a fixed angle and store it rotated. Instead of bringing the data to the client, applying the transform, and then sending it back to the server, you can do this with a single T-SQL statement. To see this in action follow these steps:
Run the db3bwin application so that you can see the models. Connect to the database and select one model; for example, "tiger" (tiger.raw is the file that contains it if you did not upload it already).
Press F5 to refresh, and you will see that the tiger is looking towards you
Connect to the DB3D database using SQL Server Management Studio or some other query tool (for example, sqlcmd). Execute the following query: * UPDATE Triangle SET TriangleObj.RotateY(0.6)FROM Triangle t INNER JOIN Wireframe w ON t.WireframeID = w.WireframeID WHERE w.WireframeName = 'tiger' *
Now go back to the application and press F5. You will see that, when the tiger is reloaded from the database, it will appear rotated in the Y axis.

Step 6: Computing the surface of a model using T-SQL

The grid in the "Wireframe Information" shows the total surface of a given wireframe. This is done using the "Surface" custom aggregate that aggregates Triangle objects into a scalar value that represents the sum of the areas of all the triangles that matched the criteria of the query. You can use the custom aggregate in Transact-SQL directly. For example, you can execute this query in SQL Server Management Studio or some other query tool (for example, sqlcmd): * CREATE PROCEDURE ListWireframesDetailed AS SELECT w.WireframeID, WireframeName, COUNT(*) AS TriangleCount, dbo.Surface(t.TriangleObj) AS Surface FROM Wireframe w INNER JOIN Triangle t ON w.WireframeID = t.WireframeID GROUP BY w.WireframeID, WireframeName *

Removing the Sample

Use the following procedure to remove the sample:

To remove the sample

Load and run Scripts\cleanup.sql in Management Studio. 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.

Error message during deployment

When running the application from Visual Studio 2005, you might get an error that says that there was an error during deployment. Because you already created the database with all its elements by executing the createdb.sql script, you do not have to worry about that. It is. ok to say "ok to continue". If later, you change the db3dsql assembly, you will have to re-deploy it to SQL Server by using the script (or part of the script if you do not want to lose the existing model data).

About the graphics rendering code

This example is designed specifically to illustrate usage of various new features in SQL Server and Visual Studio 2005. It is not the goal of the example to provide a real 3-D visualization tool. To avoid unnecessary complexity in the example, the code that renders 3-D models in the screen is very simplistic and does not not perform common optimizations such as double-buffering nor does it do appropriate adjustments such as perspective correction.
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.

Change History

Updated Wiki: Home

bonniefe — Wed, 11 Jun 2008 00:38:56 GMT

SQL Server Samples Portal Page > SQL Server End to End Product Samples

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

Individual Samples

Sample	SQL Server 2005	SQL Server 2008
DB3D	SS2005	SS2008
HRResume	SS2005	SS2008

Storefront Family

Sample	SQL Server 2005	SQL Server 2008
ReviewWatcher	SS2005	SS2008
Storefront	SS2005	SS2008
Service Broker Ordering Service Sample	SS2005	SS2008

Updated Wiki: Home

ReedMe — Tue, 10 Jun 2008 23:49:37 GMT

SQL Server Samples Portal Page > SQL Server End to End Product Samples

SQL Server 2008 RC0 product samples are now available.

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

Individual Samples

Sample	SQL Server 2005	SQL Server 2008
DB3D	SS2005	SS2008
HRResume	SS2005	SS2008

Storefront Family

Sample	SQL Server 2005	SQL Server 2008
ReviewWatcher	SS2005	SS2008
Storefront	SS2005	SS2008
Service Broker Ordering Service Sample	SS2005	SS2008

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

Tue, 10 Jun 2008 23:22:10 GMT

This release contains the SQL Server 2008 RC0 product samples for multi-technology, end-to-end and integrated applications.

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

Tue, 10 Jun 2008 23:22:10 GMT

This release contains the SQL Server 2008 RC0 product samples for multi-technology, end-to-end and integrated applications.

UPDATED WIKI: SS2008!Service Broker Ordering Service Sample

bonniefe — Wed, 20 Feb 2008 07:33:08 GMT

Readme_Service Broker Ordering Service Sample

Note:
This sample requires the Adventure Works Storefront sample. For more information about installing the Storefront sample, see Readme_Storefront.

Scenario

A developer wants to implement a backend order processing system for an e-commerce Web site.

Languages

Transact-SQL, XML, XSD, and Visual C#.

Prerequisites

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

SQL Server, including the following components:
SQL Server Database Engine
SQL Server Management Studio
AdventureWorks sample database
Database Engine Samples
Adventure Works Storefront sample
.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

Set up the Service Broker environment

Run the Transact-SQL script to set up Service Broker. You can run installorderingservice.cmd, or you can run the individual scripts.
Run installorderingservice.cmd. The default folder is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\Storefront.
Alternatively, you can run the individual scripts in the following order:
OrderingServiceScripts\Setup.sql
OrderingServiceScripts\SetupOrderingServiceProgram.sql
OrderingServiceScripts\SetupPurchasingServiceProgram.sql
OrderingServiceScripts\SetupManufacturingServiceProgram.sql
OrderingServiceScripts\SetupShippingServiceProgram.sql
Configure the Storefront.
Edit the web.config file, located in the directory C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\Storefront\CS\StoreCSVS. Find the ExtendedOrderProcessing attribute, and change the value to true. After making the change, this element should look like the element below: <add key="ExtendedOrderProcessing" value="true"/>

Running the Sample

Order an in-stock item

In Internet Explorer, open http://localhost/storeCSVS/ .
In the left pane, expand Accessories, and then expand Helmets. Select Sports-100 Helmet, Red, and then click Add to Cart. On the Shopping Cart page, click Final Check Out. On the next page, click Submit.
In SQL Server Management Studio, run AdministrationAndTroubleShooting.sql. The default folder is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\Storefront\OrderingServiceScripts. The result shows the processing flow, including Server Broker queue tables, ordering state, and audit logs.
Run purge.sql to clean up contents in queues and tables before continuing on to the next exercise.

Order an out-of-stock buy item

In Internet Explorer, open http://localhost/storeCSVS/ .
In the left menu, expand Clothing. Click the submenu item Tights. Pick Women’s Tights, M, and then click Add to Cart. In the next page, click Final Check Out. In the next page, click Submit.
In SQL Server Management Studio, run AdministrationAndTroubleShooting.sql. The default folder is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\Storefront\OrderingServiceScripts. The result shows the processing flow, including Server Broker queue tables, ordering state, and audit logs.
Run purge.sql to clean up contents in queues and tables before continuing on to the next exercise.

Order an out-of-stock make item ready for manufacturing

In Internet Explorer, open http://localhost/storeCSVS/ .
On the left menu, expand Components. Click Mountain Frames, select HL Mountain Frame – Black, 38, and then click Add to Cart. On the next page, click Final Check Out. On the next page, click Submit.
In SQL Server Management Studio, run AdministrationAndTroubleShooting.sql. The default folder is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\Storefront\OrderingServiceScripts. The result shows the processing flow, including Server Broker queue tables, ordering state, and audit logs.
Run purge.sql to clean up contents in queues and tables before continuing on to the next exercise.

Remove the sample

UPDATED WIKI: SS2005!Service Broker Ordering Service Sample

bonniefe — Wed, 20 Feb 2008 07:32:51 GMT

Service Broker Ordering Service Sample

2/19/2008 11:18:35 PM

The Adventure Works Storefront sample accepts an online order and returns a predefined ship date in the order status screen. This sample adds backend order processing capabilities to Adventure Works Storefront.
This sample illustrates the fundamental concepts of Service Broker. It lets you view the Transact-SQL scripts that are used to run the sample, and the results of executing that script in the Service Broker tables.

Note:
This sample requires the Adventure Works Storefront sample. For more information about installing the Storefront sample, see Readme_Storefront. By default, the Adventure Works Storefront sample is installed at C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\\Storefront.

Scenario

A developer wants to implement a backend order processing system for an e-commerce Web site.

Languages

Transact-SQL, XML, XSD, and Visual C#.

Prerequisites

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

SQL Server 2005, including the following components:
SQL Server Database Engine
SQL Server Management Studio
AdventureWorks sample database
Database Engine Samples
Adventure Works Storefront sample
.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

Set up the Service Broker environment

Run the Transact-SQL script to set up Service Broker. You can run installorderingservice.cmd, or you can run the individual scripts.
Run installorderingservice.cmd. The default folder is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\\Storefront.
Alternatively, you can run the individual scripts in the following order:
OrderingServiceScripts\Setup.sql
OrderingServiceScripts\SetupOrderingServiceProgram.sql
OrderingServiceScripts\SetupPurchasingServiceProgram.sql
OrderingServiceScripts\SetupManufacturingServiceProgram.sql
OrderingServiceScripts\SetupShippingServiceProgram.sql
Configure the Storefront.
Edit the web.config file, located in the directory C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\\Storefront\CS\StoreCSVS. Find the ExtendedOrderProcessing attribute, and change the value to true. After making the change, this element should look like the element below: <add key="ExtendedOrderProcessing" value="true"/>

Running the Sample

Order an in-stock item

In Internet Explorer, open http://localhost/storeCSVS/ .
In the left pane, expand Accessories, and then expand Helmets. Select Sports-100 Helmet, Red, and then click Add to Cart. On the Shopping Cart page, click Final Check Out. On the next page, click Submit.
In SQL Server Management Studio, run AdministrationAndTroubleShooting.sql. The default folder is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\\Storefront\OrderingServiceScripts. The result shows the processing flow, including Service Broker queue tables, ordering state, and audit logs.
Run purge.sql to clean up contents in queues and tables before continuing on to the next exercise.

Order an out-of-stock buy item

In Internet Explorer, open http://localhost/storeCSVS/ .
In the left menu, expand Clothing. Click the submenu item Tights. Pick Women’s Tights, M, and then click Add to Cart. In the next page, click Final Check Out. In the next page, click Submit.
In SQL Server Management Studio, run AdministrationAndTroubleShooting.sql. The default folder is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\\Storefront\OrderingServiceScripts. The result shows the processing flow, including Service Broker queue tables, ordering state, and audit logs.
Run purge.sql to clean up contents in queues and tables before continuing on to the next exercise.

Order an out-of-stock make item ready for manufacturing

In Internet Explorer, open http://localhost/storeCSVS/ .
On the left menu, expand Components. Click Mountain Frames, select HL Mountain Frame – Black, 38, and then click Add to Cart. On the next page, click Final Check Out. On the next page, click Submit.
In SQL Server Management Studio, run AdministrationAndTroubleShooting.sql. The default folder is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\\Storefront\OrderingServiceScripts. The result shows the processing flow, including Service Broker queue tables, ordering state, and audit logs.
Run purge.sql to clean up contents in queues and tables before continuing on to the next exercise.

Remove the sample

UPDATED WIKI: SS2008!Readme_Storefront

bonniefe — Wed, 20 Feb 2008 07:32:36 GMT

Readme_Storefront

2/19/2008 9:32:55 PM
[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]

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 Storefront sample for the Adventure Works Cycles sample database in SQL Server demonstrates how to build a simple Internet retail application by using SQL Server, ADO.NET, and ASP.NET. This document describes how to install the SQL Server version of the sample application.
This sample works with the AdventureWorks sample database, which is included with SQL Server. Updates for both the database and this sample are available to download at the CodePlex Web site.
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.
The default installation directory is C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\Storefront\.

Scenario

A developer wants to implement an e-commerce Web site. The Web site should offer additional product recommendations based on the contents of the shopping cart (product up sell).

Languages

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

Features

The Storefront sample uses the following features of SQL Server:

Application Area	Features
Demographics	XML, XSD
Globalization	Common language runtime user-defined function, common language runtime user-defined type
Overall	ADO.NET, Transact-SQL, AdventureWorks sample database

Prerequisites

Before running this sample, make sure that SQL Server is installed, including the following components:

SQL Server Database Engine
SQL Server Management Studio
AdventureWorks SP1 sample database
Database Engine Samples
The AdventureWorks CLR sample. By default, this is placed in C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\CLR\AdventureWorks when you install Database Engine Samples. See the readme file for this sample for additional installation instructions.
.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 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.

To build the sample, do the following:

Step 1: Install the sample and configure IIS

Alter the permissions of the folder where this sample is installed so it may be accessed by the user under which IIS runs. See the default installation directory above for the location of this folder. By default IIS runs under machinename\ASPNET for IIS 5.1 (Windows XP) and Network Service for IIS 6.0 (Windows 2003).
If you intend to compile by using MSBuild instead of Visual Studio, create the StoreCSVS v-root if it does not already exist by performing the following steps:
Right-click the StoreCSVS folder in C:\Program Files\Microsoft SQL Server\100\Samples\Integrated Samples\Storefront\CS\ and select Properties.
In the StoreCSVS Properties page, go to the Web Sharing tab and select Share this folder.
On the Edit Alias page, make sure Read is selected as the default Access permission and Script is selected as the default Application permission, and then click OK.
If you have not already enabled the Default.aspx page on this server, you can do so by performing the following steps:
Open Internet Information Services (IIS) Manager and expand the local computer in the explorer in the left pane.
Right-click StoreCSVS and click Properties. StoreCSVS should be listed under Default Web Site in Web Sites. If you have left IIS Manager open from a previous step, you might need to click Action and then click Refresh to see the newly added v-root.
Ensure that the ASP.NET version selected for the StoreCSVS virtual directory is 2.0.xxxxx where xxxxx is the build version.
On the StoreCSVS Properties page, click the Documents tab, and then select Enable default content page. If Default.aspx is not listed as a content page, click Add.
On the Add Content page, type Default.aspx, click OK, and then click OK again.

Step 2: Build the sample

In Visual Studio
Open the CS\StoreCSVS.sln solution file.
On the Build menu, click Rebuild Solution.
If you do not have Visual Studio, you can use MSBuild, which is distributed with the .NET Framework SDK 2.0
Open a .NET Framework SDK 2.0 command prompt window.
Change the directory to the Storefront sample directory.
Run this command: msbuild /property:configuration=debug CS\StoreCSVS.sln

Step 3: Configure SQL Server

Install the Storefront sample stored procedures by running the AWStore.sql script file. You can do this either by using Management Studio or by using the sqlcmd utility. The script file is located in the Scripts directory.
To run the script file by using Management Studio, on the File menu, click Open, locate the Scripts folder, select the AWStore.sql file, and then run the contents of the file.
To run the script file by using the sqlcmd utility, at the command prompt, change the directory to the folder where the AWStore.sql file is located, and then run the following command: sqlcmd -E -I -i awstore.sql

Step 4: Enable the OLAP-based product upsell scenario

Open the Analysis Services project in <drive>:\Program Files\Microsoft SQL Server\100\Tools\Samples\AdventureWorks Analysis Services Project\Adventure Works.sln.
Deploy the project.
In Management Studio, click Connect in Object Explorer, and then click Analysis Server.
Click Connect in the dialog box that appears.
Right-click the new top level Analysis Server node that is displayed in the Object Explorer tree control. The node will be similar to COMPUTERNAME. In Analysis Services, the node will be similar to Domain\User.
Click Properties.
Click the *Security *page.
Click Add.
Type NETWORK SERVICE .
Click OK twice.

Running the Sample

To run the sample, do the following:

Step 1: Browse the Web site

Open Internet Explorer and type http://localhost/storecsvs in the address bar. With this application, you can perform a variety of real-world Web application tasks, including the following:
Browse the tree control of the product categories.
Find out what products are offered and available.
Register a fictitious user on the system, including adding fictitious demographic information.
Add items to your shopping cart.
Go through the checkout process.
View previously completed orders using the account icon.
Use the Services icon to browse Web services, or the Search text box to find products.

Step 2: Modify the installed sample and recompile (Optional)

Remove the reference to the StoreClientComponents DLL and PDB files from the bin folder for the Web site.
Add the reference to the StoreClientComponents DLL by selecting the Web site project, and then using the Web Site/References menu item.
Save the project.
Delete the StoreCSVS folder and its contents from the Temporary ASP.NET Files folder by using the following procedure:
Exit Visual Studio 2005.
Stop IIS.
Delete the StoreCSVS folder from the drive:\WINNT\Microsoft.NET\Framework\v2.0.xxxxx\Temporary ASP.NET Files folder.
Empty the Recycle Bin.
Start IIS. It is not necessary to recompile the sample to run it.

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 contents of the file.

Comments

The common language runtime for SQL Server must be enabled for this sample to run correctly.

Microsoft SQL Server Product Samples: End to End

Source code checked in, #11622

Updated Wiki: SS2008!Service Broker Ordering Service Sample

Readme_Service Broker Ordering Service Sample

Scenario

Languages

Prerequisites

Building the Sample

Set up the Service Broker environment

Running the Sample

Order an in-stock item

Order an out-of-stock buy item

Order an out-of-stock make item ready for manufacturing

Remove the sample

Updated Wiki: SS2005!Service Broker Ordering Service Sample

Service Broker Ordering Service Sample

Scenario

Languages

Prerequisites

Building the Sample

Set up the Service Broker environment

Running the Sample

Order an in-stock item

Order an out-of-stock buy item

Order an out-of-stock make item ready for manufacturing

Remove the sample

Updated Wiki: SS2008!Readme_Storefront

Readme_Storefront

Scenario

Languages

Features

Prerequisites

Building the Sample

To generate a strong name key file

Step 1: Install the sample and configure IIS

Step 2: Build the sample

Step 3: Configure SQL Server

Step 4: Enable the OLAP-based product upsell scenario

Running the Sample

Step 1: Browse the Web site

Step 2: Modify the installed sample and recompile (Optional)

Removing the Sample

Remove the sample

Comments

See Also

Concepts

Help and Information

Updated Wiki: SS2005!Readme_Storefront

Readme_Storefront

Scenario

Languages

Features

Prerequisites

Building the Sample

To generate a strong name key file

Step 1: Install the sample and configure IIS

Step 2: Build the sample

Step 3: Configure SQL Server

Step 4: Enable the OLAP-based product upsell scenario

Running the Sample

Step 1: Browse the Web site

Step 2: Modify the installed sample and recompile (Optional)

Removing the Sample

Remove the sample

Comments

See Also

Concepts

Help and Information

Change History

Updated Wiki: SS2008!Readme_ReviewWatcher

Readme_ReviewWatcher

Scenario

Languages

Features

Prerequisites

Building the Sample

Build the sample

Running the Sample

Run the sample

Removing the Sample