All,

we have a MSSQL DB that has a transaction log approaching a GB! How do I tame it? We researched the issue and it seems we need to create some kind of "restore point" on the database, but have been unable to determine how to do this.

Any ideas? Will DBCC ShrinkDatabase do it? Remember, it is the transaction log that is out of control in size.

Thanks!

Dave