see this article for explanation/solution to your problem:

http://support.microsoft.com/kb/264474/EN-US/

As Karl said there's no need to script out users, permissions etc., normal steps should be:

1. script out logins

2.restore database to the server

3.run script to create logins

4.synchronize logins and users, i use...

My "best practice" is to configure sql server and sql agent to run under the same domain account that has no special privileges (except password never expires). This account doesn't...

In order to detach and attach msdb you must stop SQL Server and run it with trace flag 3608 (skip recovery of all dbs except master) - from command line...

Unfortunately, you cannot change collation of existing columns without exporting data, droping column, recreating columns with new collation and importing data back.

This is a nasty situation. If I were...

In addition to profiler and your own observations you can check this article:

http://www.sql-server-performance.com/ak_inside_sql_server_maintenance_plans.asp

Yes you can use sp_detach_db stored proc, move your transaction log file and use sp_attach_db sp to attach db. However it requires db downtime. Alternatively you can add new log...

Your solution is perfectly feasible, original password will be kept. But the drawback is that it requires dropping user from db and dropping login from the server which requires changing...

If we talk about development box, you can simply store sysxlogins.password value for the user in working table (one column varbinary-256) then change the password, run your job and then...

you could create a share on your client and specify UNC path when choosing location for your backup. it should work without problems under one condition - that sql server is...

Probably no need for REPAIR_FAST anyway if there are no error messages reported. it seems to me that it could be hw-related problem (disk or controller). check this article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;826433

Once,...

Can you run DBCC CHECKDB or at least DBCC CHECKTABLE against your db? It's I/O intensive operation, so you should run it during off-peak hours. Start without repair clauses and...

Are you sure that you have got all data files from the original db? Are you sure that your .mdf and .ldf files come from the same db? If the...

As long as your server is up and media that holds transaction log is intact, there is no problem doing that. You can easily test this situation for yourself with...

Just out of curiosity - How did you manage to return tempdb to sysdatabases table? By creating tempdb as a user db with logical filenames tempdev and templog?