Viewing 15 posts - 50,221 through 50,235 (of 59,099 total)
Thanks for the links and info, Tom... I'll take a look.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 31, 2008 at 4:06 pm
You certainly don't need any prefixes to make them run. So far as not being able to tell what the views are used for, that's thanks to the lack...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 31, 2008 at 10:36 am
Ok... I'm just going to go ahead and guess you meant "shrinking" TempDB... 😉
Yes... you may shrink the "files" associated with TempDB as you would any other database. It...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 31, 2008 at 10:28 am
Yes... here's the syntax from Books Online (comes free with SQL Server)...
SET IDENTITY_INSERT [ database. [ owner. ] ] { table } { ON | OFF }
... but, generally, there's...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 31, 2008 at 10:18 am
adshisode85 (5/30/2008)
1 6
2 7
3 ...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 31, 2008 at 10:09 am
Howdy folks,
Someone who wishes to remain anonymous, send me an email asking the following questions related to this article. I've not worked with SQL Server 2008 (shoot, I'm just...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2008 at 10:43 pm
I don't believe anything is missing... just alter the column like I did... don't mess with the constraint or the default.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2008 at 9:28 pm
karthikeyan (5/30/2008)
1) what is the best size of TempDB ? The answer may be 'it depends',But if anybody added some valid points then...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2008 at 7:45 pm
Matt Miller (5/30/2008)
bcronce (5/30/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2008 at 7:12 pm
Look at the code, guys... column was previously defined as NOT NULL.
Dunno if it'll work because no one provided the code for the rest of the table, but...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2008 at 6:46 pm
I'd say to never look at the percentage of batch in the execution plan... it lies... a lot...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2008 at 6:32 pm
First, I think I'd use UNION ALL... considering the source tables, there's probably not much chance of duplication, anyway.
The other thing is that the CPU time is not varying all...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2008 at 6:29 pm
Tomm,
Your code won't work on SQL Server 2000 (this forum is a 2k forum)... keyword PERSISTED does not exist and the calculated column is considered "non-deterministic" in 2k so the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2008 at 6:02 pm
Heh... regular doses of a good Scotch and soda fixed mine... 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2008 at 5:27 pm
jmapledoram (5/30/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2008 at 5:17 pm
Viewing 15 posts - 50,221 through 50,235 (of 59,099 total)