Viewing 15 posts - 38,476 through 38,490 (of 59,098 total)
Atif Sheikh (5/11/2010)
This code gave out only 253 duplicates on 16 Mln records.
I don't know if this is exactly what you're after, but you could give it a go.
SELECT TOP...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2010 at 7:19 am
john.moreno (5/10/2010)
How does the idea that you can always replace a cursor with something else, fit in with your Connect suggestion, https://connect.microsoft.com/SQLServer/feedback/details/440375?
Maybe it's just me but it seems obvious... it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2010 at 6:53 am
... and aggregate the older data if it's static.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2010 at 6:30 am
sohairzaki (5/10/2010)
Any solution for that
It depends... where does the data come from and why can't it be split up a bit at the source?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2010 at 6:28 am
You bet... thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2010 at 6:25 am
Cory E. (5/11/2010)
Jeff Moden (5/10/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2010 at 6:20 am
kazim.raza (5/10/2010)
Duplicates records need to be there as they'll be going...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2010 at 9:22 pm
You bet, MC... thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2010 at 9:04 pm
First... http://www.sqlservercentral.com/articles/Best+Practices/61537/
Second... http://www.sqlservercentral.com/articles/Crosstab/65048/
I have the patience if you have the data and the willingness to help yourself by learning something new. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2010 at 8:57 pm
First, it would probably run a bit faster if you didn't select so many unused columns from #Hie.
Second, since your latest query isn't actually using OrgEntityType, my suggestion would be...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2010 at 8:47 pm
irobertson (5/10/2010)
You need to pass the results of your query to a variable, then call this using either exec or preferably sp_executesql.
I'm assuming that you'll have more than one...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2010 at 8:37 pm
dbowlin (5/10/2010)
The more tools you have in your toolbelt the better off you will be.
There is such a thing as carrying too many tools on your "toolbelt" and has the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2010 at 8:22 pm
BWAA-HAA!!! They beat us to the punch on the MCJ cert... "Microsoft Certified Joker". 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2010 at 8:11 pm
Lynn Pettis (5/10/2010)
Grant Fritchey (5/10/2010)
GilaMonster (5/10/2010)
You need skilled people, not titles, to get the job done.
Here, here!
I fully agree!
Heh... I don't believe there's a doubt in anyone's mind as to...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2010 at 8:07 pm
As much as I love working with the Tally table, it just doesn't need to be that complicated for this. In fact, the CASE formula in the following could...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2010 at 7:58 pm
Viewing 15 posts - 38,476 through 38,490 (of 59,098 total)