What effect do you think that creating stored procedures in managed code will have on developers? Do you think they should even consider adopting it? Is it even a good idea? Do you think the effort involved in later migrating such applications to a different back-end database is worth the time gained by using this feature? Do you agree with the author that it makes organization easier, or is this just a nightmare waiting to happen? Is this a truly useful feature or is Microsoft simply buffing up its feature set to match Oracle's support for Java stored procedures? Let us know in the .NET Discussion forum on DevX.
Writing Managed Stored Procedures in SQL Server 2005
Are you tired of struggling with T-SQL to encapsulate the logic your applications need to get data into and out of SQL Server? Now you can bypass SQL altogether, and write logic that runs directly within SQL Server in your favorite .NET language.
by Thiru Thangarathinam
June 8, 2004
ith the functionality found in the .NET Framework Base Class Library (BCL), database developers now have access to thousands of pre-built classes and routines which can be easily accessed from stored procedures. The BCL includes classes that provide functionality for improved string functioning, advanced math operations, file access, cryptography, and more. .NET languages such as VB .NET and C# offer object-oriented capabilities such as encapsulation, inheritance and polymorphism.
SQL Server 2005's (formerly code named Yukon) integration with the .NET CLR makes it possible for developers to author stored procedures, triggers, user defined functions, and create other database objects using a managed language such as VB.NET or C#. This excellent feature provides a number of benefits, including increased productivity, significant performance gains, and the ability to leverage the features of .NET Code Access Security to prevent assemblies from performing certain operations. This article takes a look at this new CLR integration feature so you can understand how to create stored procedures in SQL Server using a managed language. You'll also see how to leverage.NET code access security to better control the assembly execution environment. Despite the benefits, it isn't appropriate to use .NET code for every stored procedure you write, so you'll see how to decide when to use T-SQL and when to use a .NET language for creating SQL Server stored procedures.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
ith the functionality found in the .NET Framework Base Class Library (BCL), database developers now have access to thousands of pre-built classes and routines which can be easily accessed from stored procedures. The BCL includes classes that provide functionality for improved string functioning, advanced math operations, file access, cryptography, and more. .NET languages such as VB .NET and C# offer object-oriented capabilities such as encapsulation, inheritance and polymorphism.
