June 20, 2009 at 11:06 am
There are some samples and tutorials on MSDN:
http://msdn.microsoft.com/en-us/library/ms160894.aspx
Some of the business cases they show are much better done in T-SQL but it shows how it works and explains the syntax.
June 22, 2009 at 8:02 am
A good book to get you started would be:
http://www.amazon.com/Pro-SQL-Server-2005-Assemblies/dp/1590595661
However, after 2+ years working with SQLCLR, I'll tell you that appropriate use cases for it are pretty uncommon unless you offload a large portion of your application processing onto your database server. Most often times, middle tier services in a N-tier architecture are better performance wise for doing processing, and they are much more scalable. That is not to say that there are not appropriate places to make use of SQLCLR, but it isn't a replacement for TSQL which is what I see lots of people trying to do.
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
June 22, 2009 at 8:42 pm
Thanks. I was wanting to see if I could replace a lot of processing that goes on in a lot of MS Access databases that run at night by way of a scheduling software. These access databases run various updates and transactions into tables at night and on weekends.
Just looking to see if this could provide me an alternative by transferring the vba in access to a clr stored procedure and and running those sprocs by the sql agent.
Lonnie Johnson
May God Bless You Beyond Your Imagination
Prodev
June 23, 2009 at 3:22 am
Lonnie Johnson (6/22/2009)
These access databases run various updates and transactions into tables at night and on weekends.
Data updates are in most cases wrong stored in CLR modules. You should move those code to T-SQL procedures instead of CLR.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply