you would have been able to keep the existing identity values by using

set identity_insert yourtable on

perform your inserts

set identity_insert yourtable off

This way you would have been able to...

make sure your sqlagent / sqlserver service account is able (authorized) to access/write to those volumes.

If these drives are mapped drives, use UNC in stead !

- IMO the "execute as .." is the preferable path.

If that cannot be done, maybe the (log)overhead of a simple delete from tablexyz will just do to avoid...

SQL ORACLE explained what it did.

If you alter columns like that you should keep in mind if you are changeing the space needed to store the data.

- char(x) space needed...

just my 2ct (without seeing the actual sql you submit or the actual errormessage )

Does the sqlserver service account have auth to write to the folder/file you have supplied...

the checksum has no relation with previous backups, it only validates the current backup.

You can see a backup contains checksum info by using RESTORE HEADERONLY .

We prefer having single collation server instances !

The impact a instance level is a reinstall in our case.

Mixed collation databases may cause tempdb to have some hickups because

of collation conflicts

e.g....

- did you follow the KB for moving systemdatabases around ?

- can you doublecheck the sqlserver service startup parameters ?

and don't forget to capture CLR-stuff 😉

If you're trying to figure out wich objects are used by your proc,

check out your xml-plan !

you could off course equipt your sproc so it returen the objectid for...

No, these settings are active after stop/start of sqlserver.

they report failed logins in the sql errorlog file;

You can read it directly or import it using exec sys.sp_readerrorlog

Because that proc needs...

checksum is not an option in a maintenance plan gui (not manual, not with the wizard).

However you can check "verify backup integrity".

Jeff Moden (3/14/2008)

I appreciate the feedback, Johan...

The problem is that most of the Devs nowadays are really GUI programmers that learned just enough SQL to be able to do...

most scripts at SSC need to be executed in a query panel or using sqlcmd unless mentioned otherwise.

So in Sqlserver Management Studio, open a query panel to the desired sqlserver...

- is msdtc running at both instances ?

- did you configure msdtc security ?

Windows 2003 vs other windows ?

- did you add the registry key ?

-- zie...