also, if my mirror server fails (for whatever reason) and the log size is limited on my primary, whats going to happen?

I lie - removes currently unused space, but does not remove committed transactions.

Will open a new thread

I got it - you have to back up the log file first, then shrink it. Seems to do the job.

Cheers

Alastair Jones

sorry? - dont quite understand

As separate from my other query about manually forcing role reversal, i am currently wondering how to manage the size of the log file to stop...

the command DUMP TRANSACTION [database_name] WITH NO_LOG gives me an error that i cant as the DB is now used for mirroring.

Ive restricted the max size of the log file,...

Mike

I found that command on MSDN after some googling, so I started a shrink on my primary DB, limited the bandwidth on my mirror (to match the speeds ill get...

Thanks for your help Mike

Alastair Jones.

yeah ok - hadnt thought of that - but this will ONLY help with the T log shipping, correct? theres nothing I can do to compresss the data thats being...

I'm using some bandwidth limiting software on my mirror server - a reindex of a tiny database (which sent over about 40MB of data) took 3 minutes over an equivalent...

ive got it configured without a witness, and I am told by my developers that the system MUST run in ASYNC mode, so therefore failover is manual. If i DONT...

I reindex everything over the weekend which I think would probably mess up the trans log shipping if im shipping over a wan - what about if I do it...

As I cant qualify

exec msdb.dbo.sp_start_job @job_name='xxxx

with the actual job name, I run this section alone from the EM...and I get a snap of the entire database....

can you tell me how...

forgive the newbie - where do I get the job name from?

ill buy you a beer if it works - cant test it at the moment as my box is being hammered by a previous attempt that then snapped the entire...

wow. thanks.