MSFTSBProdSamples Wiki & Documentation Rss Feed

New Comment on "SS2008!Readme_ShoppingCart"

mnvraghuram — Wed, 10 Apr 2013 17:53:11 GMT

Where can i download this "ssb_ShoppingCart" database.

Updated Wiki: Home

bonniefe — Tue, 08 Dec 2009 23:58:30 GMT

SQL Server Samples Portal Page > SQL Server Service Broker Product Samples

This project contains Service Broker samples released with Microsoft SQL Server product. Below is the list of these samples. If you are interested in contributing Service Broker 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
EventNotification	SS2005	SS2008
HelloWorld	SS2005	SS2008
HelloWorld_CLR	SS2005	SS2008
ServiceBrokerInterface	SS2005	SS2008
ShoppingCart	SS2005	SS2008
Dialog Security		SS2008
Transport Security		SS2008
Dialog Pool		SS2008
Fast Data Push		SS2008

Got questions? Check out the SQL Server Community & Samples Discussion Forum

For more samples, or if you want to contribute, see the SQL Server Community Samples for Service Broker

Updated Wiki: SS2008!Readme_FastDataPush

portegys — Sat, 28 Feb 2009 03:03:38 GMT

Readme_FastDataPush Sample

11/05/2008 21:36:06

Scenario

A common use of service broker is the "data push" scenario in which messages are asynchronously sent to a destination such as a data warehouse for storage and processing with minimal processing delay to the source application. Two frequent concerns are whether service broker can handle a proposed work load, and how to "tune" a broker application so that it can achieve the required performance. Since various applications impose different constraints and are hosted within differing computing and networking configurations, there is no "one size fits all" answer.

This sample offers a means of estimating the performance of a broker application and tuning it to suit a given load and configuration. The user does this by setting several application parameters, such as message volume, message size, and processing time, as well as several internal parameters, such as number of initiator transactions, number of dialogs, etc. On the initiator, the output is the time to send the specified number of messages and the time for the messages to be transmitted to the target. On the target, the output is the time to receive and process the messages, which allows the user to obtain an estimate of whether the initiator is overrunning the target, something to avoid for a sustained high volume message load.

The sample also illustrates a number of recommended practices for using service broker, and can serve as an example of how to build the service broker part of a data push application. Of particular significance, it is recommended that batch messaging be done where possible. On the initiator side, this refers to sending messages on a set of "reusable" dialogs to avoid the overhead of creating a dialog per message. The dialog pool sample shows how to do this. On the target, batching refers to receiving a set of messages at a time, which can significantly improve performance.

Running the Sample

This sample is normally run between two server instances on different machines using Windows transport security. However, it can easily be configured to perform a "loop around" data push in the same database by skipping the indicated sections of the initiator and target setup scripts. For the two server case, it is essential that the servers are configured to enable communication protocols. In this example, we will be using TCP, so use the SQL Server Configuration Manager to make sure TCP is enabled on both servers.

On each server, open the project file in SQL Server Management Studio.

Edit the Common setup.sql script and set the desired parameters. Make sure the edits are performed identically on both servers.

Run the scripts, in order:

1 - Common setup.sql (both servers).
2 - Initiator setup.sql.
3 - Target setup.sql.
4 - Initiator send.sql. The message sending start and end times are printed.
5 - Target monitor.sql. The message processing time is printed.
6 - Cleanup.sql (both servers).

© 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Readme_DialogPool

portegys — Sat, 28 Feb 2009 03:01:29 GMT

Readme_DialogPool Sample

11/05/2008 21:36:06

Scenario

As noted in various Service Broker sources, it is often advantageous to minimize the overhead of creating dialogs to send messages on. This sample shows how to create a shared pool of dialogs to be able to reuse dialogs instead of creating new ones.

The code shows how to get, free and delete dialogs from a dialog pool table. Initially empty, a new dialog is created in the pool when a request for an existing free dialog cannot be met. Thus the pool will grow during bursts of high demand.

The dialog pool entries also contain creation time and send count fields that ease the auditing and "recycling" of dialogs in the pool based on application requirements. Recycling consists of gracefully ending an existing dialog between services and beginning a new one. If done prudently, this technique can ease the handling of dialog errors by limiting the number of messages affected. For example, the application may choose to contrain a dialog to a certain number of messages before it is recycled. This might also be done according to the age of a dialog. See the end of the usp_send procedure for an example of recycling.

