As local system works it sounds like a permissions issue.

does the local windows account have logon as a service rights?

there is an option to set the collation during install, you need to ensure you select each tab during the install so things like that are not missed.

Remember you...

no probs, thanks for posting back

duplicate. No further replies here please. see -

http://www.sqlservercentral.com/Forums/Topic930909-291-1.aspx#bm931000

I agree with Brandie. That disclaimer is there for a reason.

There is a post SP3 security fix you should apply, especially if you run reporting services, MS09-062

at its most basic -

select 'exec sp_spaceused ['+name+']' from sysobjects where type = 'U'

copy and paste resilts to another query window and run

you are right the restore won't work as the tran log recovery is not from the database that had the full backup.

That was your last hope, you will have to...

What have you tried so far?

I have not tested the following but I think it should work.

Stop connections to the primary.

If mirroring not already in synchronous mode switch to that...

Thats a big question. you need to look for queries that are heavy on IO, they could be table scanning because an index is...

this suggests your I/O subsystem is stressed if this is a a common occurrence.

This could be because the server is just not powerful enough to cope with the SQL load...

Are you trying to restore over the existing EpitomeRAC database? Do the logical filenames match?

Please supply the restore command you used.

if you mean the onepoint and systemcenterreporting databases (MOM 2005) and whatever the equivalents are called in SCOM there is no special SQL components you need, just the database engine,...

sorry, no can do, but a restart of just SQLAgent should not affect the app.

move the errorlog via the startup parameters in config manager, that will require a SQL restart

this command moves the location of the file

USE msdb

GO

EXEC msdb.dbo.sp_set_sqlagent_properties @errorlog_file=N''new path\SQLAGENT.OUT'

GO

Sqlagent will need restarting to write to this new location though. what's the problem with restarting...

your question has no referall to SAN mirroring so I don't see how it is close, you would be better off starting your own thread.

why not just use logshipping?