correct

I make the service account passwords long and random so hard to break but I do record them. Reasons being

If you do ever need to change the password you need...

to confuse the issue security release MS08-040 is out which would take you to 3233 if you were already at 3186.

http://www.microsoft.com/technet/security/Bulletin/MS08-040.mspx

setup is only specifying where system db files go, application database files you can put anywhere SQL has access to on the server later. Just specify data file location and...

I would hope you can get a one column one row table past this 'policy'

Anthony,

thanks for that, most helpful. so what it means is in 2005 we can still use the DR process of copying over and restoring the msdb to recover jobs,...

why not?

Anthony question for you perhaps you can help with. If you can get maintenance plans working on a new server after copying over msdb, can you get all SSIS packages...

if you run that in QA it would buffer up the results and return it to you in one go. if you are waiting an hour between checks output the...

sorry, I give in. As long as the database .bak file is restorable and your databse is working............

when you script out the logins, place [] around the login name. i.e.

CREATE LOGIN [00048594] WITH PASSWORD = 'PASSWORD',DEFAULT_DATABASE = master, CHECK_POLICY = OFF

if you use the 2005 version of...

if you do not specify the time it defaults to 00:00:00 hence you won't get 06\30 entries. include the time in the range.

-- or what jack said

if it was me i would stop all agents

then this must have been the file size at the time the backup was taken. Is the .ldf 1mb on the restored db or something bigger. sounds to me like...

just make sure you are able to restore from this .bak file. will be interesting to see how long the recovery stage takes,.