Microsoft SQL Server Product Samples: Replication

Updated Wiki: Home

ReedMe — Wed, 27 Aug 2008 23:55:28 GMT

SQL Server 2008 samples download.
SQL Server 2005 samples download.

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
Sales Orders Mobile Replication Sample	SS2005	SS2008
Sales Orders Sample for Merge Replication	SS2005	SS2008
Subscriber Monitor Utility Sample for Merge Replication	SS2005	SS2008

Closed Issue: Problem with install SampleDB

ReedMe — Tue, 12 Aug 2008 21:37:29 GMT

While install SampleDB I've received the Error 1721: There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: InstallDatabase, location: C:\AdventureWorks_Log.idf') FOR ATTACh;"

What can I do?

My OS: Windows 2000,
SQL: Microsoft SQL Server 2005 Express Edition
SampleDB:AdventureWorksDB.msi (http://www.codeplex.com/MSFTDBProdSamples/Release/ProjectReleases.aspx?ReleaseId=5705)
Comments: Issues with AdventureWorks should be open @ connect.microsoft.com or http://www.codeplex.com/MSFTDBProdSamples/

Updated Wiki: SS2008!Subscriber Monitor Utility Sample for Merge Replication

bonniefe — Thu, 07 Aug 2008 08:31:22 GMT

Readme_Subscriber Monitor Utility Merge Replication Sample

08/06/2008 01:27:32

This sample works only with SQL Server 2005 and SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2005.
The Subscriber Monitor Utility sample is a Windows application that demonstrates how the Subscriber-side monitoring functionality provided by Replication Management Objects (RMO) is used to monitor merge subscriptions at the Subscriber. This sample solution can be built and run standalone at the Subscriber (using SubscriberMonitorUtility.exe). The SubscriberMonitor.dll assembly is also used by the Readme_Sales Orders Merge Replication Sample to display subscription status.

Scenario

A replication topology is generally monitored at the Publisher or Distributor. The Microsoft SQL Server Replication Monitor is the most important tool for monitoring replication, presenting a Publisher-focused view of all replication activity. For more information, see Monitoring Replication with Replication Monitor. SQL Server Management Studio provides access to Replication Monitor. However, merge replication is designed specifically to support disconnected clients. Because it is still necessary to monitor the status of a subscription, even when the Subscriber is disconnected from the Publisher, RMO provides classes that enable this Subscriber-side monitor functionality.

Languages

Features

The Subscriber Monitor Utility sample primarily demonstrates the facilities of RMO for monitoring merge subscriptions at the Subscriber. This sample is designed to run at a server that subscribes to a merge publication.

Prerequisites

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

Microsoft SQL Server 2005 or later version, including the following optionally installed components:
SQL Server Database Engine Services (including replication)
Client Tools
AdventureWorks Sample OLTP Database. This sample database is available on the Microsoft SQL Server Samples and Community Projects page on CodePlex.
The SQL Server samples. These samples are available on the Microsoft SQL Server Samples and Community Projects page on CodePlex. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.
.NET Framework SDK 2.0 or Microsoft Visual Studio 2005. You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework Documentation.

Required Permissions

This sample uses Windows Authentication. To run the sample, your Windows account must be a member of the replmonitor fixed database role or the db_owner fixed database role on the subscription database.

Building and Configuring the Sample

To build the sample solution, you will need to do the following:
To build the Subscriber Monitor Utility sample Install the replication samples. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.At the command prompt, navigate to the SQL Server samples installation directory. The default is C:\Program Files\Microsoft SQL Server\100\Samples\. Execute the following at a .NET Framework or Microsoft Visual Studio 2005 command prompt:sn -k SampleKey.snkNote: You can skip this step if this key was previously created for use with another sample. Navigate to the SubscriberMonitorUtility folder in the replication samples directory and open the SubscriberMonitorUtility.sln solution file in Visual Studio. The location of this folder for a default installation is C:\Program Files\Microsoft SQL Server\100\Samples\Replication\Merge\SubscriberMonitorUtility\CS. Build the solution.

Running the Sample

To run the sample, you need to navigate to the location of the built executable and run it.
To run the Subscriber Monitor Utility sample at the Subscriber Start SubscriberMonitorUtility.exe from Visual Studio or from the command prompt. In the Select Subscription to Monitor dialog box, choose an instance of SQL Server from the Local Server Name drop-down box.Select a subscription to monitor from the Available Subscriptions drop-down list box.(Optional) Click the Edit button to change subscription properties.Click Connect. Select a Merge Agent session from the Merge Sessions tree view. (Optional) Click the Refresh button to refresh the session list.

Comments

Samples are provided for educational purposes only. They have not been tested in nor are they intended to be used in a production environment. Microsoft does not provide technical support for these samples. Sample applications and assemblies should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

Updated Wiki: SS2005!Subscriber Monitor Utility Sample for Merge Replication

bonniefe — Thu, 07 Aug 2008 08:31:02 GMT

Subscriber Monitor Utility Sample for Merge Replication

Updated: 5 December 2005
The Subscriber Monitor Utility sample is a Windows application that demonstrates how the Subscriber-side monitoring functionality provided by Replication Management Objects (RMO) is used to monitor merge subscriptions at the Subscriber. This sample solution can be built and run standalone at the Subscriber (using SubscriberMonitorUtility.exe). The SubscriberMonitor.dll assembly is also used by the Sales Orders Sample for Merge Replication to display subscription status.

Scenario

Languages

Features

Prerequisites

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

Microsoft SQL Server 2005, including the following optionally installed components:
SQL Server Database Services (including replication)
Client Connectivity Components
Programming Models
Development Tools (including SDK)
Samples
.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.

Required Permissions

Building and Configuring the Sample

To build the sample solution, you will need to do the following:
To build the Subscriber Monitor Utility sample Install the replication samples. For more information, see Installing Samples.At the command prompt, navigate to the SQL Server 2005 samples installation directory. The default is C:\Program Files\Microsoft SQL Server\90\Samples. Execute the following at a .NET Framework or Microsoft Visual Studio 2005 command prompt:sn -k SampleKey.snkNote: You can skip this step if this key was previously created for use with another sample. Navigate to the SubscriberMonitorUtility folder in the replication samples directory and open the SubscriberMonitorUtility.sln solution file in Microsoft Visual Studio 2005. The location of this folder for a default installation is C:\Program Files\Microsoft SQL Server\90\Samples\Replication\Merge\SubscriberMonitorUtility\CS. Build the solution.

Running the Sample

To run the sample, you need to navigate to the location of the built executable and run it.
To run the Subscriber Monitor Utility sample at the Subscriber Start SubscriberMonitorUtility.exe from Visual Studio 2005 or from the command prompt. In the Select Subscription to Monitor dialog box, choose an instance of SQL Server from the Local Server Name drop-down box.Select a subscription to monitor from the Available Subscriptions drop-down list box.(Optional) Click the Edit button to change subscription properties.Click Connect. Select a Merge Agent session from the Merge Sessions tree view. (Optional) Click the Refresh button to refresh the session list.

Comments

Change History

Release	History
5 December 2005	Changed content: Updated key creation and deployment information to reflect sample updates.

Updated Wiki: SS2008!Sales Orders Sample for Merge Replication

bonniefe — Thu, 07 Aug 2008 08:30:46 GMT

Readme_Sales Orders Merge Replication Sample

08/06/2008 01:27:32

This sample works only with SQL Server 2005 and SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2005.
This readme file details how to install and run the Sales Orders sample. This file also details any known issues with the sample.

Scenario

This sample highlights a merge replication topology for delivering data to mobile users, and it also demonstrates the programmability features of merge replication in SQL Server. The sample is a Windows Forms-based application that uses standard Microsoft data access technologies and merge replication to enable a salesperson to maintain her own local data while synchronizing periodically with the home office. This sample is supported for Subscribers running all editions of SQL Server. The publication also supports SQL Server Compact 3.5 Subscribers. For more information about this sample scenario, see Sales Orders Sample Scenario.

Languages

C#
Transact-SQL

Features

The Sales Orders sample demonstrates the following features of merge replication:

Replication Management Objects (RMO).
Parameterized row filters.
Precomputed partitions.
Client-requested partitioned snapshot.
Article type-based performance optimizations.
SQL Server Compact 3.5 and SQL Server Express Subscribers.
Automatic identity range management.
Business logic handlers.
Web synchronization (optional). For more information about how these replication features are demonstrated in the sample, see Sales Orders Sample Implementation Details.

Prerequisites

This sample is supported only on default installations of SQL Server. Named instances are not supported. Before running this sample, make sure the following software is installed:

SQL Server 2005 or later version, including the following optionally installed components:
SQL Server Database Engine Services (including replication)
Client Tools
AdventureWorks Sample OLTP Database. This sample database is available on the Microsoft SQL Server Samples and Community Projects page on CodePlex.
The SQL Server samples. These samples are available on the Microsoft SQL Server Samples and Community Projects page on CodePlex. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.
.NET Framework SDK 2.0 or Microsoft Visual Studio 2005. You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework Documentation.

Required Permissions

The permissions needed to configure and run the Sales Orders sample are based on replication security requirements, and are as follows:

To run InstallSalesOrdersSample.bat, which configures replication, creates the AdvWorksSalesOrders publication, and generates the initial snapshot, your Windows account must be a member of the sysadmin fixed server role at the Publisher.
The Sales Orders sample does various Database Engine and replication tasks, including creating the AdventureWorksLocal database, creating the local Subscription, and running the Merge Agent to initialize, reinitialize or synchronize the subscription. In order to successfully run the sample executable (SalesOrders.exe) at the Subscriber, your Windows account must have at least CREATE DATABASE permissions at the Subscriber. Note: When the local database and subscription exists, your Windows account must be at least a member of the db_owner fixed database role on the AdventureWorksLocal database at the Subscriber to run the application.
To initialize the subscription and synchronize with the Publisher, the Windows account used to connect to the Publisher (or with the Web server when using Web synchronization) must meet the following requirements:
Have a valid login at the Publisher associated with a user in the publication database.
Have a valid login at the Distributor associated with a user in the distribution database (of the guest user).
Be a member of the publication access list (PAL) for the AdvWorksSalesOrders publication.

Building and Configuring the Sample

To build the sample project and configure the replication topology, you will need to do the following:

At the Publisher, run the replication installation script.
(Optional) Configure the Internet Information Services (IIS) server to support Web synchronization for merge replication. If this is not done, you cannot use the Web synchronization feature of the sample.
At the Subscriber, modify the configuration settings in the app.config file of the sample.
At the Subscriber, build the sample using Visual Studio 2005 or the .NET Framework 2.0 SDK.
At the Subscriber, place a copy of the BusinessLogic.dll assembly in the C:\Program Files\Microsoft SQL Server\100\COM directory. When using Web synchronization, you must also place a copy of BusinessLogic.dll in the C:\Program Files\Microsoft SQL Server\100\COM directory on the Web server.

To configure the Sales Orders sample at the Publisher

Ensure that the AdventureWorks sample database has been installed and the database is attached. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.
Ensure that the SQL Server Database Engine samples have been installed. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.
Ensure that SQL Server Agent is running. You can view the status of and start this service from Object Explorer in SQL Server Management Studio.
Navigate to the installation location for the Sales Order sample scripts. The default is C:\Program Files\Microsoft SQL Server\100\Samples\Replication\Merge\SalesOrders\Scripts.
(Optional) Configure Secure Sockets Layer (SSL) at the Publisher or at the server used for Web synchronization. SSL is required for communication between the IIS server and all Subscribers. To configure SSL, specify a server certificate for the IIS server to use.
Execute InstallSalesOrdersSample.bat and when prompted enter the login (in the case-sensitive format "DOMAIN\login") and password for the Windows account under which the Snapshot Agent job will run. This calls sqlcmd.exe to execute CreateAdvWorksSalesOrdersPublication.sql, which does the following:
Checks that replication has been configured on the local server, and if not configures it as a Publisher with local Distributor using the distribution database.
Drops and re-creates the stored procedures and user-defined functions used for data access at the client.
Drops and re-creates the AdvWorksSalesOrders Publication.
Adds articles to the publication.
Registers the business logic handler at the Distributor.
Starts the Snapshot Agent job to generate the initial snapshot. The batch file can also automatically configure a virtual directory at the Publisher to support Web synchronization. If you choose not configure the virtual directory at the Publisher during installation, or if you plan to use a separate Web server, you must run the Configure Web Synchronization Wizard prior to using the Web synchronization features of the sample.
(Optional) Run the Configure Web Synchronization Wizard to configure an IIS server to support Web synchronization. Skip this step if InstallSalesOrdersSample.bat successfully created the virtual directory or if you will not use Web synchronization. For complete instructions about using this wizard, see How to: Configure IIS for Web Synchronization.
Before continuing, ensure that the Snapshot Agent job for the AdvWorksSalesOrders publication has successfully completed. The status of this job can be viewed using Replication Monitor. For information about using Replication Monitor to view the status of a Snapshot Agent job, see the topic How to: View Information and Perform Tasks for the Agents Associated With a Publication (Replication Monitor) in SQL Server Books Online.

To build and configure the Sales Orders sample at the Subscriber

At the command prompt, navigate to the SQL Server samples installation directory. The default is C:\Program Files\Microsoft SQL Server\100\Samples\.
Execute the following at a .NET Framework or Microsoft Visual Studio 2005 command prompt: sn -k SampleKey.snk *Note: You can skip this step if this key was previously created for use with another sample. *
Navigate to the installation location for the Sales Orders sample solution in Microsoft Visual C#. The default is C:\Program Files\Microsoft SQL Server\100\Samples\Replication\Merge\SalesOrders\CS.
Open the SalesOrders.sln solution file in Visual Studio 2005.
Build the project.
In the project output folder, edit the SalesOrders.exe.config file and change the following:
Replace the value of the Subscriber key with the name of the local server.
Replace the value of the Publisher key with the name of the server configured previously as the Publisher.
(Optional) Replace the value of the WebSynchronizationUrl key when connecting to the Publisher using Web synchronization. This can also be done at run time.
(Optional) Use the SyncWhenConnectedInterval key to set the interval between synchronizations, in seconds, when using the synchronize-when-connected functionality. Note: Replication does not support localhost for server names.
Place a copy of the BusinessLogic.dll assembly in the C:\Program Files\Microsoft SQL Server\100\COM directory.
(Optional) If using Web synchronization, place a copy of the BusinessLogic.dll assembly in the C:\Program Files\Microsoft SQL Server\100\COM directory on the Web server.

Running the Sample

To run the Sales Orders sample and synchronize data

Ensure that remote connections are enabled at the Publisher and at the Subscriber (TCP/IP or Named Pipes) and that the SQL Server Agent service is running.
(Optional) At the Subscriber, test the Web synchronization connection by connecting to the Web server in diagnostic mode following the instructions on "To configure client certificates at the Subscriber" in How to: Configure Web Synchronization for Merge Replication (Replication Transact-SQL Programming). Note: If an HTTP error occurs when using Web synchronization, open Internet Explorer, and from the Tools menu select Internet Options, Connections, and LAN Settings. Ensure that Automatically detect settings is disabled.
Start SalesOrders.exe from Visual Studio 2005 or from the command prompt. When the application runs for the first time, the subscription database and subscription are created and the Merge Agent is started to initialize the subscription.
After the subscription data has been initialized, the Sales Orders form will load, displaying a list of existing orders that belong to salesperson "adventure-works\garrett1".
Using the Sales Orders form, you can make the following changes to sales data:
Edit sales order information.
Add a new item to a sales order.
Delete an item from a sales order.
Change the ordered quantity for an item in a sales order.
Select a synchronization method from the Synchronize menu to synchronize the subscription.
(Optional) Check Synchronize When Connected to automatically synchronize the subscription. Set the synchronization interval for background synchronization using the SyncWhenConnectedInterval key in the app.config file. Note: The Synchronize When Connected feature is not available when running on Microsoft Windows 2000 platforms. For more information, see Sales Orders Sample Implementation Details.

To use advanced synchronization options of the Sales Orders sample

From Advanced in the Synchronize menu, choose one of the following options:
(Optional) Select a reinitialize option to reinitialize the subscription.
(Optional) Select Web Synchronization Options and supply the Internet URL and the Windows Authentication credentials used to access the Web server over a secure HTTPS connection. To use this option, you must have already configured an IIS server for Web synchronization. Note: Upload-only or download-only synchronization is not supported with Web synchronization. When Web synchronization is enabled, the Only Upload Data menu item is disabled.
(Optional) Select Get Subscription Status to view the results the most recent Merge Agent sessions.

Removing the Sample

Use the following procedure to remove the Sales Orders sample.

To delete the subscription only

At the Subscriber, execute the following Transact-SQL script to delete the pull subscription. * {" -- This batch is executed at the Subscriber to remove

-- the Sales Orders sample subscription.
DECLARE @publisher AS sysname;

-- change this value to the name of the Publisher server.
SET @publisher = N'PUBSERVER';

USE AdventureWorksLocal
EXEC sp_dropmergepullsubscription
@publisher = @publisher,
@publisher_db = N'AdventureWorks',
@publication = N'AdvWorksSalesOrders';
GO "}*

At the Publisher, execute the following Transact-SQL script to unregister the pull subscription. * {" -- This batch is executed at the Publisher to remove

-- the Sales Orders sample subscription.
DECLARE @subscriber AS sysname;

-- change this value to the name of the Subscriber server.
SET @subscriber = N'SUBSERVER';

USE AdventureWorks
EXEC sp_dropmergesubscription
@publication = N'AdvWorksSalesOrders',
@subscriber = @subscriber,
@subscriber_db = N'AdventureWorksLocal';
GO "}*

To remove the Sales Orders sample

At the Publisher, navigate to the installation location for the Sales Order sample scripts. The default is C:\Program Files\Microsoft SQL Server\100\Samples\Replication\Merge\SalesOrders\Scripts.
Execute the batch file RemoveSalesOrdersSample.bat.
When prompted, type "Y" and press Enter to remove all replication objects at the Publisher, remove all replication objects in the subscription database, and uninstall publishing and distribution at the Publisher. *Important: When using this script, all replication infrastructure will be removed. If you have created other publications that use this Publisher or Distributor, do not execute DropAdvWorksSalesOrdersPublication.sql. Instead, you should remove the AdvWorksSalesOrders publication manually. For more information, see How to: Delete a Publication (SQL Server Management Studio) or How to: Delete a Publication (Replication Transact-SQL Programming) in SQL Server Books Online. *
At the Subscriber on the AdventureWorksLocal database, execute sp_removedbreplication (Transact-SQL).
Change the database context to the master database and execute DROP DATABASE AdventureWorksLocal .

Comments

Samples are provided for educational purposes only. They are not intended to be used in a production environment and have not been tested in a production environment. Microsoft does not provide technical support for these samples. Sample applications and assemblies should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.

Updated Wiki: SS2005!Sales Orders Sample for Merge Replication

bonniefe — Thu, 07 Aug 2008 08:30:24 GMT

Sales Orders Sample for Merge Replication

Updated: 14 April 2006
This readme file details how to install and run the Sales Orders sample. This file also details any known issues with the sample.

Scenario

This sample highlights a merge replication topology for delivering data to mobile users, and it also demonstrates the programmability features of merge replication in SQL Server 2005. The sample is a Windows Forms-based application that uses standard Microsoft data access technologies and merge replication to enable a salesperson to maintain her own local data while synchronizing periodically with the home office. This sample is supported for Subscribers running all editions of SQL Server 2005. The publication also supports SQL Server 2005 Compact Edition Subscribers. For more information about this sample scenario, see Sales Orders Sample Scenario.

Languages

C#
Transact-SQL

Features

The Sales Orders sample demonstrates the following features of merge replication:

Replication Management Objects (RMO).
Parameterized row filters.
Precomputed partitions.
Client-requested partitioned snapshot.
Article type-based performance optimizations.
SQL Server 2005 Compact Edition and Express Edition Subscribers.
Automatic identity range management.
Business logic handlers.
Web synchronization (optional). For more information about how these replication features are demonstrated in the sample, see Sales Orders Sample Implementation Details.

Prerequisites

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

SQL Server 2005 Service Pack 1 (SP1), including the following optionally installed components:
SQL Server Database Services (including replication)
Client Connectivity Components
Programming Models
Development Tools (including SDK)
AdventureWorks Sample OLTP Database. This sample database is included with SQL Server 2005 and is also available at the SQL Server Developer Center.
The SQL Server 2005 samples. These samples are included with SQL Server 2005 and are also available at the SQL Server Developer Center. For more information, see Installing Samples.
.NET Framework SDK 2.0 or Microsoft Visual Studio 2005. You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework SDK. *Note: To generate the initial snapshot, you must have SQL Server 2005 SP1 applied at the Publisher. To use this sample on a SQL Server 2005 Publisher without SP1 applied, you must first drop and re-create the FKSalesOrderDetailSalesOrderHeader_SalesOrderID FOREIGN KEY constraint on the SalesOrderHeader table without the ON DELETE CASCADE clause. *

Required Permissions

The permissions needed to configure and run the Sales Orders sample are based on replication security requirements, and are as follows:

To run InstallSalesOrdersSample.bat, which configures replication, creates the AdvWorksSalesOrders publication, and generates the initial snapshot, your Windows account must be a member of the sysadmin fixed server role at the Publisher.
The Sales Orders sample does various Database Engine and replication tasks, including creating the AdventureWorksLocal database, creating the local Subscription, and running the Merge Agent to initialize, reinitialize or synchronize the subscription. In order to successfully run the sample executable (SalesOrders.exe) at the Subscriber, your Windows account must have at least CREATE DATABASE permissions at the Subscriber. Note: When the local database and subscription exists, your Windows account must be at least a member of the db_owner fixed database role on the AdventureWorksLocal database at the Subscriber to run the application.
To initialize the subscription and synchronize with the Publisher, the Windows account used to connect to the Publisher (or with the Web server when using Web synchronization) must meet the following requirements:
Have a valid login at the Publisher associated with a user in the publication database.
Have a valid login at the Distributor associated with a user in the distribution database (of the guest user).
Be a member of the publication access list (PAL) for the AdvWorksSalesOrders publication.

Building and Configuring the Sample

To build the sample project and configure the replication topology, you will need to do the following:

At the Publisher, run the replication installation script.
(Optional) Configure the Internet Information Services (IIS) server to support Web synchronization for merge replication. If this is not done, you cannot use the Web synchronization feature of the sample.
At the Subscriber, modify the configuration settings in the app.config file of the sample.
At the Subscriber, build the sample using Visual Studio 2005 or the .NET Framework 2.0 SDK.
At the Subscriber, place a copy of the BusinessLogic.dll assembly in the C:\Program Files\Microsoft SQL Server\90\COM directory. When using Web synchronization, you must also place a copy of BusinessLogic.dll in the C:\Program Files\Microsoft SQL Server\90\COM directory on the Web server.

To configure the Sales Orders sample at the Publisher

Ensure that the AdventureWorks sample database has been installed and the database is attached. If the database is not attached, see Installing AdventureWorks Sample Databases and Samples in SQL Server Books Online.
Ensure that the SQL Server Database Engine samples have been installed.For more information, see Installing Samples.
Ensure that SQL Server Agent is running. You can view the status of and start this service from Object Explorer in SQL Server Management Studio.
Navigate to the installation location for the Sales Order sample scripts. The default is C:\Program Files\Microsoft SQL Server\90\Samples\Replication\Merge\SalesOrders\Scripts.
(Optional) Configure Secure Sockets Layer (SSL) at the Publisher or at the server used for Web synchronization. SSL is required for communication between the IIS server and all Subscribers. To configure SSL, specify a server certificate for the IIS server to use.
Execute InstallSalesOrdersSample.bat and when prompted enter the login (in the case-sensitive format "DOMAIN\login") and password for the Windows account under which the Snapshot Agent job will run. This calls sqlcmd.exe to execute CreateAdvWorksSalesOrdersPublication.sql, which does the following:
Checks that replication has been configured on the local server, and if not configures it as a Publisher with local Distributor using the distribution database.
Drops and re-creates the stored procedures and user-defined functions used for data access at the client.
Drops and re-creates the AdvWorksSalesOrders Publication.
Adds articles to the publication.
Registers the business logic handler at the Distributor.
Starts the Snapshot Agent job to generate the initial snapshot. The batch file can also automatically configure a virtual directory at the Publisher to support Web synchronization. If you choose not configure the virtual directory at the Publisher during installation, or if you plan to use a separate Web server, you must run the Configure Web Synchronization Wizard prior to using the Web synchronization features of the sample.
(Optional) Run the Configure Web Synchronization Wizard to configure an IIS server to support Web synchronization. Skip this step if InstallSalesOrdersSample.bat successfully created the virtual directory or if you will not use Web synchronization. For complete instructions about using this wizard, see How to: Configure an IIS Server for Web Synchronization (SQL Server Management Studio).
Before continuing, ensure that the Snapshot Agent job for the AdvWorksSalesOrders publication has successfully completed. The status of this job can be viewed using Replication Monitor. For information about using Replication Monitor to view the status of a Snapshot Agent job, see the topic How to: View Information and Perform Tasks for the Agents Associated With a Publication (Replication Monitor) in SQL Server Books Online.

To build and configure the Sales Orders sample at the Subscriber

At the command prompt, navigate to the SQL Server 2005 samples installation directory. The default is C:\Program Files\Microsoft SQL Server\90\Samples.
Execute the following at a .NET Framework or Microsoft Visual Studio 2005 command prompt: sn -k SampleKey.snk *Note: You can skip this step if this key was previously created for use with another sample. *
Navigate to the installation location for the Sales Orders sample solution in Microsoft Visual C#. The default is C:\Program Files\Microsoft SQL Server\90\Samples\Replication\Merge\SalesOrders\CS.
Open the SalesOrders.sln solution file in Visual Studio 2005.
Build the project.
In the project output folder, edit the SalesOrders.exe.config file and change the following:
Replace the value of the Subscriber key with the name of the local server.
Replace the value of the Publisher key with the name of the server configured previously as the Publisher.
(Optional) Replace the value of the WebSynchronizationUrl key when connecting to the Publisher using Web synchronization. This can also be done at run time.
(Optional) Use the SyncWhenConnectedInterval key to set the interval between synchronizations, in seconds, when using the synchronize-when-connected functionality. Note: Replication does not support localhost for server names.
Place a copy of the BusinessLogic.dll assembly in the C:\Program Files\Microsoft SQL Server\90\COM directory.
(Optional) If using Web synchronization, place a copy of the BusinessLogic.dll assembly in the C:\Program Files\Microsoft SQL Server\90\COM directory on the Web server.

Running the Sample

To run the Sales Orders sample and synchronize data

Ensure that remote connections are enabled at the Publisher and at the Subscriber (TCP/IP or Named Pipes) and that the SQL Server Agent service is running.
(Optional) At the Subscriber, test the Web synchronization connection by connecting to the Web server in diagnostic mode following the instructions on "To configure client certificates at the Subscriber" in How to: Configure Web Synchronization for Merge Replication (Replication Transact-SQL Programming). Note: If an HTTP error occurs when using Web synchronization, open Internet Explorer, and from the Tools menu select Internet Options, Connections, and LAN Settings. Ensure that Automatically detect settings is disabled.
Start SalesOrders.exe from Visual Studio 2005 or from the command prompt. When the application runs for the first time, the subscription database and subscription are created and the Merge Agent is started to initialize the subscription.
After the subscription data has been initialized, the Sales Orders form will load, displaying a list of existing orders that belong to salesperson "adventure-works\garrett1".
Using the Sales Orders form, you can make the following changes to sales data:
Edit sales order information.
Add a new item to a sales order.
Delete an item from a sales order.
Change the ordered quantity for an item in a sales order.
Select a synchronization method from the Synchronize menu to synchronize the subscription.
(Optional) Check Synchronize When Connected to automatically synchronize the subscription. Set the synchronization interval for background synchronization using the SyncWhenConnectedInterval key in the app.config file. Note: The Synchronize When Connected feature is not available when running on Microsoft Windows 2000 platforms. For more information, see Sales Orders Sample Implementation Details.

To use advanced synchronization options of the Sales Orders sample

From Advanced in the Synchronize menu, choose one of the following options:
(Optional) Select a reinitialize option to reinitialize the subscription.
(Optional) Select Web Synchronization Options and supply the Internet URL and the Windows Authentication credentials used to access the Web server over a secure HTTPS connection. To use this option, you must have already configured an IIS server for Web synchronization. Note: Upload-only or download-only synchronization is not supported with Web synchronization. When Web synchronization is enabled, the Only Upload Data menu item is disabled.
(Optional) Select Get Subscription Status to view the results the most recent Merge Agent sessions.

Removing the Sample

Use the following procedure to remove the Sales Orders sample.

To delete the subscription only

At the Subscriber, execute the following Transact-SQL script to delete the pull subscription.
At the Publisher, execute the following Transact-SQL script to unregister the pull subscription.

To remove the Sales Orders sample

At the Publisher, navigate to the installation location for the Sales Order sample scripts. The default is C:\Program Files\Microsoft SQL Server\90\Samples\Replication\Merge\SalesOrders\Scripts.
Execute the batch file RemoveSalesOrdersSample.bat.
When prompted, type "Y" and press Enter to remove all replication objects at the Publisher, remove all replication objects in the subscription database, and uninstall publishing and distribution at the Publisher. *Important: When using this script, all replication infrastructure will be removed. If you have created other publications that use this Publisher or Distributor, do not execute DropAdvWorksSalesOrdersPublication.sql. Instead, you should remove the AdvWorksSalesOrders publication manually. For more information, see How to: Delete a Publication (SQL Server Management Studio) or How to: Delete a Publication (Replication Transact-SQL Programming) in SQL Server Books Online. *
At the Subscriber on the AdventureWorksLocal database, execute sp_removedbreplication.
Change the database context to the master database and execute DROP DATABASE AdventureWorksLocal .

Comments

Change History

Release	History
14 April 2006	Changed content: Updated the requirements to SQL Server 2005 SP1. Added a note with information on how to run the sample on a SQL Server 2005 Publisher.
5 December 2005	Changed content: Updated deployment steps. Updated key creation and deployment information to reflect sample updates.

Updated Wiki: SS2008!Sales Orders Mobile Replication Sample

bonniefe — Thu, 07 Aug 2008 08:30:04 GMT

Readme_Sales Orders Mobile Replication Sample

08/06/2008 01:27:32

This sample works only with SQL Server 2005 and SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2005. This sample is the SQL Server Compact 3.5 Subscriber version of the Sales Orders Sample for Merge Replication. This sample highlights using Microsoft SQL Server Compact 3.5 as a Subscriber in a merge replication topology for delivering data to mobile users. It also demonstrates the programmability features of replication in SQL Server Compact 3.5. The sample is a Windows Forms-based application that uses standard Microsoft data access technologies and merge replication to enable a salesperson to maintain her own local data while synchronizing periodically with the home office. The publication used by this sample is created when you install the Sales Orders Sample for Merge Replication. For more information about the replication scenario used in this sample, see Sales Orders Sample Scenario.

Languages

*
C#

Prerequisites

This sample is supported only on default installations of SQL Server. Named instances are not supported. Before running this sample, make sure the following software is installed on the development computer:

Microsoft Compact 2.0.
.NET Framework SDK 2.0 or Microsoft Visual Studio 2005. For more information, see Installing the .NET Framework Documentation.
Microsoft SQL Server Compact 3.5.
Microsoft ActiveSync 4.0 or later versions.
The SQL Server samples. These samples are available on the Microsoft SQL Server Samples and Community Projects page on CodePlex. For more information, see Considerations for Installing SQL Server Samples and Sample Databases. You must also have either a mobile device or a mobile device emulator (included with Microsoft Visual Studio 2005) with at least 15 MB of free memory on which to deploy and run the sample.

To initialize the subscription and download sales order data to the device, you must have a SQL Server Publisher configured to run the Sales Orders Sample for Merge Replication.

Required Permissions

The permissions required to configure and run the Sales Orders sample are based on replication security requirements, and are as follows:

To run InstallSalesOrdersSample.bat at the Publisher, your Windows account must be a member of the sysadmin fixed server role at the Publisher. This batch file configures replication, creates the AdvWorksSalesOrders publication, and generates the initial snapshot.
To initialize the subscription and synchronize data with the Publisher, the Windows account used to connect to the Web server must meet the following requirements:
Have a valid login at the Publisher associated with a user in the publication database.
Have a valid login at the Distributor associated with a user in the distribution database (or the guest user).
Be a member of the publication access list (PAL) for the AdvWorksSalesOrders publication. Note: When you use an anonymous connection to the Web server, the IIS anonymous Windows account is used to connect to the Publisher.
To connect to the Web server using Secure Sockets Layer (SSL) encryption, you must have a copy of the root certificate of the server certificate used to secure the Web server installed as a root certificate on the device. If the Web server is configured to require client certificates, you must also have a valid certificate installed as a personal certificate on the device.

Building and Configuring the Sample

To configure the replication topology and build and deploy the sample project:

At the Publisher, run the publication installation script from the Sales Orders sample.
Build the Sales Orders sample and deploy the business logic handler assembly on the Web server.
Run the Configure Web Synchronization wizard to configure the virtual directory.
Build and deploy the sample to a device or device emulator using Visual Studio 2005.

To configure the Publisher, and build and deploy the sample project

On a computer that is running SQL Server 2005 or a later version, execute the installation script from the Sales Orders Sample for Merge Replication to create the AdvWorksSalesOrders publication at the Publisher.
At the command prompt, navigate to the SQL Server samples installation directory. The default is C:\Program Files\Microsoft SQL Server\100\Samples\.
Execute the following at a .NET Framework or Microsoft Visual Studio 2005 command prompt: sn -k SampleKey.snk *Note: You can skip this step if this key was previously created for use with another sample. *
Navigate to the installation location for the Sales Orders sample solution in Microsoft Visual C#. The default is C:\Program Files\Microsoft SQL Server\100\Samples\Replication\Merge\SalesOrders\CS.
Open the SalesOrders.sln solution file in Visual Studio 2005.
Build the project.
Place a copy of the BusinessLogic.dll assembly in the C:\Program Files\Microsoft SQL Server\100\COM directory on the Web server.
Run the Configure Web synchronization Wizard to create a virtual directory name "SalesOrdersMobile." For information about how to run this wizard, follow the steps in the How To: Configure Connectivity with the Configure Web Synchronization Wizard topic in SQL Server Compact 3.5 Books Online. Note: When client certificates are required to connect to the Web server, you must have a valid personal certificate installed on the device.
If using an anonymous connection to the Web server, create a login at the Publisher for the Windows account used for anonymous access, create a user in the AdventureWorks database for this login, and add this user to the PAL for the AdvWorksSalesOrders publication. For more information, see How to: Manage Logins in the Publication Access List (SQL Server Management Studio).
Navigate to the installation location for the Sales Orders Mobile sample solution in Microsoft Visual C#. The default is C:\Program Files\Microsoft SQL Server\100\Samples\Replication\Merge\SalesOrdersMobile\CS.
Open the SalesOrdersMobile.sln solution file in Visual Studio 2005.
Connect the device or device emulator and start ActiveSync.
Build and deploy the project to the device.

Running the Sample

To run the Sales Orders Mobile sample and synchronize data

Cradle the device and ensure that ActiveSync is running.
To secure the connection to the Web server using SSL, export the root certificate of the server certificate used to secure the SalesOrdersMobile virtual directory (in DER encoded binary X.509 format), copy it to the device, and tap to install it as a root certificate on the device. When client certificates are required to connect to the Web server, you must also have a valid personal certificate installed on the device. Security Note: If you use Basic Authentication to connect to the Web server, you should use SSL to encrypt the connection to the Web server. This protects the Windows credentials.
On the device, start Internet Explorer and browse to one of the following URLs:
http://webserver/SalesOrdersMobile/sqlcesa30.dll?diag - when using anonymous access to the Web server.
https://webserver/SalesOrdersMobile/sqlcesa30.dll?diag - when connecting to the Web server using SSL and specifying a Windows login and password to use for Basic Authentication.
On the device or device emulator, start the SalesOrdersMobile program. When run for the first time, the program creates the mobile subscription database (\My Documents\AWMobile.sdf).
On the Settings page, enter the name of the Publisher and the URL of the Web server in one of the following formats:
http://webserver/SalesOrdersMobile/sqlcesa30.dll. This URL is used when the Connect anonymously to server box is checked.
https://webserver/SalesOrdersMobile/sqlcesa30.dll. This URL is used when the Connect anonymously to server box is unchecked. You must also specify a Windows login and password in the Windows login and Password fields, where these values are the credentials that correspond to a Windows login at the Publisher and Distributor.
Tap Save to save these settings.
On the Synchronize page, verify the value in the Hostname field, select Full (recommended) for Sync type, and then tap Synchronize. The device connects to the specified Web server to create, initialize, and download subscription data for the application.

To update sales order data and synchronize with the Publisher

With the subscription initialized, on the File menu, tap View Orders, and select a customer from the Customers list.
To update an existing order, tap on an existing order in the Orders table, then do one of the following:
To update an existing item, double-tap an item in the Order Items grid, change the Quantity value for the selected item, and then tap Save.
To add a new item to the order, tap Add New, select the product from the Category and Product lists, set the order quantity in the Quantity field, and then tap Save.
To delete an existing item from an order, select the item in the Order Items grid, and then tap Delete.
Tap Synchronize from the Tools menu, select either Full (recommended) or Upload only from the Sync type list, and then tap Synchronize. © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2005!Sales Orders Mobile Replication Sample

bonniefe — Thu, 07 Aug 2008 08:29:44 GMT

Sales Orders Sample for Devices

New: 14 April 2006
This sample is the mobile device version of the Sales Orders Sample for Merge Replication. This sample highlights using Microsoft SQL Server 2005 Compact Edition (SQL Server Compact Edition) as a Subscriber in a merge replication topology for delivering data to mobile device users. It also demonstrates the programmability features of replication in SQL Server Compact Edition. The sample is a Windows Forms-based application that uses standard Microsoft data access technologies and merge replication to enable a salesperson to maintain her own local data while synchronizing periodically with the home office. The publication used by this sample is created when you install the Sales Orders Sample for Merge Replication. For more information about the replication scenario used in this sample, see Sales Orders Sample Scenario.

Languages

Prerequisites

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

.NET Framework SDK 2.0 or Microsoft Visual Studio 2005 Service Pack 1 (SP1) or later versions. For more information, see Installing the .NET Framework SDK.
Microsoft SQL Server 2005 Compact Edition (SQL Server Compact Edition).

*
Microsoft ActiveSync 4.0 or later versions.

SQL Server 2005 Service Pack 2 (SP2) or later versions.
The SQL Server 2005 samples. These samples are included with SQL Server 2005 and are also available at the SQL Server Developer Center. For more information, see Installing Samples. You must also have either a mobile device or a mobile device emulator (included with Microsoft Visual Studio 2005) with at least 15 MB of free memory on which to deploy and run the sample.

To initialize the subscription and download sales order data to the device, you must have a SQL Server 2005 Publisher configured to run the Sales Orders Sample for Merge Replication.

Required Permissions

The permissions required to configure and run the Sales Orders sample are based on replication security requirements, and are as follows:

To run InstallSalesOrdersSample.bat at the Publisher, your Windows account must be a member of the sysadmin fixed server role at the Publisher. This batch file configures replication, creates the AdvWorksSalesOrders publication, and generates the initial snapshot.
To initialize the subscription and synchronize data with the Publisher, the Windows account used to connect to the Web server must meet the following requirements:
Have a valid login at the Publisher associated with a user in the publication database.
Have a valid login at the Distributor associated with a user in the distribution database (or the guest user).
Be a member of the publication access list (PAL) for the AdvWorksSalesOrders publication. Note: When you use an anonymous connection to the Web server, the IIS anonymous Windows account is used to connect to the Publisher.
To connect to the Web server using Secure Sockets Layer (SSL) encryption, you must have a copy of the root certificate of the server certificate used to secure the Web server installed as a root certificate on the device. If the Web server is configured to require client certificates, you must also have a valid certificate installed as a personal certificate on the device.

Building and Configuring the Sample

To configure the replication topology and build and deploy the sample project:

At the Publisher, run the publication installation script from the Sales Orders sample.
Build the Sales Orders sample and deploy the business logic handler assembly on the Web server.
Run the Configure Web Synchronization wizard to configure the virtual directory.
Build and deploy the sample to a device or device emulator using Visual Studio 2005.

To configure the Publisher, and build and deploy the sample project

On a computer that is running SQL Server 2005, execute the installation script from the Sales Orders Sample for Merge Replication to create the AdvWorksSalesOrders publication at the Publisher. Note: The Sales Orders sample configuration script configures Web synchronization only for SQL Server 2005 and SQL Server Express Subscribers.
At the command prompt, navigate to the SQL Server 2005 samples installation directory. The default is C:\Program Files\Microsoft SQL Server\90\Samples.
Execute the following at a .NET Framework or Microsoft Visual Studio 2005 command prompt: sn -k SampleKey.snk *Note: You can skip this step if this key was previously created for use with another sample. *
Navigate to the installation location for the Sales Orders sample solution in Microsoft Visual C#. The default is C:\Program Files\Microsoft SQL Server\90\Samples\Replication\Merge\SalesOrders\CS.
Open the SalesOrders.sln solution file in Visual Studio 2005.
Build the project.
Place a copy of the BusinessLogic.dll assembly in the C:\Program Files\Microsoft SQL Server\90\COM directory on the Web server.
Run the Configure Web synchronization Wizard to create a virtual directory name "SalesOrdersMobile." For information about how to run this wizard, follow the steps in the How To: Configure Connectivity with the Configure Web Synchronization Wizard topic in SQL Server Compact Edition Books Online. Note: When client certificates are required to connect to the Web server, you must have a valid personal certificate installed on the device.
If using an anonymous connection to the Web server, create a login at the Publisher for the Windows account used for anonymous access, create a user in the AdventureWorks database for this login, and add this user to the PAL for the AdvWorksSalesOrders publication. For more information, see How to: Manage Logins in the Publication Access List (SQL Server Management Studio).
Navigate to the installation location for the Sales Orders Mobile device sample solution in Microsoft Visual C#. The default is C:\Program Files\Microsoft SQL Server\90\Samples\Replication\Merge\SalesOrdersMobile\CS.
Open the SalesOrdersMobile.sln solution file in Visual Studio 2005.
Connect the device or device emulator and start ActiveSync.
Build and deploy the project to the device.

Running the Sample

To run the Sales Orders Mobile device sample and synchronize data

Cradle the device and ensure that ActiveSync is running.
To secure the connection to the Web server using SSL, export the root certificate of the server certificate used to secure the SalesOrdersMobile virtual directory (in DER encoded binary X.509 format), copy it to the device, and tap to install it as a root certificate on the device. When client certificates are required to connect to the Web server, you must also have a valid personal certificate installed on the device. Security Note: If you use Basic Authentication to connect to the Web server, you should use SSL to encrypt the connection to the Web server. This protects the Windows credentials.
On the device, start Internet Explorer and browse to one of the following URLs:
http://webserver/SalesOrdersMobile/sqlcesa30.dll?diag - when using anonymous access to the Web server.
https://webserver/SalesOrdersMobile/sqlcesa30.dll?diag - when connecting to the Web server using SSL and specifying a Windows login and password to use for Basic Authentication.
On the device or device emulator, start the SalesOrdersMobile program. When run for the first time, the program creates the SQL Server Compact Edition subscription database (\My Documents\AWMobile.sdf).
On the Settings page, enter the name of the Publisher and the URL of the Web server in one of the following formats:
http://webserver/SalesOrdersMobile/sqlcesa30.dll. This URL is used when the Connect anonymously to server box is checked.
https://webserver/SalesOrdersMobile/sqlcesa30.dll. This URL is used when the Connect anonymously to server box is unchecked. You must also specify a Windows login and password in the Windows login and Password fields, where these values are the credentials that correspond to a Windows login at the Publisher and Distributor.
Tap Save to save these settings.
On the Synchronize page, verify the value in the Hostname field, select Full (recommended) for Sync type, and then tap Synchronize. The device connects to the specified Web server to create, initialize, and download subscription data for the application.

To update sales order data and synchronize with the Publisher

With the subscription initialized, on the File menu, tap View Orders, and select a customer from the Customers list.
To update an existing order, tap on an existing order in the Orders table, then do one of the following:
To update an existing item, double-tap an item in the Order Items grid, change the Quantity value for the selected item, and then tap Save.
To add a new item to the order, tap Add New, select the product from the Category and Product lists, set the order quantity in the Quantity field, and then tap Save.
To delete an existing item from an order, select the item in the Order Items grid, and then tap Delete.
Tap Synchronize from the Tools menu, select either Full (recommended) or Upload only from the Sync type list, and then tap Synchronize. © 2007 Microsoft Corporation. All rights reserved.

Updated Wiki: Home

bonniefe — Thu, 07 Aug 2008 08:29:23 GMT

SQL Server Samples Portal Page > SQL Server Replication Product Samples

Replication is a set of technologies for copying and distributing data and database objects from one database to another and then synchronizing between databases to maintain consistency. Using replication, you can distribute data to different locations and to remote or mobile users over local and wide area networks, dial-up connections, wireless connections, and the Internet.

This project contains Replication samples released with Microsoft SQL Server product. Below is the list of these samples. If you are interested in contributing Replication 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
Sales Orders Mobile Replication Sample	SS2005	SS2008
Sales Orders Sample for Merge Replication	SS2005	SS2008
Subscriber Monitor Utility Sample for Merge Replication	SS2005	SS2008

Updated Release: SQL Server 2008 RTM (Aug 06, 2008)

Thu, 07 Aug 2008 04:42:38 GMT

This release contains the SQL Server 2008 RTM product samples for Replication.

Released: SQL Server 2008 RTM (Aug 06, 2008)

Thu, 07 Aug 2008 04:42:38 GMT

This release contains the SQL Server 2008 RTM product samples for Replication.

Source code checked in, #15927

ReedMe — Thu, 07 Aug 2008 00:04:16 GMT

Adding 'Katmai:August 2008 RTM'

Source code checked in, #11622

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

Adding 'Katmai:June 2008 RC0'

Updated Wiki: SS2008!Subscriber Monitor Utility Sample for Merge Replication

bonniefe — Wed, 11 Jun 2008 00:53:18 GMT

Readme_Subscriber Monitor Utility Merge Replication 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 Subscriber Monitor Utility sample is a Windows application that demonstrates how the Subscriber-side monitoring functionality provided by Replication Management Objects (RMO) is used to monitor merge subscriptions at the Subscriber. This sample solution can be built and run standalone at the Subscriber (using SubscriberMonitorUtility.exe). The SubscriberMonitor.dll assembly is also used by the Readme_Sales Orders Merge Replication Sample to display subscription status.

Scenario

Languages

Features

Prerequisites

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

Microsoft SQL Server 2005 or later version, including the following optionally installed components:
SQL Server Database Engine Services (including replication)
Client Tools
AdventureWorks Sample OLTP Database. This sample database is available on the Microsoft SQL Server Samples and Community Projects page on CodePlex.
The SQL Server samples. These samples are available on the Microsoft SQL Server Samples and Community Projects page on CodePlex. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.
.NET Framework SDK 2.0 or Microsoft Visual Studio 2005. You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework Documentation.

Required Permissions

Building and Configuring the Sample

Running the Sample

Comments

Updated Wiki: SS2005!Subscriber Monitor Utility Sample for Merge Replication

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

Subscriber Monitor Utility Sample for Merge Replication

6/10/2008 4:38:07 PM

Updated: 5 December 2005
The Subscriber Monitor Utility sample is a Windows application that demonstrates how the Subscriber-side monitoring functionality provided by Replication Management Objects (RMO) is used to monitor merge subscriptions at the Subscriber. This sample solution can be built and run standalone at the Subscriber (using SubscriberMonitorUtility.exe). The SubscriberMonitor.dll assembly is also used by the Sales Orders Sample for Merge Replication to display subscription status.

Scenario

Languages

Features

Prerequisites

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

Microsoft SQL Server 2005, including the following optionally installed components:
SQL Server Database Services (including replication)
Client Connectivity Components
Programming Models
Development Tools (including SDK)
Samples
.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.

Required Permissions

Building and Configuring the Sample

Running the Sample

To run the sample, you need to navigate to the location of the built executable and run it.
To run the Subscriber Monitor Utility sample at the Subscriber Start SubscriberMonitorUtility.exe from Visual Studio 2005 or from the command prompt. In the Select Subscription to Monitor dialog box, choose an instance of SQL Server from the Local Server Name drop-down box.Select a subscription to monitor from the Available Subscriptions drop-down list box.(Optional) Click the Edit button to change subscription properties.Click Connect. Select a Merge Agent session from the Merge Sessions tree view. (Optional) Click the Refresh button to refresh the session list.

Comments

Change History

Release	History
5 December 2005	Changed content: Updated key creation and deployment information to reflect sample updates.

Updated Wiki: SS2008!Sales Orders Sample for Merge Replication

bonniefe — Wed, 11 Jun 2008 00:51:47 GMT

Readme_Sales Orders Merge Replication 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.
This readme file details how to install and run the Sales Orders sample. This file also details any known issues with the sample.

Scenario

Languages

C#
Transact-SQL

Features

The Sales Orders sample demonstrates the following features of merge replication:

Replication Management Objects (RMO).
Parameterized row filters.
Precomputed partitions.
Client-requested partitioned snapshot.
Article type-based performance optimizations.
SQL Server Compact 3.5 and Express Edition Subscribers.
Automatic identity range management.
Business logic handlers.
Web synchronization (optional). For more information about how these replication features are demonstrated in the sample, see Sales Orders Sample Implementation Details.

Prerequisites

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

SQL Server 2005 or later version, including the following optionally installed components:
SQL Server Database Engine Services (including replication)
Client Tools
AdventureWorks Sample OLTP Database. This sample database is available on the Microsoft SQL Server Samples and Community Projects page on CodePlex.
The SQL Server samples. These samples are available on the Microsoft SQL Server Samples and Community Projects page on CodePlex. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.
.NET Framework SDK 2.0 or Microsoft Visual Studio 2005. You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework Documentation.

Required Permissions

The permissions needed to configure and run the Sales Orders sample are based on replication security requirements, and are as follows:

To run InstallSalesOrdersSample.bat, which configures replication, creates the AdvWorksSalesOrders publication, and generates the initial snapshot, your Windows account must be a member of the sysadmin fixed server role at the Publisher.
The Sales Orders sample does various Database Engine and replication tasks, including creating the AdventureWorksLocal database, creating the local Subscription, and running the Merge Agent to initialize, reinitialize or synchronize the subscription. In order to successfully run the sample executable (SalesOrders.exe) at the Subscriber, your Windows account must have at least CREATE DATABASE permissions at the Subscriber. Note: When the local database and subscription exists, your Windows account must be at least a member of the db_owner fixed database role on the AdventureWorksLocal database at the Subscriber to run the application.
To initialize the subscription and synchronize with the Publisher, the Windows account used to connect to the Publisher (or with the Web server when using Web synchronization) must meet the following requirements:
Have a valid login at the Publisher associated with a user in the publication database.
Have a valid login at the Distributor associated with a user in the distribution database (of the guest user).
Be a member of the publication access list (PAL) for the AdvWorksSalesOrders publication.

Building and Configuring the Sample

To build the sample project and configure the replication topology, you will need to do the following:

At the Publisher, run the replication installation script.
(Optional) Configure the Internet Information Services (IIS) server to support Web synchronization for merge replication. If this is not done, you cannot use the Web synchronization feature of the sample.
At the Subscriber, modify the configuration settings in the app.config file of the sample.
At the Subscriber, build the sample using Visual Studio 2005 or the .NET Framework 2.0 SDK.
At the Subscriber, place a copy of the BusinessLogic.dll assembly in the C:\Program Files\Microsoft SQL Server\100\COM directory. When using Web synchronization, you must also place a copy of BusinessLogic.dll in the C:\Program Files\Microsoft SQL Server\100\COM directory on the Web server.

To configure the Sales Orders sample at the Publisher

Ensure that the AdventureWorks sample database has been installed and the database is attached. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.
Ensure that the SQL Server Database Engine samples have been installed. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.
Ensure that SQL Server Agent is running. You can view the status of and start this service from Object Explorer in SQL Server Management Studio.
Navigate to the installation location for the Sales Order sample scripts. The default is C:\Program Files\Microsoft SQL Server\100\Samples\Replication\Merge\SalesOrders\Scripts.
(Optional) Configure Secure Sockets Layer (SSL) at the Publisher or at the server used for Web synchronization. SSL is required for communication between the IIS server and all Subscribers. To configure SSL, specify a server certificate for the IIS server to use.
Execute InstallSalesOrdersSample.bat and when prompted enter the login (in the case-sensitive format "DOMAIN\login") and password for the Windows account under which the Snapshot Agent job will run. This calls sqlcmd.exe to execute CreateAdvWorksSalesOrdersPublication.sql, which does the following:
Checks that replication has been configured on the local server, and if not configures it as a Publisher with local Distributor using the distribution database.
Drops and re-creates the stored procedures and user-defined functions used for data access at the client.
Drops and re-creates the AdvWorksSalesOrders Publication.
Adds articles to the publication.
Registers the business logic handler at the Distributor.
Starts the Snapshot Agent job to generate the initial snapshot. The batch file can also automatically configure a virtual directory at the Publisher to support Web synchronization. If you choose not configure the virtual directory at the Publisher during installation, or if you plan to use a separate Web server, you must run the Configure Web Synchronization Wizard prior to using the Web synchronization features of the sample.
(Optional) Run the Configure Web Synchronization Wizard to configure an IIS server to support Web synchronization. Skip this step if InstallSalesOrdersSample.bat successfully created the virtual directory or if you will not use Web synchronization. For complete instructions about using this wizard, see How to: Configure IIS for Web Synchronization.
Before continuing, ensure that the Snapshot Agent job for the AdvWorksSalesOrders publication has successfully completed. The status of this job can be viewed using Replication Monitor. For information about using Replication Monitor to view the status of a Snapshot Agent job, see the topic How to: View Information and Perform Tasks for the Agents Associated With a Publication (Replication Monitor) in SQL Server Books Online.

To build and configure the Sales Orders sample at the Subscriber

At the command prompt, navigate to the SQL Server samples installation directory. The default is C:\Program Files\Microsoft SQL Server\100\Samples\.
Execute the following at a .NET Framework or Microsoft Visual Studio 2005 command prompt: sn -k SampleKey.snk *Note: You can skip this step if this key was previously created for use with another sample. *
Navigate to the installation location for the Sales Orders sample solution in Microsoft Visual C#. The default is C:\Program Files\Microsoft SQL Server\100\Samples\Replication\Merge\SalesOrders\CS.
Open the SalesOrders.sln solution file in Visual Studio 2005.
Build the project.
In the project output folder, edit the SalesOrders.exe.config file and change the following:
Replace the value of the Subscriber key with the name of the local server.
Replace the value of the Publisher key with the name of the server configured previously as the Publisher.
(Optional) Replace the value of the WebSynchronizationUrl key when connecting to the Publisher using Web synchronization. This can also be done at run time.
(Optional) Use the SyncWhenConnectedInterval key to set the interval between synchronizations, in seconds, when using the synchronize-when-connected functionality. Note: Replication does not support localhost for server names.
Place a copy of the BusinessLogic.dll assembly in the C:\Program Files\Microsoft SQL Server\100\COM directory.
(Optional) If using Web synchronization, place a copy of the BusinessLogic.dll assembly in the C:\Program Files\Microsoft SQL Server\100\COM directory on the Web server.

Running the Sample

To run the Sales Orders sample and synchronize data

Ensure that remote connections are enabled at the Publisher and at the Subscriber (TCP/IP or Named Pipes) and that the SQL Server Agent service is running.
(Optional) At the Subscriber, test the Web synchronization connection by connecting to the Web server in diagnostic mode following the instructions on "To configure client certificates at the Subscriber" in How to: Configure Web Synchronization for Merge Replication (Replication Transact-SQL Programming). Note: If an HTTP error occurs when using Web synchronization, open Internet Explorer, and from the Tools menu select Internet Options, Connections, and LAN Settings. Ensure that Automatically detect settings is disabled.
Start SalesOrders.exe from Visual Studio 2005 or from the command prompt. When the application runs for the first time, the subscription database and subscription are created and the Merge Agent is started to initialize the subscription.
After the subscription data has been initialized, the Sales Orders form will load, displaying a list of existing orders that belong to salesperson "adventure-works\garrett1".
Using the Sales Orders form, you can make the following changes to sales data:
Edit sales order information.
Add a new item to a sales order.
Delete an item from a sales order.
Change the ordered quantity for an item in a sales order.
Select a synchronization method from the Synchronize menu to synchronize the subscription.
(Optional) Check Synchronize When Connected to automatically synchronize the subscription. Set the synchronization interval for background synchronization using the SyncWhenConnectedInterval key in the app.config file. Note: The Synchronize When Connected feature is not available when running on Microsoft Windows 2000 platforms. For more information, see Sales Orders Sample Implementation Details.

To use advanced synchronization options of the Sales Orders sample

From Advanced in the Synchronize menu, choose one of the following options:
(Optional) Select a reinitialize option to reinitialize the subscription.
(Optional) Select Web Synchronization Options and supply the Internet URL and the Windows Authentication credentials used to access the Web server over a secure HTTPS connection. To use this option, you must have already configured an IIS server for Web synchronization. Note: Upload-only or download-only synchronization is not supported with Web synchronization. When Web synchronization is enabled, the Only Upload Data menu item is disabled.
(Optional) Select Get Subscription Status to view the results the most recent Merge Agent sessions.

Removing the Sample

Use the following procedure to remove the Sales Orders sample.

To delete the subscription only

At the Subscriber, execute the following Transact-SQL script to delete the pull subscription. * {" -- This batch is executed at the Subscriber to remove

At the Publisher, execute the following Transact-SQL script to unregister the pull subscription. * {" -- This batch is executed at the Publisher to remove

To remove the Sales Orders sample

At the Publisher, navigate to the installation location for the Sales Order sample scripts. The default is C:\Program Files\Microsoft SQL Server\100\Samples\Replication\Merge\SalesOrders\Scripts.
Execute the batch file RemoveSalesOrdersSample.bat.
When prompted, type "Y" and press Enter to remove all replication objects at the Publisher, remove all replication objects in the subscription database, and uninstall publishing and distribution at the Publisher. *Important: When using this script, all replication infrastructure will be removed. If you have created other publications that use this Publisher or Distributor, do not execute DropAdvWorksSalesOrdersPublication.sql. Instead, you should remove the AdvWorksSalesOrders publication manually. For more information, see How to: Delete a Publication (SQL Server Management Studio) or How to: Delete a Publication (Replication Transact-SQL Programming) in SQL Server Books Online. *
At the Subscriber on the AdventureWorksLocal database, execute sp_removedbreplication (Transact-SQL).
Change the database context to the master database and execute DROP DATABASE AdventureWorksLocal .

Microsoft SQL Server Product Samples: Replication

Updated Wiki: Home

Closed Issue: Problem with install SampleDB

Updated Wiki: SS2008!Subscriber Monitor Utility Sample for Merge Replication

Readme_Subscriber Monitor Utility Merge Replication Sample

Scenario

Languages

Features

Prerequisites

Required Permissions

Building and Configuring the Sample

Running the Sample

Comments

See Also

Other Resources

Help and Information

Updated Wiki: SS2005!Subscriber Monitor Utility Sample for Merge Replication

Subscriber Monitor Utility Sample for Merge Replication

Scenario

Languages

Features

Prerequisites

Required Permissions

Building and Configuring the Sample

Running the Sample

Comments

Change History

Updated Wiki: SS2008!Sales Orders Sample for Merge Replication

Readme_Sales Orders Merge Replication Sample

Scenario

Languages

Features

Prerequisites

Required Permissions

Building and Configuring the Sample

To configure the Sales Orders sample at the Publisher

To build and configure the Sales Orders sample at the Subscriber

Running the Sample

To run the Sales Orders sample and synchronize data

To use advanced synchronization options of the Sales Orders sample

Removing the Sample

To delete the subscription only

To remove the Sales Orders sample

Comments

See Also

Other Resources

Help and Information

Updated Wiki: SS2005!Sales Orders Sample for Merge Replication

Sales Orders Sample for Merge Replication

Scenario

Languages

Features

Prerequisites

Required Permissions

Building and Configuring the Sample

To configure the Sales Orders sample at the Publisher

To build and configure the Sales Orders sample at the Subscriber

Running the Sample

To run the Sales Orders sample and synchronize data

To use advanced synchronization options of the Sales Orders sample

Removing the Sample

To delete the subscription only

To remove the Sales Orders sample

Comments

Change History

Updated Wiki: SS2008!Sales Orders Mobile Replication Sample

Readme_Sales Orders Mobile Replication Sample

Languages

Prerequisites

Required Permissions

Building and Configuring the Sample

To configure the Publisher, and build and deploy the sample project

Running the Sample

To run the Sales Orders Mobile sample and synchronize data

To update sales order data and synchronize with the Publisher

Updated Wiki: SS2005!Sales Orders Mobile Replication Sample

Sales Orders Sample for Devices

Languages

Prerequisites

Required Permissions