Web Seminar – Tomorrow
Five things every SQL Server DBA needs to know when managing multiple database platforms, that will be the subject of tomorrow’s web seminar.
While some DBAs work exclusively on SQL Server, you may have to support two or more types of database platforms today, and certainly multiple types of databases throughout the course of your career. During this very different, interview-style show with real world examples, we’ll discuss the five things every SQL Server DBA needs to know when managing multiple database platforms.
Sign up for this web seminar if you’re interested in learning how your SQL Server skills can be easily extended to additional database platforms such as Oracle, DB2, MySQL, or Sybase.
Experiences withthe CLR – Continued
This is a continued conversation about the CLR – where it fits, where it doesn’t. Have feedback? Send it in! Just drop me an email here.
Darin had this to say about CLR-based work – "We have some file system procedures and functions:
FileDelete, FileExists, FileSize, DirectorySize, FileCopy, FileMove, DirectoryCreate, DirectoryList
These are low overhead (moreover, they might get called a couple of dozen times a day) and more convenient than working with xp_cmdshell and parsing out "dir" listings. Plus, IIRC, they impersonate the calling principle so people can only see what they should and they have auditing built into them so call to the proc is logged to a table. They are in a restricted-access, sysadmin-only database, so we can have more fine grained control than we used to have when we had to rely on xp_cmdshell and it was the Wild West.
They have been running for a couple of years and I don’t think about them much.
From what I’ve read, people usually get into trouble when they start writing large, complicated things that eat up a lot of memory.
One request I had two or three years back was to run packages from within stored procedures, synchronously. IIRC, you can’t even load up the .Net libraries that will do that inside of the SQLCLR."
Sibi wrote – "We have written few CLR to do some specific thing such as
1. Call a web service from a T-sql stored procedure
2. Receive and send message to a MSSMQ queue from a T-Sql stored procedure
3. Writing one to get group membership for AD group
These are the thing we could not do from T-SQL, so we write a common CLR which people can use it directly from T-SQL proc instead o f writing SSIS package
We may write more as and when we find things which are not possible in T-SQL. We would like almost everything to be written in T-SQL . It is easy to maintain and upgrade."
Featured Script
CheckNewDBStructure
Many times I get from my boss a database that was build by a software vendor, and I have to give him my opinion about the da… (read more)