An example application that exercises the dialog pool is also included.

Running the Sample

Open the project file in SQL Server Management Studio.

Run the scripts, in order:

1 - Demo database setup.sql
2 - Dialog pool setup.sql
3 - Demo app setup.sql
4 - Run demo.sql
5 - Cleanup.sql

© 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Readme_DialogPool

portegys — Sat, 28 Feb 2009 02:59:15 GMT

This sample requires two server instances on different machines to avoid a port collision. It is essential that the servers are configured to enable communication protocols. In this example, we will be using TCP, so use the SQL Server Configuration Manager to make sure TCP is enabled on both servers.

On one server, open the initiator project file in SQL Server Management Studio. Open the target project file on the other server.

Run the scripts, in order:

1 - Initiator endpoint setup.sql.

1 - Target endpoint setup.sql.

2 - Initiator certification of target.sql.

2 - Target certification of initiator.sql.

3 - Initiator service setup.sql.

3 - Target service setup.sql.

4 - Initiator message send.sql.

4 - Target message receive.sql.

5 - Initiator cleanup.sql.

5 - Target cleanup.sql.

Updated Wiki: SS2008!Readme_TransportSecurity

portegys — Sat, 28 Feb 2009 02:58:34 GMT

Readme_TransportSecurity Sample

11/05/2008 21:36:06

Scenario

In order to have a broker dialog between server instances, you have to be concerned with having a secure network connection, which in service broker terminology is called transport security. An effective way to accomplish this is using certificates to secure the broker endpoints, which is the topic of this sample. You can then safely establish dialogs knowing that the communication context is authenticated. By default, messages are also encrypted on behalf of dialogs by the endpoints to prevent monitoring.

Certificate-based authentication is more cumbersome to set up than Windows based authentication, but it works in more general circumstances, e.g., between different domains, and allows users to specify a window of time in which authentication will be honored. In any case, some form of transport security is always necessary.

The initiator and target certificates must be exchanged in order for them to authenticate each other. This "out of band" exchange should be done with a high level of trust, since a certificate bearer will be able to begin dialogs and send messages to service broker services in the authenticating server.

Transport security allows dialogs to be set up between services and is not concerned with permissions and security associated with these services. For example, in the sample code the target service will accept messages from any source in the sender server. If this is an issue, then see the dialog security sample.

Running the Sample

This sample requires two server instances on different machines to avoid a port collision. It is essential that the servers are configured to enable communication protocols. In this example, we will be using TCP, so use the SQL Server Configuration Manager to make sure TCP is enabled on both servers.

On one server, open the initiator project file in SQL Server Management Studio. Open the target project file on the other server.

Run the scripts, in order:

1 - Initiator endpoint setup.sql.
1 - Target endpoint setup.sql.
2 - Initiator certification of target.sql.
2 - Target certification of initiator.sql.
3 - Initiator service setup.sql.
3 - Target service setup.sql.
4 - Initiator message send.sql.
4 - Target message receive.sql.
5 - Initiator cleanup.sql.
5 - Target cleanup.sql.

© 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Readme_TransportSecurity

portegys — Sat, 28 Feb 2009 02:58:16 GMT

Readme_DialogSecurity Sample

11/05/2008 21:36:06

Scenario

Running the Sample

This sample requires two server instances on different machines to avoid a port collision. It is essential that the servers are configured to enable communication protocols. In this example, we will be using TCP, so use the SQL Server Configuration Manager to make sure TCP is enabled on both servers.

On one server, open the initiator project file in SQL Server Management Studio. Open the target project file on the other server.

Run the scripts, in order:

1 - Initiator endpoint setup.sql.
1 - Target endpoint setup.sql.
2 - Initiator certification of target.sql.
2 - Target certification of initiator.sql.
3 - Initiator service setup.sql.
3 - Target service setup.sql.
4 - Initiator message send.sql.
4 - Target message receive.sql.
5 - Initiator cleanup.sql.
5 - Target cleanup.sql.

© 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Readme_DialogSecurity

portegys — Sat, 28 Feb 2009 02:55:38 GMT

Readme_DialogSecurity Sample

