SQL # |
Expanding the capabilities of T-SQL |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Home
Features
Benefits
F.A.Q.
Contact Us
Full Version Free Version Documentation |
❗❗ Version 4.0 Announcement ❗❗ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
SQL CLR Library , SQLCLR , CLR Routines , CLR Library , SQL Server CLR , Bulk Export , Regular Expressions , HTML Export , Generate Insert Statements , Median , Automation , RegEx
⸦ Features ⸧
** "4k" versions: Quite a few of the String and RegEx functions that have NVARCHAR(MAX) input parameters, and/or output parameters, and/or return types have a second T-SQL wrapper object, pointing to the same .NET method, but that does not use any MAX type, instead using NVARCHAR(4000). The problem with NVARCHAR(MAX) is that if there is even one of them in the object's signature, then there is a noticable performance hit. If the function you are using has a "4k" version and the parameters, return type, or result set fields are guaranteed to never hold more than 4000 characters (or more accurately: 8000 bytes worth of characters since Supplementary Characters are 4 bytes each), then use the "4k" version as it will perform better. What can SQL# do?
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Copyright © 2006-2024 Sql Quantum Lift, LLC. All rights reserved. |