Log shipping maintenance on secondary server

Due to a large input on the primary server, one of our tables had grown
enormously. With the right commands (delete, dbcc shrinkdatabase), we managed
to shrink this primary server down to normal proportions. Is there a way to
do this also for the secondary server?
As it is log shipped you can't.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"JohnPaw" <JohnPaw@.discussions.microsoft.com> wrote in message
news:C2CCBFDF-6C2C-4D62-B5D0-5224E7E5CB59@.microsoft.com...
> Due to a large input on the primary server, one of our tables had grown
> enormously. With the right commands (delete, dbcc shrinkdatabase), we
> managed
> to shrink this primary server down to normal proportions. Is there a way
> to
> do this also for the secondary server?
>
|||That database cannot be shrunk at all? Just delete log shipping and start all
over again?
|||I don't believe it can as it will break the log shipping chain. Give it a
try and see what happens.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"JohnPaw" <JohnPaw@.discussions.microsoft.com> wrote in message
news:2CF05F31-AC52-48D2-93BE-661C783BDBA2@.microsoft.com...
> That database cannot be shrunk at all? Just delete log shipping and start
> all
> over again?
>