done

May I add this has been a guideline for quite some time now :

The curse and blessings of dynamic SQL

Keep in mind NOT to have your website run with sa-privilages !

but you'll need security-admin privileges

Keep in mind, one should prefer "least authorities" above "all privileges"

That's how it works for me

 All my sql7 and sql2k servers have these parameters.

I did forget to mention -T3605 makes sqlserver write this...

if you want deadlock-explanation (involved spids and statements) add these parameters to your sqlserver startup parameters :

-T1204

and

-T3605

use the -c parameter

from BOL isql-utility :

-c cmd_end

Specifies the command terminator. By default, commands are terminated and sent to SQL Server 2000 by entering GO on a line...

in addition to wz700's reply :

regarding the linked server : it depends on how the linked server is defined at your local...

- wich version of sqlserver are you using ?

- does the table have a clustering index ? (indexid = 1)

maybe this can be used ...

-- how to determin SQLServer Uptime

--  Tracking Uptime by Brian Moran http://www.winnetmag.com/SQLServer/Article/ArticleID/38042/SQLServer_38042.html

--

SELECT @@servername as ServerName, datediff(mi, login_time, getdate()) as SQLServer_UpTime_Minutes

FROM...

Check out cadebryant 's article

Using UDFs to avoid cursors

 : http://www.sqlservercentral.com/scripts/contributions/439.asp

it's always a gamble with this question since there are more than one errors !

use master e.g. is not mandatory, it can be any database.

Did you also switch service-accounts ?

did you kick out builtin-administrators ? If yes, check sqlagent is not running on localsystem !

Did you have a blanc sa-password

Check uot SQLDMO is BOL.

It has scripting capabilities.

Check uot SQLDMO is BOL.

It has scripting capabilities.

go straight forward to sp4, gon't go to start, you'll not receive 2000 startmoney

MS servicepacks are cumulatively.