moving system databases

http://msdn.microsoft.com/en-us/library/ms345408(v=SQL.90).aspx

You may get away with just moving tempdb (much simpler) - it depends how tight your space is.

As for the user databases I much prefer using alter database...modify...

there should be a text file produced in the LOG directory of the path sql was installed to.

I'm afraid that won't give full control over other peoples jobs.

I have a working setup as described in my earlier post...

If all you have is logins and jobs you would be better off scripting them out and loading them in.

Maintenance plans do not transfer well to another server, in fact...

As long as the two servers are the exact same version the resource databases are interchangeable as it contains system objects only and does not change except when upgrades are...

check out dbcc shrinkfile

note this is a command you should only run in this sort of circumstance where you are short of disk space, don't run it on a regular...

restoring msdb will recover your SSIS packages, if you have saved them to SQLServer. It will also recover the SQLAgent jobs that run them as well.

To backup your RS configuration...

You would normally only keep backups for longer than a few weeks if there was a legal or business reason to do so, e.g. there is often a legal requirement...

I still got a point!

is this any use

http://www.sqlservercentral.com/articles/64016/

read the discussion as well

run this from the command line to return all sql instances in the same domain

sqlcmd -L

edit - sorry did not read question properly :blush:, this only returns instance names

Coozie has duplicated posted here but it is good forum etiquette to post your resolution to an issue to help others.

did you use sp_help_revlogin to transfer the new ID?

what are the results when you run

exec sp_helpuser

and

exec sp_change_users_login 'report'

in the secondary database

if you added the user in the primary...

use this Script to reverse engineer the SQL to attach the databases on the new server

set quoted_identifier off

go

create proc usp_create_attach_db

as

--set quoted_identifier off

set nocount on

declare

@dbid smallint,

@name sysname,

@statement nvarchar(40),

@filename nvarchar(80),

@filename1 nvarchar(80),

@filename2...

Maintenance plans will create a single file for each backup.

I avoid multi file backupsets like the plague. I see no advantages to using them, it means having to work out...

I'd use lowells stored proc method with execute as to grant permissions in the database rather than impersonate a login with sysadmin rights.

If other accounts than dblogin are CREATING databases...