Haslett, Andrew
andrew.haslett at ilc.gov.au
Wed Oct 8 21:01:01 CDT 2003
******************************** I already have the shrinking and re-indexing in place to occur before I back up the transaction logs ******************************** Wrong way round. Backing it up marks the inactive portion 'shrinkable', so it has to be done first. Cheers, A -----Original Message----- From: Julie Reardon-Taylor [mailto:prosoft6 at hotmail.com] Sent: Thursday, 9 October 2003 1:05 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer]SQL LOG File is Huge! 10GB - Help Thanks Eric. I already have the shrinking and re-indexing in place to occur before I back up the transaction logs. It looks like the database is corrupt and is causing massive bloating. Cannot see why this occurred, but it happened overnight. Anyone have this problem before? The transaction logs are backed up every two hours, with the databases backed up in the PM, shrunk and re-indexed every night. Julie Reardon-Taylor PRO-SOFT OF NY, INC. www.pro-soft.net _________________________________________________________________ Instant message in style with MSN Messenger 6.0. Download it now FREE! http://msnmessenger-download.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not.