11/05/2008 21:36:06

Scenario

This sample shows how to set up a secure dialog using certificates. Service broker will always have a level of security at the transport level, which may include encryption, but this is at a server level of granularity. It does not secure conversations on a database-to-database basis. If this is required, then dialog security can be used. Dialog security is also end-to-end as opposed to the point-to-point connection-based security provided by transport security. Since conversations may entail multiple hops through the use of forwarding, dialog security can provide authentication and one-time encryption at the terminating services. Certificate-based authentication also allows users to specify a window of time in which authentication will be honored.

The initiator and target certificates must be exchanged in order for them to authenticate each other. This "out of band" exchange should be done with a high level of trust, since a certificate bearer will be able to begin dialogs and send messages to service broker services in the authenticating server.

Running the Sample

This sample requires two server instances on different machines to avoid a port collision. It is essential that the servers are configured to enable communication protocols. In this example, we will be using TCP, so use the SQL Server Configuration Manager to make sure TCP is enabled on both servers. To keep things simple, Windows authentication is used for transport security. The transport security sample shows how to use certificates for this if needed.

On one server, open the initiator project file in SQL Server Management Studio. Open the target project file on the other server.

Run the scripts, in order:

1 - Initiator endpoint setup.sql.
1 - Target endpoint setup.sql.
2 - Initiator service setup.sql.
2 - Target service setup.sql.
3 - Initiator certification of target.sql.
3 - Target certification of initiator.sql.
4 - Initiator message send.sql.
4 - Target message receive.sql.
5 - Initiator cleanup.sql.
5 - Target cleanup.sql.

© 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Readme_ShoppingCart

portegys — Sat, 28 Feb 2009 02:46:24 GMT

Readme_ShoppingCart Sample

11/05/2008 21:36:06

The Shopping Cart sample uses the conversation group identifier to maintain state for a simple shopping cart application. The application uses the ServiceBrokerInterface sample.

Building and Installing the Sample

In Visual Studio 2008, open ShoppingCartCS.sln .
Build the solution by pressing F6, or by selecting Build Solution from the Build menu.
Open a command prompt, locate the Scripts folder, and then run the following command: * install all *The install script installs the SQL Server objects for the application, including the common language runtime (CLR) stored procedure that implements the ShoppingCartService service.

Running the Sample

Run the ShoppingCartClient.exe application from the sample directory. For simplicity, the client processes one order each time the client runs.
Click Create Order to create an order. Add items to the shopping cart by selecting the item from the Item list, and then clicking the Add Item button.
Click the *Service Broker Trace *tab at any time to see a summary of the Service Broker messages sent and received.
The ShoppingList and StateTable tables in the ssb_ShoppingCart database maintain state for the application. The CLR stored procedure updates the tables based on messages from the client. You can use Management Studio or sqlcmd to inspect these tables.

Uninstalling the Sample

Open a command prompt, locate the Scripts folder, and then run the following command: * uninstall all *
The uninstall script removes the SQL Server objects for the application.

Requirements

This sample requires Visual Studio 2008. Because the sample uses features of the CLR that were not available in earlier versions, versions of Visual Studio earlier than 2008 cannot build the sample.

Demonstrates

Service Broker applications most often store state in the database that hosts the service. When messages arrive, the application loads state from the database, and then processes the messages.
The *Service* class of the Service Broker Interface sample provides a convenient way to maintain state. This sample demonstrates how to use the Service class to maintain state.
To maintain state by using the *Service* class, you implement two methods in your application and a stored procedure in SQL Server, as listed in the following table:

Item	Signature	Description
Stored Procedure	CREATE PROCEDURE name (@cgid uniqueidentifier)	Returns the state for the application. The result sets that are returned by this procedure must contain the conversation group identifier.
public method	public override bool LoadState(System.Data.Sql.SqlReader reader)	Reads the result sets that are provided by the stored procedure to restore state. This stored procedure must save the conversation group identifier in the class, because the Service Broker Interface does not provide the identifier to the SaveState method.
public method	public override void SaveState()	Saves state to the database.

