bhattpranav (4/9/2015)
That would be a lot of rows to put in an excel and compare or filter on. querying the table directly for duplicates would be so much quicker.It's weird that i am not able to duplicate the issue after the error occurs using the same input parameters
You don't need to put them all in at once. Put them in in chunks of say 10,000 until you've got some duplicates to analyze. Just make sure you sort them first.
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