SQL Server Performance

Srinking Database for LogShipping

Discussion in 'SQL Server 2005 Log Shipping' started by rayala.thulasi, Aug 28, 2009.

  1. rayala.thulasi New Member

    Hi All,
    I have Database with 500 tables intially, now i have separated 500 tables in to two different databases.these two databases has been configured for log shipping process.now i am planing to Shinking the intial database to release the unused space.in this case is my logshipping process will distrub? do i need to reconfigure the Log shipping process again? Please help me to proceed future.
  2. satya Moderator

    Why do you want to SHRINK, do you have any storage issues on server?
    In any case the log shipping will be affected, so you have to stop before SHRINK operation and then restore database to secondary server in order to continue the log shipping, this is better way than leave the options to system when SHRINK is involved.
  3. rayala.thulasi New Member

    HI Satya,
    Good Morning , yes i have actual database size is 400gb and actaul size is 200gb remaing 50% is unused space.so it's the management decision to releaze the unused space on the server. thanks for your kinf information.
  4. rayala.thulasi New Member

    Hi satya,
    One more update in this process.To confirm the above query i have configured Log Shipping Process in testing server.after successfull run of process we Shrink the Dabase which has been configured for LS Process.After Shinking the Database again i ran LS Jobs it's ran perfectly without any distrabance.Finslly the actual size has been updated in the LS Server.
    Thanks for your kind update.
  5. ghemant Moderator

    I would suggest you to refer below links http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=111856 and http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=43966Regards

Share This Page