Updated: 5 December 2005
The XmlSurvey sample application collects information for a store survey and updates the SQL Server
database with the results. Stores in the database represent resellers. The survey is stored as XML in the
column of the Sales.Store
To keep the application simple, the record with a Customer ID of 1 is updated to contain the specified XML each time a survey is saved.
|CustomerID is the primary key in the Sales.Store table and a foreign key in the
This sample is not supported on Windows 2000 and earlier operating systems.
The default installation directory is drive
:\Program Files\Microsoft SQL Server\90\Samples\Engine\XML\XmlSurvey.
A developer wants to create an application that updates store demographics information by sending an XML document to a Web service hosted by SQL Server.
Transact-SQL, XML, XSD, Visual C#, and Visual Basic.
The XmlSurvey sample uses the following features of SQL Server 2005.
||XML, SQL Server-hosted Web services
Before running this sample, make sure SQL Server 2005 is installed, including the following components:
- SQL Server Database Engine
- SQL Server Management Studio
- The AdventureWorks database which is included with SQL Server 2005, and is also available at the SQL Server Developer
- The SQL Server 2005 Database Engine samples. These samples are included with SQL Server 2005. You can download the latest version of the samples at the SQL Server Developer
- .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.
Building the Sample
If you have not already created a strong name key file, generate the key file using the following instructions.
To generate a strong name key file
- Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to
All Programs, point to Microsoft .NET Framework SDK 2.0, and then click
SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click
Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click
SDK Command Prompt.
- Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed.
Note: To determine the folder where samples are located, click the Start* button, point to
All Programs, point to Microsoft SQL Server 2005, point to Documentation and Tutorials, and then click
Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\90\Samples.*
- At the command prompt, run the following command to generate the key file:
sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.
To build the sample, do the following:
Build the sample
- Ensure that the AdventureWorks sample database is installed.
- In SQL Server Management Studio, load and run the Scripts\InstallCS.sql script to create the following :
- SaveStoreSurvey stored procedure
- sql_StoreSurvey HTTP Endpoint
- Build the sample by using the solution provided and Visual Studio, or run the following at a .NET Framework or Microsoft Visual Studio 2005 command prompt:
msbuild /nologo /verbosity:quiet /property:Configuration=Debug CS\XmlSurvey.sln
Running the Sample
To run the sample, do the following:
Run the sample
- Run CS\XmlSurvey\bin\debug\XmlSurvey.exe.
- Fill in the survey.
- Save the survey by clicking Save on the File menu.
- Verify that the Sales.Store table has been updated by run a query similar to the following, and then selecting the data in the
Demographics column in the results pane: SELECT * FROM Sales.Store WHERE CustomerID = 1
Removing the Sample
To remove the sample, do the following:
Remove the sample
- Open the Scripts\Cleanup.sql file by using Management Studio and execute the contents of the file.
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.
|5 December 2005
||Changed content: Changed instructions for generating a key file, including the name and location of the key file.
© 2007 Microsoft Corporation. All rights reserved.