yghaziza (9/23/2013)
@Grasshopper, problem is that client (GUI) has no control over the constraints or values for data as this is read-only GUI. Data is controlled by other means and user can only get the list from dB. And it seems the way to go is either parse the expression when quering constraints, or put those constraints in a separate table and get the values directly.@SSCrazy, the question is how to get those values you have listed in the first select statement: select 'myColumn in (''1D'', ''2D'', ''3D'', ''4D''))'. I'm not sure how to implement your suggestion :unsure:
A pretty simple modification actually:
WITH CheckConstraint ([definition]) AS (
select 'myColumn in (''1D'', ''2D'', ''3D'', ''4D''))'
),
PatternSplit AS
(
SELECT [definition], itemnumber, item, [matched]
FROM CheckConstraint
CROSS APPLY dbo.PatternSplitCM([definition], '['']')
)
SELECT myColumn FROM myTable WHERE myColumn IN
(
SELECT b.Item
FROM PatternSplit a
INNER JOIN PatternSplit b ON a.ItemNumber + 1 = b.ItemNumber
WHERE a.Item='''' AND b.Item LIKE '%[a-zA-Z0-9]%'
);
Assuming that you're referring to me as SSCrazy (handle is actually Dwain.C). 🙂
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