December 5, 2003 at 12:40 pm
Forgive me if this seems like a stupid question.
What does it mean when a document about Yukon states "Using CLR integration, database developers can code their stored procedures, functions, triggers, and user defined types in the .NET language of their choice..."?
Will that be something similar to how I execute queries and stored procedures using VB Scripts in DTS packages? Or does it mean that using VB.NET and C# you won't need any SQL in your stored procedure?
Robert W. Marda
SQL Programmer
bigdough.com
The world’s leading capital markets contact database and software platform.
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems
December 5, 2003 at 1:38 pm
You will be able to code a VB.NET procedure, using .NET constructs inside SQL Server. These are compiled and execute. However, for many query type statements, this won't make sense and you'll still use T-SQL.
An example might be you create a procedure in VB or C# to proper case a string. Then you could call this procedure from TSQL and pass in an argument. This eliminates the XP stuff you might otherwise need to do. I'm not completely sold on this as a good idea, but Oracle allows Java "procedures", so I guess there it helps.
Steve Jones
http://www.sqlservercentral.com/columnists/sjones
The Best of SQL Server Central.com 2002 - http://www.sqlservercentral.com/bestof/
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply