Post reply

Shrink file on stand by server with log shipping

  • August 6, 2004 at 1:47 pm

    #86035

    I have a regular log shipping between a production and a stand by server. This is running fine. I ran a DBCC SHRINKFILE on my data file on the prod and increased free space on that drive. I mean that the freed space was released to the operating system. But I am not able to do that on the stand by server as it is on 'Read only' mode with this log shipping.

     

    Looks this shrinking process is a non logged operation and stand by server does not effect this with log shipping (i.e with logs restore on stand by server).

     

    How do I run DBCC SHRINKFILE for a particular filr on stand by server without losing the log shipping.

     

    I welcome any suggestions.

     

    Som.

  • August 9, 2004 at 8:00 am

    This was removed by the editor as SPAM

  • August 9, 2004 at 9:23 am

    #518201

    Have you tried shrinking the log shipping database using the shrink database via enterprise manager ? If a db is in recovery mode, you have very limited access to the database.

    I have a logshipping setup on 2 serversbut have not had any problems with the database size on the standby server.

    I'll try a few things on my test servers >>> I'll share with the community if I run across anything.

    Good luck "Life is not measured by the number of breaths we take, but by the moments that take our breath away."

    Don't count what you do, do what counts.

    SQL Draggon

  • August 9, 2004 at 9:53 am

    #518211

    If you don't want to break log shipping, you'll have to keep the secondary dbs in either recovery or standby mode. Neither mode allows transactions. Therefore you can't shrink the databases without putting them back to normal status.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply