Viewing 15 posts - 46 through 60 (of 149 total)
It sounds like you've described a non-clustered index that is partitioned separate from the base table. Can you post the definition of the index?
If that is the case...
Wes
(A solid design is always preferable to a creative workaround)
February 14, 2017 at 8:23 am
Wes
(A solid design is always preferable to a creative workaround)
February 14, 2017 at 7:42 am
Wes
(A solid design is always preferable to a creative workaround)
January 26, 2017 at 10:26 am
Wes
(A solid design is always preferable to a creative workaround)
January 26, 2017 at 7:10 am
Wes
(A solid design is always preferable to a creative workaround)
January 12, 2017 at 1:48 pm
A very skinny index can read data faster, because more records fit per page. However, every insert/update/delete will need to be propagated to all of the indexes containing the affected...
Wes
(A solid design is always preferable to a creative workaround)
January 12, 2017 at 1:25 pm
Andrew P - Wednesday, January 11, 2017 4:13 PMhowever, I may have canceled query execution
Do you still have the transaction open?
[code...
Wes
(A solid design is always preferable to a creative workaround)
January 12, 2017 at 1:12 pm
wendy elizabeth - Thursday, January 12, 2017 9:13 AMdate1 (datetime,null) to date2(datetime,null).
WHERE date1 = date2
OR date1 IS NULL AND date2 IS NULL
You...
Wes
(A solid design is always preferable to a creative workaround)
January 12, 2017 at 12:53 pm
There is a distinct difference between converting data and formatting it.
Formatting should nearly always be done at the presentation layer (application or report). This generally allows your presentation...
Wes
(A solid design is always preferable to a creative workaround)
January 12, 2017 at 12:49 pm
Wes
(A solid design is always preferable to a creative workaround)
January 12, 2017 at 12:23 pm
On a side note, the original Op mentioned his TempDb was stored on his SAN. IMO, that is a waste of SAN and Backup resources. We put our tempdb on...
Wes
(A solid design is always preferable to a creative workaround)
January 12, 2017 at 12:18 pm
Wes
(A solid design is always preferable to a creative workaround)
January 12, 2017 at 12:12 pm
Wes
(A solid design is always preferable to a creative workaround)
January 12, 2017 at 12:09 pm
To answer your base question, use the NoLock hint in front of each table that you want it applied to. In my opinion, you add maintenance risk to your...
Wes
(A solid design is always preferable to a creative workaround)
January 6, 2017 at 7:18 am
SQL Server will try to pack a rowgroup as full as possible, to the max of 1,048,576. The deltastore will not be converted to a rowgroup until there are...
Wes
(A solid design is always preferable to a creative workaround)
January 3, 2017 at 12:51 pm
Viewing 15 posts - 46 through 60 (of 149 total)