First I would suggest you take care of space issue on DR side immediately.

Second, how often you run your log backups?.....it seems like highly transactional database, you need to run...

can I someone explain why shrinking the db/db files won't release space?

I was thinking the same, if you have 217GB free space, shrinking db files, will release space....and I would...

5.Start SQL Server

Should step 5 is to Stop SQL Server or Start?

Hi,

As long as the mirroring is not removed, the log will not be truncated on the principal side. You need to identify what exactly causing the mirroring to suspend....

Brandie Tarvin (1/13/2015)

---

SQLisAwE5OmE (1/13/2015)

---

GilaMonster (1/13/2015)

---

Script all their modified procs, views, functions out. Backup, restore with overwrite. Run script with all objects (take a backup of their DB first, just in...

GilaMonster (1/13/2015)

---

Script all their modified procs, views, functions out. Backup, restore with overwrite. Run script with all objects (take a backup of their DB first, just in case)

Likely to be...

Grant Fritchey (1/12/2015)

---

If it's a one-time data move, the easiest is going to be to just do a restore. You can drop all the objects on the other side after...

Yes, correct.

Would transaction replication work for this scenario?

Yes, correct Gail. Thanks.

Did you try to shrink tempdb after killings processes?

That might release the space.

If it still not released, give it more time...it might still be rolling back.

Can you try with IP and port# instead of serverne, port

I had similar issue and using IP worked.... There was some issue with FQDN.

Thanks Perry for clarifying, appreciated.

Why you want to shrink the log file?

Maybe its only shrinking 1 GB because that's all the free space available.

If you still want to shrink, take log backups and then...

I'm not sure if I understand your requirements, correctly... Can you clarify?

Was the auto growth restricted to a specific size and it reached that size?