SQL Server transaction log

I have 2 servers configured in a primary secondary model with transaction logs shipped from the primary to the secondary every 10 minutes.  The log file on the primary is 32Gb.  Is it possible to reduce this without breaking the log shipping? and if so what is the best way
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Just shrink normally on the primary and it will shrink on the secondary as well.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
gleadsAuthor Commented:
Can you be more specific?  Shrink it or truncate it?  What load will this place on the server (primary especially) while this occurs?
Get a highly available system for cyber protection

The Acronis SDI Appliance is a new plug-n-play solution with pre-configured Acronis Software-Defined Infrastructure software that gives service providers and enterprises ready access to a fault-tolerant system, which combines universal storage and high-performance virtualization.

truncate does not shink the file size, but marks the space as unused within the file

shrink if your log contains free space and you want to free it

so do one then the other

CHECKPOINT first will make it possible to truncate
gleadsAuthor Commented:
deisn't truncating break log shipping though?
You can make a full backup of database then the log file will be truncated after full backup.
gleadsAuthor Commented:
their is a full backup taken each evening of the datatbase, do i need to take one of the log fil - will this not break the log shipping though?
John EsraeloDatabase / SQL DeveloperCommented:
What's the size of this DB to begin with.. if you have a large Trn every 10 minutes then either there is something wrong or log-shipping is not suitable for this purpose and should choose replication ... if your tables have proper primary keys that are also suitable for replication purposes... otherwise depending upon your bandwidth .. you may not even get a chance copying the first Trn to the second server..
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.