Viewing 15 posts - 50,761 through 50,775 (of 59,098 total)
GilaMonster (5/5/2008)
Here's something:
Thanks, Gail... That's one of the ones I was trying to find... I can't find the other one that explains the "why"...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 5, 2008 at 8:08 am
Maybe I've not had enough coffee... or maybe just too much scotch.
How do you check the production execution plan without getting QA involved, Barry?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2008 at 11:30 pm
john pan (5/4/2008)
what do you mean by recompiling for each row updated?
Are you saying that the query plan is being re-evaluated for each time a row...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2008 at 11:28 pm
Do you have the original file? SOmeone obviously tried to change the first one... even a computer couldn't screw things up that badly... takes a human beinging to mess...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2008 at 11:25 pm
Thank you for the feedback... but we'd all be interestd in what you actually meant...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2008 at 10:12 pm
Though shalt not double post... go to your other post and answer the questions that I asked.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2008 at 9:53 pm
And, why do you think this is very very "urgent"?... It's been 9 hours since you've posted and 7 hours since the first response... yet, you've not replied to that...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2008 at 9:50 pm
No.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2008 at 9:47 pm
It's not uncommon for a proc to look like it's blocking itself... if a proc is taking way to long to run, it's not usually because it's blocking itself... it...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2008 at 9:46 pm
Post the name of the supposedly non existant index, please.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2008 at 9:43 pm
In short... no. There's no command available to get a backup file to identify the database(s) that have been backed up in the file.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2008 at 9:36 pm
Sure... when you're using QA, you may run the same thing more than once. Data is cached and everything looks rosy because of it.
If you really want...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2008 at 9:35 pm
Gosh, I sure hope so, Lester. Thank you for the confidence. I look at some of the articles I've written and say to myself, "Everyone probably knows that...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2008 at 9:29 pm
susheereddy (5/4/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2008 at 9:23 pm
jeff.williams3188 (5/4/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2008 at 9:19 pm
Viewing 15 posts - 50,761 through 50,775 (of 59,098 total)