Viewing 15 posts - 21,451 through 21,465 (of 59,098 total)
ScottPletcher (2/27/2015)
Your clustered index key(s) doesn't(don't) have to be unique by itself(themselves); SQL will take care of that if it needs to.
... at possibly quite some cost if the clustered...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2015 at 2:51 pm
Fandy08 (2/27/2015)
So the problem is limited to (deprecated)...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2015 at 2:45 pm
Grant Fritchey (2/27/2015)
Instead, I'd go with a more standard approach:
Heh... why? Portability? 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2015 at 2:41 pm
Yes... at the "tipping point", a table scan will occur instead. More correctly on a clustered table, a clustered index scan will occur. On very large tables, having...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2015 at 12:18 pm
ScottPletcher (2/27/2015)
Eric M Russell (2/27/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2015 at 11:37 am
N_Muller (2/26/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2015 at 8:53 am
Lynn Pettis (2/26/2015)
... Mark one off, 1 day on the calendar to go. 1 day on the calendar to go, 1 day to go, ...
I'm a bit late on my...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2015 at 8:41 am
SQLJay (2/26/2015)
We use an ERP system that is leveraging SQL2008R2 x64 database. Some of the ERP tables are massive holding close to 275 million rows of data.
Our work environment...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2015 at 8:19 am
This would make a great article. You should write it up and submit it to the folks on this site.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2015 at 7:48 am
Sreepathi1987 (2/26/2015)
because there are other conditions and need to append with that...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2015 at 5:16 pm
Lowell (2/26/2015)
just stick the top results of your recursive query in a temp table...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2015 at 5:15 pm
elee1969 (2/26/2015)
Is using Ragged Right adding another column?
What's preventing you from trying it to see?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2015 at 5:09 pm
There's no question here. The third select on the original post shows the set-based replacement for the cursors. The title truly reflects what was posted... it's an example....
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2015 at 5:03 pm
Moin Ul Haque (2/26/2015)
Jeff Moden (2/25/2015)
Moin Ul Haque (2/25/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2015 at 5:00 pm
Steve Thompson-454462 (2/26/2015)
Jeff Moden (2/24/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2015 at 3:46 pm
Viewing 15 posts - 21,451 through 21,465 (of 59,098 total)