From: Erland Sommarskog on 23 Mar 2010 18:53 RG (nobody(a)nowhere.com) writes: > What would the downside in using sqlclr? One more of type of object to manage. Using the CLR in the wrong place invites to misuse. Gert-Jan makes the very good point that the DBA may not know it well. Deploying CLR code takes a few more steps. If you access tables direct from the CLR code, ownership-chaining does not apply, and thus users needs direct permissions on the tables. Correctly used, the CLR can be a good addition in your toolbelt, so it is definitely a good idea to learn to master it. -- Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
From: Uri Dimant on 24 Mar 2010 06:02 RG Incorrectly using CLR might lead your memory hit performance. Permissins as Erland has alredy pointed out. I would say also deploying CLR for whom that has limited experience is not an easy task "RG" <RG(a)discussions.microsoft.com> wrote in message news:B6179581-D155-491E-B5CC-5041E3C35075(a)microsoft.com... > what is the downside of using sqlcr? > > "Erland Sommarskog" wrote: > >> RG (RG(a)discussions.microsoft.com) writes: >> > Performancewise, is there a difference between your cursor loop/update >> > stored procedure and c# program, residing where sql server is, that >> > does >> > the same? >> >> Not sure exactly what you have in mind, but I suppose the answer is >> "it depends". >> >> Even if the C# program run on the SQL Server machine, there may be a lot >> of data that will be passed between different processing. On the other >> hand, if there is complex processing done to each row, this is likely to >> run faster in C#. >> >> Yet an alternative is to do the processing in a stored procedure written >> in C#. That is the same thing as the application, but inside SQL Server. >> Again, whther this is a good idea or not, depends. >> >> >> -- >> Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se >> >> Links for SQL Server Books Online: >> SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx >> SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx >> SQL 2000: >> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx >> >> . >>
First
|
Prev
|
Pages: 1 2 3 Prev: Function or insert/into temp table Next: what is the boot record of the database file? & TDE |