Hi Mir,

My original post assumed that the two domains would coexist for a period of time so you could add the new domain logins to SQL Server and duplicate the...

Please don't duplicate posts. New replies in this thread: http://www.sqlservercentral.com/Forums/Topic803368-9-1.aspx

We had to do this last year when we moved to a new domain. We modified the logins on each SQL Server instance. Here's how we handled it:

1....

I don't think you can find that out retroactively, but you can create a Server level DDL trigger to log information when a login is added. See DDL triggers...

I recommend reading Inside SQL Server 2005 by Kalen Delaney: http://www.microsoft.com/learning/en/us/book.aspx?ID=7436&locale=en-us

This is usually done with Integration Services (SSIS). If it's a one-time import you can use the Import/Export Wizard in SSMS. Just right-click on the destination database, select...

1. In SQL Server Management Studio, right-clilck on SQL Server Agent, select new, select job. One

the General page, give the job a name. On...

You should check out copy-only backups in BOL. They're recorded in the backup set, but don't affect the sequence of backups.

If you don't have package logs or auditing, you'll have to script out all the packages and search for the table name. This script helps with that: http://www.sqlservercentral.com/scripts/Miscellaneous/31613/

I only use the SQLAgentUserRole in one situation and it seems secure enough, even though I have a proxy assigned to it. I think it's safe as long...

I see this error occasionally when the tape copy is running a little longer than normal and has the backup file open when a backup job runs. We've alleviated...

I don't do this myself because we overwrite backup files, but if you search this site for something like "delete backups", you'll find tons of scripts and advice on how...

For future reference, those are documented in BOL as part of the sysschedules sytem table, but Silverfox's idea...

Also, nothing says backups have to run at the top of the hour. You could schedule diffs to run at 20 after or half-past.

Maybe you should consider SSIS to copy data between databases. You can transfer other objects also if, for example, you want to transfer stored procedures.