Viewing 15 posts - 16 through 30 (of 208 total)
That does work logically, but it's horrible to index for, especially in more complex queries.
IF @arg1 IS NULL
select * from mytable
ELSE
select * from mytable
...
August 4, 2011 at 12:29 pm
I'm totally with stolbovoy on this one. It depends on your environment, for sure, but we force LOTS of optimiser hints here. We run huge databases (terabytes), multi-on-line-users...
August 4, 2011 at 8:34 am
Alternatively, if that configuration is working for you, take advantage of that fact and plan a more scalable one now whilst you still have the luxury, rather than in...
August 4, 2011 at 2:44 am
I'm still not quite sure where your problem lies.
How many Publications do you have? I know you have 3 publishers, but do they reference one publication each...
August 3, 2011 at 9:14 am
Why do you want to separate each publication so distinctly? I wouldn't even have separate distribution databases per publication, let alone separate instances! We do have multiple distribution...
August 3, 2011 at 8:14 am
Doh - wrong way round! Not thinking straight today ...:crazy:
July 29, 2011 at 5:54 pm
The most likely culprit is the SET ARITHABORT option.
By default in SSMS, this is OFF. Most applications will run with ARITHABORT ON. You will see very...
July 29, 2011 at 5:27 am
Brandie Tarvin (7/20/2011)
This code will most likely NOT use the index because the index only works if your WHERE clause has Col3 listed and if it references Col3 first. So
It's...
July 21, 2011 at 7:45 am
Not sure if this is still relevent any more, but since no one else has posted ...
I've read about situations like this before. Deletes of large numbers of rows...
June 1, 2011 at 11:32 am
Hmmm. Someone else a tad slow on the uptake maybe ...? 😀
May 31, 2011 at 7:38 pm
OK, it's bending my head trying to actually work out which parameter is responsible (given the length of the strings being manipulated!), but essentially one or both of your Start...
May 31, 2011 at 1:58 pm
Yes, but he's selecting over 100 columns, so I don't really think a covered index is an option here ...
Also, if he's retrieving a few days worth of records about...
May 31, 2011 at 1:12 pm
No problem. Just to recap - whatever you use as your clustered key, make sure that the data will be added to the table in the clustered key order....
May 27, 2011 at 8:15 am
As a general rule, NC indexes are poor at seeking on potentially large numbers of rows (unless they account for a very low percentage of the overall table). I'd...
May 27, 2011 at 6:21 am
Viewing 15 posts - 16 through 30 (of 208 total)