Steve Muise - SQL Server stuff

From the CLR to Analysis Services - SQL 2005 is a whole new beast. I will be discussing my findings, learnings, experiences, and personal opinions on the new new SQL Platform. I will also be posting follow-up conversations, code samples, question discussions from the MSDN SQL Programmability webcasts I am doing on Fridays. Come join us on Friday http://www.microsoft.com/events/series/msdnsqlserver2005.mspx

This Blog

About
Email

Search

Navigation

Home
Blogs

MSDN Webcast - SQL 2005

Event descriptions

Syndication

Data Provider from within SQL Server's hosted CLR

Today we discussed the advantages to using the Context Connection = "true" when connecting to SQL from a cataloged assembly.

Here is the demo code.

http://www.neudesic.com/uploads/Steve_Muise/03_SqlServer_Provider.zip

Sorry about the short post, but I have a few things I need to get up here, so check back soon.

Steve

Published Friday, February 17, 2006 12:33 PM by Steve_Muise

Comments

# re: Data Provider from within SQL Server's hosted CLR @ Sunday, February 19, 2006 2:15 AM

Hi Steve,

Great Session 3!!! The first two sessions were a little bit rushed.

In PubsProcs.cs should
public static SqlInt32 getAuthorWithErrors(SqlString au_id, out SqlString au_info)
{
and
return 0 at its end not be:

[SqlProcedure]
public static void getAuthorWithErrors(SqlString au_id, out SqlString au_info)
{
and
and without any return value. In the SQL script you defined it as a procedure. With the changes it returned the same results?

Al
read
[SqlProcedure]
public static void getAuthorWithErrors(SqlString au_id, out SqlString au_info)
{

ACB

# re: Data Provider from within SQL Server's hosted CLR @ Friday, March 17, 2006 12:07 PM

You are correct, the return type is extraneous. Since there is an OUT param, there is no need to set a return type. Sorry for the mistake - good catch though

Steve_Muise

Anonymous comments are disabled

Powered by Community Server, by Telligent Systems