stephen.sarre (5/10/2012)
-- Along the same lines, this is a very simple way of listing invalid data (allowing -_,;@' in the email column)DECLARE @match VARCHAR(30)
SET @match = '%[^a-zA-Z0-9@.,;!-!_!'''']%'
SELECT email
FROM tbl_Staff
WHERE email IS NOT NULL
AND email LIKE @match ESCAPE '!'
ORDER BY email
Yep - that's a bit of a simpler problem.
In my case, I built the CTE to INSERT those bad characters into a temporary table, which I then used to construct a dynamic SQL UPDATE that replaced all the bad characters with ''. The second part ran really, really fast.
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