This topic describes the general outline for restoring state. See ShoppingCartService.cs for the full example.
The stored procedure must accept a conversation group identifier and return two result sets. The first result set consists of the conversation group identifier itself. The second result set contains the application-specific state. There is no fixed name for this stored procedure. Instead, you supply the name of the stored procedure by setting the *AppLoaderProcName* property. The Service Broker Interface simply calls the stored procedure provided.
The *LoadState* method restores the state for the application. The exact process the application follows depends on the state that the application requires. The method takes an instance of *System.Data.Sql.SqlReader* as a parameter. The *SqlReader* contains the result sets returned the stored procedure. Typically, implementations of the *LoadState* method update the *State* property of the *Service* class, save the conversation group identifier in a private field, and then save the application-specific state in appropriate data structures. For example, the *ShoppingCartService* stores information about items, quantities, and prices in a private instance of the *ShoppingCart* class.
After calling *LoadState* , the Service Broker Infrastructure dispatches the message. Notice that, if you use the attribute-based message dispatch framework, you can dispatch messages based on the State property in addition to the message type name. In the methods that handle messages, you can read or update the data structures that are created in *LoadState* .
When the message handling method returns, the Service Broker Infrastructure calls the *SaveState* method. The *SaveState* method uses the *Connection* property of the Service class to create a *SqlCommand* object, and then uses that object to update the state stored in the database. For example, the *ShoppingCartService* deletes the saved contents of the shopping cart and then inserts the current contents of the shopping cart into the database.
© 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Readme_ServiceBrokerInterface

portegys — Sat, 28 Feb 2009 02:45:20 GMT

Readme_ServiceBrokerInterface Sample

11/05/2008 21:36:06

This sample shows one way to build an object-oriented programming interface for Service Broker applications. The sample contains classes that encapsulate the details of sending and receiving messages by using the Service Broker DML. This sample forms the foundations for other sample applications included with the SQL Server samples.
The sample includes two different approaches to message dispatch. An application that uses this sample can use an attribute-based approach for message dispatch, or the application can implement a message processing loop.
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.

Building the Sample

Open the solution file Service Broker Interface.sln in Visual Studio 2008. This file is located in the cs directory within the ServiceBrokerInterface directory.
Build the solution by pressing F6, or by selecting Build Solution from the Build menu.

Using the Sample

