July 5, 2012 at 1:54 am
Without a better idea of what such "futuristic" errors may be, I'm not sure I can help you.
I will point out that data cleansing should be addressed by the front end so that you don't have to keep adapting your SQL to take care of captured garbage.
What's important is that you have a solution you're happy with.
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
July 5, 2012 at 2:05 am
Dear Dwain,
I had apply distinct clause previously but same is giving multiple row as mention earlier.
Actually I have large data (in thousands) so I can't analyze all data one by one.
So I find my solution very easy and systematic step by step. So that is not hard to understand to any one.
Yes you are right Solution is important, no matter from which way its comes.
Vijay
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply