THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Browse by Tags

All Tags » SQL Server 2008 » C#   (RSS)
  • Performance impact: Try/Catch blocks in SQLCLR – a follow up

    My previous post showed a simple test that appears to suggest that you may experience significant performance degradation if multiple users are calling the same SQLCLR function at the same time and they are all catching a lot of exceptions.   However, it’s not clear whether that behavior is limited to SQLCLR or applies to .NET in general. ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on July 7, 2011
  • Performance impact: too many try/catch blocks may be harmful in SQLCLR

    If you have many try/catch blocks in your .NET code and your code execution actually passes through them, you should expect a performance hit. That’s intuitive and no surprise.   What is surprising is the extent to which you may experience severe performance degradation when multiple users are executing a piece of SQLCLR code (e.g. calling ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on July 6, 2011
  • Let's Encrypt a BLOB

    SQL Server 2008 has an impressive array of encryption features -- cell-level symmetric and asymmetric encryption, key management, EKM, TDE, and more. But they do have some limitations. Symmetric encryption functions, for instance, can only encrypt slightly less than 8,000 bytes of data (the additional information like random IV and ...
    Posted to Michael Coles: Sergeant SQL (Weblog) by Mike C on April 8, 2009
  • SSIS Script Task In SQL Server 2008 Can Use VB Or C#

    Where do I send a thank you letter? Finally we are allowed to use C# in the SQL Server Integration Services Script Task. I always wondered why SQL Server 2005 only uses VB and not C#, you can use C# in the SQLCLR but not in a Script Task. It turns out that SSIS in SQL Server 2005 uses VSA (Visual Studio for Applications) but SQL Server 2008 will ...
    Posted to Denis Gobo (Weblog) by Denis Gobo on July 4, 2007
Privacy Statement