Viewing 9 posts - 16 through 24 (of 24 total)
I was actually incorrect. There is a SP3 CU1 for those that want the SP2 CU10 and CU11 fixes.
What you are seeing sounds more like the install may have failed...
January 6, 2009 at 8:02 am
It sounds like you might have a cardinality error. If you are using an @temp table try changing it to a #temp table. If that does not help try adding...
January 2, 2009 at 4:35 pm
It sounds like you may have installed cumulative update 10 or higher before applying the service pack. There was a bit in the release notes about having to apply the...
January 2, 2009 at 3:52 pm
Yes, freeing the proccache will bring back the free space in tempdb temporarily. It will not shrink the file for you, but constantly growing and shrinking the file could result...
January 2, 2009 at 9:36 am
I should have added that while freeing the proc cache will clear the symptoms you are seeing temporarily the root cause is likely proc cache bloat. If all the temp...
January 2, 2009 at 9:12 am
You can also try a DBCC FREEPROCCACHE to blow out all the work tables, cached temp tables etc.
January 2, 2009 at 8:44 am
The dmv's do not exist in SQL 2000 so there is not a real quick way that I have run across. Your best bet is to use profiler, removing databases...
January 2, 2009 at 8:36 am
The script below should do the trick, but watch out for reindex jobs etc as they may show as user activity. I would still recommend setting up a server side...
January 1, 2009 at 10:31 pm
Another way to go on this one is to setup a server alias using Client Network Utility. It does not care what machine it points to and can be set...
July 6, 2004 at 8:18 am
Viewing 9 posts - 16 through 24 (of 24 total)