both RS and AS are high CPU and Memory users.

they should be on separate servers.

RS should be RS only , NO DATABASE engine.

AS should be AS only, NO DATABASE engine.

a...

one of the reasons for using DB mirroring is someone wants "High Availibilty"

nothing needs to be done to reboot the mirror server in your case.

obviously, because you have one database...

does this person exist yet on the new 2008 server ?

ERPMERKEZ580\Administrator

if not, either add them OR change your scripted out job with the proper login.

you should probably think more about scripting 'out' your jobs and logins and then scripting them back 'in' to the new server. everything you need to move can be scripted....

declare @oper_email nvarchar(100)

set @oper_email = (select email_address from msdb.dbo.sysoperators)

EXEC msdb.dbo.sp_send_dbmail @profile_name = 'SQLMail Profile',

@recipients = @oper_email, @copy_recipients = '',

@importance = 'High', @subject...

clean install or upgrade?

sounds like a "roll code" tool. probably a custom tool / process not described very well. We have some apps with such tools that involve NTFS permissions, check...

depends....

you can't offline a Principal database.

you can't...

i am not sure how you got 2 separate pairs of servers to use the same witness on the same port... that is something i could never do in my...

so you are running multiple instances of mirroring using a single witness on different ports....

i never ever had any luck with that setup. I always have separate instances for each...

hopefully, your principal server has enough disk space to log then 😛

does your witness have 2 instances?

you should restart FIN1.

AVB,

the witness really should go with the mirror. I know there is no best practice to justify this, but in my testing, it is easier to recover in a datacenter...

i would be concerned with running the witness remotely. (unless you mean the principal and mirror will be remote also :-P)

the witness may initiate false fail overs because of latency...

SQL 2005. and yes, the sql service account is a local admin.

i guess i also left out that ALL sql bits are on drive E: (which is mirrored)

we are currently...