Viewing 15 posts - 21,421 through 21,435 (of 59,072 total)
To be sure, on large tables, it's not just an obsession.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2015 at 4:08 pm
ANn -425914 (2/27/2015)
for indexes, does the order of column matters?
For example I want to create an index of ID, SchoolID, on terms table.
Does the order of...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2015 at 4:03 pm
ScottPletcher (2/27/2015)
Jeff Moden (2/27/2015)
ScottPletcher (2/27/2015)
Jeff Moden (2/27/2015)
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2015 at 3:57 pm
ScottPletcher (2/27/2015)
Jeff Moden (2/27/2015)
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2015 at 3:47 pm
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
Viewing 15 posts - 21,421 through 21,435 (of 59,072 total)