Jeff Moden (12/25/2012)
Jeff Moden (12/18/2012)
@Sachin,I agree that the CLR Regex method should be the fastest although I've not seen any performance testing on it.
The questions I have for you is...
1. Can you use CLR or do you need a 100% T-SQL solution?
2. Is the maximum length of the data <= 8K bytes?
Actually, I have to take that back. CLR would be the fastest method but only if you DON"T use Regex. I've recently seen many performance tests and either some dedicated CLR or some dedicated T-SQL will usually smoke RegEx according to the tests I've seen.
I've got your back Jeff.
Here's one example: http://www.sqlservercentral.com/Forums/Topic1390297-3122-5.aspx
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St