Viewing 15 posts - 51,511 through 51,525 (of 59,091 total)
If nothing has changed on the system, then keep looking in the source file... the problem is there and you've just not seen it yet. My favorite error is...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2008 at 7:51 am
If it's for "point in time", then I'm pretty sure you need FUll Recovery and differential backups multiple times per day. Do 1 full backup a week... differential backups...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2008 at 7:45 am
Balmukund Lakhani (3/26/2008)
Default trace would help you in such cases if you are on SQL 2005. very few knows the power of it.
Heh... don't tease us, now. Would you...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2008 at 7:41 am
I agree with Michael Earl... I've done this many, many times (cofiguration table that looks like a name/value or "EAV" table). I've found that it's very handy. When...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2008 at 7:38 am
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
Viewing 15 posts - 51,511 through 51,525 (of 59,091 total)