[AccessD] SQL Server 2005 Cool stuff

John Colby jwcolby at ColbyConsulting.com
Wed Dec 28 13:19:25 CST 2005


I just found this:

.NET Integration and What It Does for You
The most evident change in Yukon is a far greater integration with the .NET
Framework. The current versions of SQL Server 2000 are accessible via
CLR-hosted assemblies, but the DBMS engine itself is not integrated with
.NET. As a result, multi-tiered deployment involves bridging technologies
like ADO.NET, and database coding is constrained to Microsoft's own SQL
dialect, Transact-SQL (aka T-SQL). In contrast, Yukon will host a CLR
directly in the DBMS engine, meaning that code written in C#, VB.NET, and
other .NET languages can be executed by SQL Server. (This is in addition to
Transact-SQL.)

Given the greater expressiveness of C# and VB.NET, this feature will greatly
facilitate coding, and it will remove the requirement that programmers learn
advanced features of SQL to perform straightforward tasks. In fact, should
they wish to, developers can code stored procedures, triggers, and
user-defined functions (UDFs) entirely in .NET languages. Microsoft uses the
System.Data.SqlServer namespace to provide this .NET access to SQL Server.
(Readers who are members of Microsoft's MSDN network can download beta
versions of Yukon and the needed .NET files from the MSDN website to begin
testing this functionality.) 

In this:

http://www.devx.com/SummitDays/Article/22469

John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/




More information about the AccessD mailing list