You've run sp_updatestats.

Did you try to dbcc dbreindex('Yourdb') with count_cows ?

Be carefull, this will invoke heavy locking, so plan it to run in "easy" times.

You're no alone ...

With this site, you'll never walk alone

Thanks for the confirmation, Brian.

We did some testing regarding the clusterserviceaccount about 3 years ago.

It works just fine with these minimal rights (login only).

it even doesn't heed any rights but login because your clusterservices heartbeat uses it.

At our clusters the clustering service only was added as login for the server and it works...

use profiler to intercept the activity and analyse !

especialy look for hints in statements. You could use a trace-flag for the system to disregard hints and see what th effect...

you could schedule a job at you "regular" sqlserver and have the steps execute OSQL

to backup the needed databases and then copy them to your safe place.

all steps would...

Thanks for the link, wich is a nice article.

The problem with these circular references is that I would need to exclude all "new" items that would already be in the...

oops .. overlooked that because we don't use it in that way

- with SQLServer2005 you can perform this by granting at schema level.

- In sqlserver2000 you can only add the user to the db_owner group of the database. But then that...

just my 2ct

nvarchar(..) is double byte so nvarchar(1000) takes max 2000 bytes + length indicator.

making it ntext will allow you to store up to 2G for that column.

Downsides are :

globSMOSrv = the smo.server

as stated in the first of this thread :

oDatabase = globSMOSrv.Databases.Item("master")

in VS2005 immediate window

?oDatabase.CompatibilityLevel

Version80 {80}

?globSMOSrv.Information.VersionString

"9.00.1399.06"

Now what's the point of not having at least the system...

The strange thing is that I can implement storedprocs that use e.g. CTE's and execute them without a problem or warning

if this is not a sql2000 sp4 system ...

There have been issues with parallelism with sp3(a), and it took a while until there was a hotfix to overcome the buggy...

You 'll need your db in bulk or full recovery mode.

check out http://www.sqlservercentral.com/columnists/kKellenberger/restoringtoapointintime.asp