Jeff Papiez - SQL Server Test Developer : SQL Server 2005

Passing a DataSet to a SQLCLR Stored Procedure

jpapiez — Mon, 26 Sep 2005 21:15:33 GMT

Is it possible to pass a DataSet to SQL and process the data in a SQLCLR stored procedure? This is the question I set out to answer.

The .NET Framework 2.0 adds some features to the DataSet that make this scenario possible (WriteXml, ReadXml). I created a sample that proves this concept.

First we need the CLR stored proc to handle the passed in dataset. Start by creating a new "SQL Server Project" in Visual Studio 2005. This example uses the Northwind database installed with SQLExpress.

using System;

using System.Data;

using System.Data.SqlClient;

using System.Data.SqlTypes;

using Microsoft.SqlServer.Server;

using System.IO;

using System.Xml.Serialization;

using System.Text;

public partialclassStoredProcedures

{

[Microsoft.SqlServer.Server.SqlProcedure]

publicstaticvoid uspProcessCustomers(string customerData)

{

// Need to convert the inbound string to a byte array

UTF8Encoding encoding = newUTF8Encoding();

DataSet ds = newDataSet();

// Convert the string to a byte array, then load into a MemoryStream

using (MemoryStream ms = newMemoryStream(encoding.GetBytes(customerData)))

{

// Populate the DataSet from the MemoryStream

ds.ReadXml(ms);

}

// Iterate through the dataset and process each record.

foreach (DataRow dr in ds.Tables["customers"].Rows)

{

if (dr.RowState != DataRowState.Unchanged &&

dr.RowState != DataRowState.Detached)

{

string procName = string.Empty;

// Instantiate a SqlCommand object to perform the

// required DB operation

using (SqlCommand cmd = newSqlCommand())

{

cmd.CommandType = CommandType.StoredProcedure;

// determine which procedure to execute

// based on the state of the row

switch (dr.RowState)

{

caseDataRowState.Added:

caseDataRowState.Modified:

if (dr.RowState == DataRowState.Added)

{

procName = "uspInsCustomer";

}

else

{

procName = "uspUpdCustomer";

}

// Populate the Parameters collection

cmd.Parameters.Add(

newSqlParameter("@customerID", dr["CustomerID"].ToString()));

cmd.Parameters.Add(

newSqlParameter("@companyName", dr["CompanyName"].ToString()));

cmd.Parameters.Add(

newSqlParameter("@contactName", dr["ContactName"].ToString()));

cmd.Parameters.Add(

newSqlParameter("@contactTitle", dr["ContactTitle"].ToString()));

cmd.Parameters.Add(

newSqlParameter("@address", dr["Address"].ToString()));

cmd.Parameters.Add(

newSqlParameter("@city", dr["City"].ToString()));

cmd.Parameters.Add(

newSqlParameter("@region", dr["Region"].ToString()));

cmd.Parameters.Add(

newSqlParameter("@postalCode", dr["PostalCode"].ToString()));

cmd.Parameters.Add(

newSqlParameter("@country", dr["Country"].ToString()));

cmd.Parameters.Add(

newSqlParameter("@phone", dr["Phone"].ToString()));

cmd.Parameters.Add(

newSqlParameter("@fax", dr["Fax"].ToString()));

break;

caseDataRowState.Deleted:

procName = "uspDelCustomer";

// Populate the Parameters collection

cmd.Parameters.Add(

newSqlParameter("@customerID", dr["CustomerID"].ToString()));

break;

}

using (SqlConnection cxn = newSqlConnection("context connection=true"))

{

cmd.Connection = cxn;

cmd.CommandText = procName;

cmd.Connection.Open();

cmd.ExecuteNonQuery();

cmd.Connection.Close();

}

If you use Visual Studio to deploy the stored procedure to the database you'll need to drop and recreate the procedure. This is because the procedure gets created with the customerData parameter as NVarChar(4000). In order to accept even a minimal DataSet (in my test I populated the DS with 10 records), 4000 chars isn't going to be large enough. To get around this you can use the new variable text types in SQL Server 2005, in this case NVarChar(max):

CREATE PROCEDURE uspProcessCustomers

@CustomerData AS NVarChar(max)

EXTERNAL NAME SQLData.StoredProcedures.uspProcessCustomers

The procedures for inserting/updating/deleting aren't that interesting, so I'll leave those to your imagination. Now we need a client app that consumes this stored procedure. Start by creating a new Windows Forms client. Add to the client a button, then add the following to the button click event handler:

privatevoid button1_Click(object sender, EventArgs e)

{

this.Cursor = Cursors.WaitCursor;

this.button1.Enabled = false;

// Create the dataset

DataSet ds = newDataSet();

// Create the data table

DataTable dt = newDataTable("Customers");

ds.Tables.Add(dt);

// Create the table schema

DataColumn dc = dt.Columns.Add("CustomerID", typeof(string));

// the first column is the primary key

dc.AllowDBNull = false;

dc.Unique = true;

dt.Columns.Add("CompanyName", typeof(string));

dt.Columns.Add("ContactName", typeof(string));

dt.Columns.Add("ContactTitle", typeof(string));

dt.Columns.Add("Address", typeof(string));

dt.Columns.Add("City", typeof(string));

dt.Columns.Add("Region", typeof(string));

dt.Columns.Add("PostalCode", typeof(string));

dt.Columns.Add("Country", typeof(string));

dt.Columns.Add("Phone", typeof(string));

dt.Columns.Add("Fax", typeof(string));

// Add a few records to the data table.

for (int i = 1; i <= 10; i++)

{

// create a new row

DataRow dr = dt.NewRow();

// populate the fields

dr[0] = "C" + i.ToString();

dr[1] = "Company Name " + i.ToString();

dr[2] = "Contact Name " + i.ToString();

dr[3] = "Contact Title " + i.ToString();

dr[4] = "Address " + i.ToString();

dr[5] = "City " + i.ToString();

dr[6] = "Region " + i.ToString();

dr[7] = "POSTL " + i.ToString();

dr[8] = "Country " + i.ToString();

dr[9] = "Phone " + i.ToString();

dr[10] = "FAX " + i.ToString();

// add the row to the table

dt.Rows.Add(dr);

}

string strConnection = "Data Source=.\\sqlexpress;" +

"Initial Catalog=Northwind;Integrated Security=True";

// Now, connect to the database and pass the dataset

using (SqlConnection cxn = newSqlConnection(strConnection))

{

SqlCommand cmd = newSqlCommand("uspProcessCustomers", cxn);

cmd.CommandTimeout = 1800;

cmd.CommandType = CommandType.StoredProcedure;

// SqlParameter to hold the dataset

SqlParameter param1 = newSqlParameter("@customerData", SqlDbType.NVarChar);

// Create a temporary MemoryStream to hold the output

// of the WriteXml method of the DataSet

using (MemoryStream memoryStream = newMemoryStream())

{

ds.WriteXml(memoryStream);

UTF8Encoding encoding = newUTF8Encoding();

param1.Value = encoding.GetString(memoryStream.ToArray());

}

// Add the SqlParameter to the Parameters collection

cmd.Parameters.Add(param1);

// Open the connection to the database

cmd.Connection.Open();

// Execute the query

cmd.ExecuteNonQuery();

// Finally, close the connection

cmd.Connection.Close();

}

this.button1.Enabled = true;

this.Cursor = Cursors.Arrow;

}

That's all it takes. I welcome your comments and suggestions on this post.

SQL Server 2005 and SQL Server Express 2005 on The Same Machine

jpapiez — Wed, 08 Jun 2005 00:20:00 GMT

Installing both SQL Server 2005 (SQL) and SQL Server Express 2005 (Express) on the same machine can present a problem that might not be easily identifiable.

You can install both of these products on the same machine, though you must take care when choosing which options get installed. If you install the Management Tools for Express you will be unable to install the Management Tool for SQL.

So, if you have Express installed then want to install SQL, make sure you do not have Management Tools for Express already installed, otherwise none of the tools will be installed for SQL, and you'll be left with the likes of sqlcmd.exe for managing SQL untill the Express tools are uninstalled.

Re-installing WMI

jpapiez — Thu, 09 Dec 2004 21:24:00 GMT

For those folks out there using Windows Server 2003 SP1 Build 1277 along with the SQL Server 2005 December CTP, you may be unable to install SQL Server 2005 with the following error:


Microsoft SQL Server 2005 Beta 3 Setup

The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine SI4P64LF3-05 Error:2147749907 (0x80041013).

The cause of this error is a corrupt install of WMI, caused by upgrading Windows Server 2003 to SP1 build 1277. To fix this issue, copy the following into notepad and save it with either a .cmd or .bat extension. Then run the script to re-install WMI:


%SYSTEMDRIVE%
CD %windir%\system32\wbem
Mofcomp.exe cimwin32.mof
Regsvr32 /s wbemupgd.dll
Regsvr32 /s wbemsvc.dll
wmiprvse /regserver 
 
If that doesn't work, try the info here posted on msdn:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/reinstalling_wmi.asp

HowTo: Debug a Managed Stored Procedure with Visual Studio 2005 and SQL Server 2005

jpapiez — Fri, 23 Jul 2004 20:06:00 GMT

In response to a newsgroup post, I wrote this quick little tutorial.

This tutorial assumes you have the AdventureWorks database installed, but any database will do.

1. Create SQL Server Project in Visual Studio

2. Add a connection to AdventureWorks database when prompted for a connection.

3. Add a new item to the project, new Stored Procedure, name: uspHellowWorld.cs

4. add the following code to uspHelloWorld():

SqlContext.GetPipe().Send("Hello World");

5. Deploy the project (right click on the product, select Deploy)

6. In the Server Explorer window, right click on the Data Connection to the AdventureWorks database, select "Allow SQL/CLR Debugging". CLick YES to the message that says "SQL/CLR debugging will cause all managed threads on the server to be stopped. Do you want to continue?"

7. Set a break point on the code created in step 4.

8. Press F5 to start debugging. You should see that your project will get re-deployed, then vs debugging will startup and your breakpoint should be hit.

This is about as simple as it gets.

How do we Integrate?

jpapiez — Wed, 21 Jul 2004 20:56:00 GMT

Some background is probably in order. I'm a Software Tester here at Microsoft. I work in the Integration Test Team, Release Release Services, SQL Server. One of my new jobs is to look at how our products integrate. Currently I'm investigating SQL Server and Visual Studio 2005.

My question to you is this:

If you've had the chance to try out Visual Studio 2005 Beta 1 (or earlier versions), what has been your experience with it's integration with SQL Server? What works well? What doesn't? What can we do to improve the integration between our two products?

If you haven't yet tried Visual Studio 2005 or SQL Server 2005, no worries. I'll take your comments on previous versions of Visual Studio .NET and SQL Server.

If you are up to it send feedback to this post, or reply to me directly: jpapiez@microsoft.com (no spam please :)