Build the sample as described above.
Add a reference to the assembly Microsoft.Samples.SqlServer.dll .
In your code, add a using directive (C#) or Imports statement (Visual Basic) for the namespace Microsoft.Samples.SqlServer .

Requirements

This sample requires Visual Studio 2008. Because the sample uses features of the common language runtime that were not available in earlier versions, versions of Visual Studio earlier than 2008 cannot build the sample.

Demonstrates

This sample demonstrates one way to represent Service Broker DML within a .NET language.
© 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Readme_HelloWorldService

portegys — Sat, 28 Feb 2009 02:44:09 GMT

ReadmeHelloWorldCLR Sample

11/05/2008 21:36:06

This sample shows a simple, stateless application that uses the ServiceBrokerInterface sample.
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.

Building and Installing the sample

In Visual Studio 2008, open HelloWorldCS.sln or HelloWorldVB.sln .
Build the solution by pressing F6, or by selecting Build Solution from the Build menu.
Run Install.cmd , located in the Scripts folder of the HelloWorld_CLR directory. This file sets up the environment, and then runs the Install.sql install script. If you built the Visual Basic version of the project, you might have to change the "cs" in the path for the assembly to "vb" in the Install.sql script.

Running the sample

Run the HelloWorldClient.exe console application from the sample directory. To exit the client, press Enter after the client shows the response.

Requirements

This sample requires Visual Studio 2008. Because the sample uses features of the common language runtime (CLR) that were not available in earlier versions, versions of Visual Studio earlier than 2008 cannot build the sample.

Demonstrates

This sample demonstrates use of the sample object-oriented programming interface provided in the Service Broker Interface sample. All Service Broker functionality for the sample uses the Service Broker Interface.
There are two main parts of the sample: a client program that runs outside of SQL Server, and a CLR stored procedure that implements the service.
The external program begins a conversation from the service HelloWorldClient to the service HelloWorldService, and then sends a message on that conversation. This application sends a Request message to the service HelloWorldService. The activated stored procedure receives and responds to the message. The client receives a response, shows the response on the console, and then ends the dialog.
The CLR stored procedure implements the HelloWorldService. Service Broker activates this procedure. The procedure reads a message from the queue. For a Request message, the procedure responds with a Response message. For a Service Broker end dialog message, the procedure ends the conversation.
© 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: Home

portegys — Sat, 28 Feb 2009 02:43:33 GMT

Sample	SQL Server 2005	SQL Server 2008
EventNotification	SS2005	SS2008
HelloWorld	SS2005	SS2008
HelloWorld_CLR	SS2005	SS2008
ServiceBrokerInterface	SS2005	SS2008
ShoppingCart	SS2005	SS2008
Dialog Security		SS2008
Transport Security		SS2008
Dialog Pool		SS2008
Fast Data Push		SS2008

Got questions? Check out the SQL Server Community & Samples Discussion Forum

For more samples, or if you want to contribute, see the SQL Server Community Samples for Service Broker

Updated Wiki: Home

portegys — Fri, 27 Feb 2009 22:27:51 GMT

Sample	SQL Server 2005	SQL Server 2008
EventNotification	SS2005	SS2008
HelloWorld	SS2005	SS2008
HelloWorldService	SS2005	SS2008
ServiceBrokerInterface	SS2005	SS2008
ShoppingCart	SS2005	SS2008
Dialog Security		SS2008
Transport Security		SS2008
Dialog Pool		SS2008
Fast Data Push		SS2008

Got questions? Check out the SQL Server Community & Samples Discussion Forum

For more samples, or if you want to contribute, see the SQL Server Community Samples for Service Broker

Updated Wiki: Home

portegys — Fri, 27 Feb 2009 22:26:57 GMT

Sample	SQL Server 2005	SQL Server 2008
EventNotification	SS2005	SS2008
HelloWorld	SS2005	SS2008
HelloWorldService	SS2005	SS2008
ServiceBrokerInterface	SS2005	SS2008
ShoppingCart	SS2005	SS2008
Dialog Security		SS2008
Transport Security		SS2008
Dialog Pool		SS2008
Fast Data Push		SS2008

Got questions? Check out the SQL Server Community & Samples Discussion Forum

Want to contribute? See the SQL Server Community Samples for Service Broker

Updated Wiki: Home

portegys — Fri, 27 Feb 2009 22:25:10 GMT

Sample	SQL Server 2005	SQL Server 2008
EventNotification	SS2005	SS2008
HelloWorld	SS2005	SS2008
HelloWorldService	SS2005	SS2008
ServiceBrokerInterface	SS2005	SS2008
ShoppingCart	SS2005	SS2008
Dialog Security		SS2008
Transport Security		SS2008
Dialog Pool		SS2008
Fast Data Push		SS2008

Got questions? Want to contribute? Check out the SQL Server Community & Samples Discussion Forum and the
SQL Server Community Samples for Service Broker

Updated Wiki: Home

portegys — Fri, 27 Feb 2009 22:24:02 GMT

Sample	SQL Server 2005	SQL Server 2008
EventNotification	SS2005	SS2008
HelloWorld	SS2005	SS2008
HelloWorldService	SS2005	SS2008
ServiceBrokerInterface	SS2005	SS2008
ShoppingCart	SS2005	SS2008
Dialog Security		SS2008
Transport Security		SS2008
Dialog Pool		SS2008
Fast Data Push		SS2008

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

Updated Wiki: Home

portegys — Fri, 27 Feb 2009 20:09:24 GMT

Sample	SQL Server 2005	SQL Server 2008
EventNotification	SS2005	SS2008
HelloWorld	SS2005	SS2008
HelloWorldService	SS2005	SS2008
ServiceBrokerInterface	SS2005	SS2008
ShoppingCart	SS2005	SS2008
Dialog Security		SS2008
Transport Security		SS2008
Dialog Pool		SS2008
Fast Data Push		SS2008

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

Updated Wiki: SS2008!Readme_DialogSecurity

portegys — Wed, 11 Feb 2009 01:20:58 GMT

<html DIR="LTR" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:ddue="http://ddue.schemas.microsoft.com/authoring/2003/5" xmlns:MSHelp="http://msdn.microsoft.com/mshelp">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=utf-8" />
<META NAME="save" CONTENT="history" />
<title>Readme_DialogSecurity</title>

<Style TYPE="text/css">

body
{
background: #FFFFFF;
color: #000000;
font-family: Verdana;
font-size: medium;
font-style: normal;
font-weight: normal;
margin-top: 0;
margin-bottom: 0;
margin-left: 0;
margin-right: 0;
width: 100%;
}

div.#mainSection
{
font-size: 70%;
width: 100%;
padding-left: 10;
margin-right: 10;
}

div.#mainBody
{
font-size: 90%;
margin-top: 10;
padding-bottom: 20;
}

div.#header
{
background-color: #D2D2D2;
padding-top: 0;
padding-bottom: 0;
padding-left: 10;
padding-right: 0;
width: 100%;
}

div.#header table
{
border-bottom-color: #C8CDDE;
border-bottom-style: solid;
border-bottom-width: 1;
width: 100%;
}

span.#runningHeaderText
{
color: #003399;
font-size: 90%;
}

span.#nsrTitle
{
/* color: #003399;*/
font-size: 120%;
font-weight: 600;
}

div.#header table td
{
color: #000000;
font-size: 70%;
margin-top: 0;
margin-bottom: 0;
padding-right: 20;
}

div.#header table tr.#headerTableRow3 td
{
padding-bottom: 2;
padding-top: 5;
}

div.#header table.#bottomTable
{
border-top-color: #FFFFFF;
border-top-style: solid;
border-top-width: 1;
text-align: left;
}

div.#footer
{
font-size: 90%;
margin-top: 0;
margin-bottom: 0;
margin-left: -5;
margin-right: 0;
padding-top: 2;
padding-bottom: 2;
padding-left: 0;
padding-right: 0;
width: 100%;
}

hr.#footerHR
{
border-bottom-color: #EEEEFF;
border-bottom-style: solid;
border-bottom-width: 1;
border-top-color: C8CDDE;
border-top-style: solid;
border-top-width: 1;
height: 3;
color: #D2D2D2;
}

div.section
{
padding-top: 2;
padding-bottom: 2;
padding-right: 15;
width: 100%;
}

.heading
{
color: #000000;
font-weight: bold;
margin-top: 18;
margin-bottom: 8;
}

h1.heading
{
color: #000000;
font-size: 150%;
}

.subHeading
{
color: #000000;
font-weight: bold;
font-size: 150%;
margin-bottom: 4;
}

h2.subHeading
{
color: #000000;
font-weight: bold;
font-size: 130%;
}
h3.subHeading
{
color: #000000;
font-size: 125%;
font-weight: bold;
}

h4.subHeading
{
color: #000000;
font-size: 110%;
font-weight: bold;
}

h4.procedureHeading
{
color: #000080;
font-size: 110%;
font-weight: bold;
}

h5.subHeading
{
color: #000000;
font-size: 100%;
font-weight: bold;
}

img
{
padding-bottom: 10;
}

img.toggle
{
border: 0;
margin-right: 5;
padding-bottom: 10;
}

img.copyCodeImage
{
border: 0;
margin: 1;
margin-right: 3;
padding-bottom: 10;
}

img.downloadCodeImage
{
border: 0;
margin-right: 3;
padding-bottom: 10;
}

img.viewCodeImage
{
border: 0;
margin-right: 3;
padding-bottom: 10;
}

img.note
{
border: 0;
margin-right: 3;
padding-bottom: 10;
}

img.#membersOptionsFilterImage
{
border: 0;
margin-left: 10;
vertical-align: middle;
padding-bottom: 10;
}

img.#toggleAllImage
{
margin-left: 4;
vertical-align: middle;
padding-bottom: 10;
}

div.#mainSection table
{
border: 0;
font-size: 100%;
width: 100%;
margin-top: 5px;
margin-bottom: 15px;
}

div.#mainSection table tr
{
vertical-align: top;
}

div.#mainSection table th
{
text-align: left;
background: #D8D8D8;
border-bottom-color: #D8D8D8;
border-bottom-style: solid;
border-bottom-width: 1;
color: #000000;
padding-left: 5;
padding-right: 5;
}

div.#mainSection table td
{
background: #F2F2F2;
border-top-color: #D8D8D8;
border-top-style: solid;
border-top-width: 1;
padding-left: 5;
padding-right: 5;
}

div.#mainSection table td.imageCell
{
white-space: nowrap;
}

div.code
{
width: 98%;
}

div.code table
{
border: 0;
font-size: 95%;
margin-bottom: 5;
width: 100%
}

div.code table th
{
text-align: left;
background: #D8D8D8;
border-bottom-color: #D8D8D8;
border-bottom-style: solid;
border-bottom-width: 1;
color: #000000;
font-weight: bold;
padding-left: 5;
padding-right: 5;
}

div.code table td
{
background: #CCCCCC;
border-top-color: #D8D8D8;
border-top-style: solid;
border-top-width: 1;
padding-left: 5;
padding-right: 5;
padding-top: 5;
}

div.alert
{
margin-left: 10;
width: 98%;
}

div.alert table
{
border: 1;
font-size: 100%;
width: 100%;
border: solid 1 #DEDFEF;
}

div.alert table th
{
text-align: left;
background: #D8D8D8;
border-bottom-width: 0;
color: #000000;
padding-left: 5;
padding-right: 5;
border: solid 1 #DEDFEF;
}

div.alert table td
{
background: #FFFFFF;
border-top-color: #D8D8D8;
border-top-style: solid;
border-top-width: 1;
padding-left: 5;
padding-right: 5;
border: solid 1 #DEDFEF;
}

span.copyCode
{
color: #0000ff;
font-size: 90%;
font-weight: normal;
cursor: hand;
float: right;
display: inline;
text-align: right;
}

.downloadCode
{
color: #0000ff;
font-size: 90%;
font-weight: normal;
cursor: hand;
}

.viewCode
{
color: #0000ff;
font-size: 90%;
font-weight: normal;
cursor: hand;
}

div.code pre
{
font-family: Monospace, Courier New, Courier;
font-size: 105%;
color: #000000;
}

code
{
font-family: Monospace, Courier New, Courier;
font-size: 105%;
color: #000000;
}

dl
{
margin-top: 0;
padding-left: 1;
}

dd
{
margin-bottom: 0;
margin-left: 0;
padding-left: 20;
}

dd p
{
margin-top: 5;
}

ul
{
margin-left: 17;
list-style-type: disc;
}

ul ul
{
margin-bottom: 4;
margin-left: 17;
margin-top: 3;
list-style-type: disc;
}

ol
{
margin-left: 24;
list-style-type: decimal;
}

ol ol
{
margin-left: 24;
margin-top: 3;
list-style-type: lower-alpha;
}

li
{
margin-top: 0;
margin-bottom: 0;
padding-bottom: 0;
padding-top: 0;
margin-left: 5;
}

p
{
margin-bottom: 15;
}

.tip
{
color: #0000FF;
font-style: italic;
cursor:hand;
text-decoration:underline;
}

.math
{
font-family: Times New Roman;
font-size: 125%
}
.sourceCodeList
{
font-family: Verdana;
font-size: 90%;
}

pre.viewCode
{
width: 100%;
overflow: auto;
}

li:hover table, li.over table
{
background-color: #C0C0C0;
}

li:hover ul, li.over ul
{
background-color: #d2d2d2;
border: 1px solid #000;
display: block;
}

</style>
</head>
<body>


<div id="header">
<table width="100%" id="topTable">
<tr>
<td align="left">
<span id="nsrTitle">Readme_DialogSecurity</span>
</td>

</tr>
</table>
</div>
<div id="mainSection">
<div id="mainBody">

<font color="DarkGray">This topic is subject to change in future releases. Blank topics are included as placeholders. </font><p />
<span id="changeHistory">
</span>
<h1 class="heading">Scenario</h1><div id="sectionSection0" class="section"><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
<p xmlns="">This sample shows how to set up a secure dialog using certificates. Service
broker will always have a level of security at the transport level, which may include
encryption, but this is at a server level of granularity.
It does not secure conversations on a database-to-database basis. If this is required,
then dialog security can be used. Dialog security is also end-to-end as opposed to the
point-to-point connection-based security provided by transport security. Since conversations
may entail multiple hops through the use of forwarding, dialog security can provide
authentication and one-time encryption at the terminating services.
Certificate-based authentication also allows users to specify a window of time
in which authentication will be honored.</p>
<p xmlns="">The initiator and target certificates must be exchanged in order for them to
authenticate each other. This "out of band" exchange should be done with
a high level of trust, since a certificate bearer will be able to begin dialogs
and send messages to service broker services in the authenticating server.</p>
</content></div><h1 class="heading">Running the Sample</h1><div id="sectionSection1" class="section"><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
<div id="procedureSectionEBBDBHA" class="section" xmlns=""><ol><li>
<p xmlns="">This sample requires two server instances on different machines to avoid a port collision. It is essential
that the servers are configured to enable communication protocols. In this example, we will be using TCP,
so use the SQL Server Configuration Manager to make sure TCP is enabled on both servers.
To keep things simple, Windows authentication is used for transport security.
The transport security sample shows how to use certificates for this if needed.</p>
</li><li>
<p xmlns="">On one server, open the initiator project file in SQL Server Management Studio.
Open the target project file on the other server.</p>
</li><li>
<p xmlns="">Run the scripts, in order:</p>
<dl xmlns=""><dt>
1 - Initiator endpoint setup.sql.<br></br>
</dt><dt>
1 - Target endpoint setup.sql.<br></br>
</dt><dt>
2 - Initiator service setup.sql.<br></br>
</dt><dt>
2 - Target service setup.sql.<br></br>
</dt><dt>
3 - Initiator certification of target.sql.<br></br>
</dt><dt>
3 - Target certification of initiator.sql.<br></br>
</dt><dt>
4 - Initiator message send.sql.<br></br>
</dt><dt>
4 - Target message receive.sql.<br></br>
</dt><dt>
5 - Initiator cleanup.sql.<br></br>
</dt><dt>
5 - Target cleanup.sql.<br></br>
</dt></dl>
</li></ol></div>
</content></div></div>
<div id="footer">

© 2008 Microsoft Corporation. All rights reserved.
</a>

</div>
</div>
</body>
</html>

Updated Wiki: Home

ReedMe — Thu, 29 Jan 2009 23:08:37 GMT

Sample	SQL Server 2005	SQL Server 2008
EventNotification	SS2005	SS2008
HelloWorld	SS2005	SS2008
HelloWorldService	SS2005	SS2008
ServiceBrokerInterface	SS2005	SS2008
ShoppingCart	SS2005	SS2008

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

Updated Wiki: SS2008!Readme_ShoppingCart

bonniefe — Thu, 06 Nov 2008 23:53:12 GMT

Readme_ShoppingCart Sample

11/05/2008 21:36:06

The Shopping Cart sample uses the conversation group identifier to maintain state for a simple shopping cart application. The application uses the ServiceBrokerInterface sample.

Building and Installing the Sample

In Visual Studio 2005, open ShoppingCartCS.sln .
Build the solution by pressing F6, or by selecting Build Solution from the Build menu.
Open a command prompt, locate the Scripts folder, and then run the following command: * install all *The install script installs the SQL Server objects for the application, including the common language runtime (CLR) stored procedure that implements the ShoppingCartService service.

Running the Sample

Run the ShoppingCartClient.exe application from the sample directory. For simplicity, the client processes one order each time the client runs.
Click Create Order to create an order. Add items to the shopping cart by selecting the item from the Item list, and then clicking the Add Item button.
Click the *Service Broker Trace *tab at any time to see a summary of the Service Broker messages sent and received.
The ShoppingList and StateTable tables in the ssb_ShoppingCart database maintain state for the application. The CLR stored procedure updates the tables based on messages from the client. You can use Management Studio or sqlcmd to inspect these tables.

Uninstalling the Sample

Open a command prompt, locate the Scripts folder, and then run the following command: * uninstall all *
The uninstall script removes the SQL Server objects for the application.

Requirements

This sample requires Visual Studio 2005. Because the sample uses features of the CLR that were not available in earlier versions, versions of Visual Studio earlier than 2005 cannot build the sample.

Demonstrates

Item	Signature	Description
Stored Procedure	CREATE PROCEDURE name (@cgid uniqueidentifier)	Returns the state for the application. The result sets that are returned by this procedure must contain the conversation group identifier.
public method	public override bool LoadState(System.Data.Sql.SqlReader reader)	Reads the result sets that are provided by the stored procedure to restore state. This stored procedure must save the conversation group identifier in the class, because the Service Broker Interface does not provide the identifier to the SaveState method.
public method	public override void SaveState()	Saves state to the database.