Viewing 15 posts - 51,526 through 51,540 (of 59,102 total)
Not real sure it'll increase performance because CASE statements in the SELECT list are normally pretty fast... BUT, things like the following...
case when @nPlatformAssets = 0 then...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2008 at 7:33 am
George Heinrich (3/26/2008)
what I really want to know is how can you run a SP with multiple instances without getting a deadlock?
There is... unfortunately, it requires a rewrite of...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2008 at 7:19 am
krishrana17 (3/26/2008)
but can u explain me what is the benefit of timestamp column??
About the only thing it's good for is to let you know that something has changed. Each...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2008 at 6:37 am
I've never had a problem with the backups staying in synch... that's what the "Archive" bit is for. But, yes, I can see where that could cause problems for...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2008 at 5:57 am
Guess I'm still worried :hehe:
Are you generating scripts from the Dev database, every day, to promote to the Production database?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2008 at 5:49 am
Chirag (3/26/2008)
Jeff - we are still in the development phase of the project. What i meant was that daily there are some modifications to the procedures. This does not...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2008 at 5:42 am
Ganesh,
Can you help me out, please? Why don't you care what the SName for a given roll is so long as you return one? Like I said... I'm...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2008 at 5:37 am
I appreciate that very much. I'm thinking that's not quite the same because the OP said they didn't care which row was returned... you would think in the example...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2008 at 5:34 am
I've never understood this type of request... and it's a fairly frequent request. If the SName (in this case) doesn't matter, why bother? Not trying to be a...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2008 at 12:44 am
You'll need to write some dynamic SQL that uses the Information_Schema views... both are in Books Online. This will likely require a loop of some sort... most prefer a...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2008 at 12:30 am
Vivien Xing (3/25/2008)
---> No
And in terms of the transaction log; potentially this will make...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2008 at 12:27 am
I just can't bring myself to believe in any test that uses RBAR as much as that :sick:
And, over a million rows, datatype isn't going to make much...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2008 at 12:01 am
Something less than a million rows at a time in order by the clustered primary key with a 10 second delay between million row updates.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 10:57 pm
I think I will stick with not in and not exists from now on.
Heh... Except on Tuesdays... that's when the "SQL Run Fast" button is automatically recycled to overcome all...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 9:26 pm
ALZDBA (3/25/2008)
Good old BOL did it again, thanks for the rectification.Here's a little test script I've found back from my test (sql7)
Just to demonstrate simple working of it.
Aye... nicely done,...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 9:20 pm
Viewing 15 posts - 51,526 through 51,540 (of 59,102 total)