Brett Barabash
BBarabash at TappeConstruction.com
Wed Feb 4 16:15:40 CST 2004
Thanks Debbie, One thing confuses me, though: >From what I've seen, it looks like when you issue a BACKUP LOG statement in SQL, it automatically truncates the log (which is why there is a NO_TRUNCATE option available). However, our DB Maintenance plan that backs up the log file doesn't seem to truncate it. There isn't even a truncate option. I was thinking about adding a step to the job, to execute a BACKUP LOG WITH TRUNCATE_ONLY command, followed by a DBCC_SHRINKFILE command to truncate the log and reclaim unused space. Am I going about this the right way? Thanks again for all your help. Brett -----Original Message----- From: Elam, Debbie [mailto:DElam at jenkens.com] Sent: Wednesday, February 04, 2004 11:21 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] OT - SQL Server transaction log size We do incremental backups several times during the day. After these backups we truncate the log. The log actually gets erased during truncation. It is a temporary storage spot only. Once the backup is complete, the log is superfluous. Time your backups based on how small you want your log file to stay. Once a week is not sufficient for the type of activity you see. At least once a day is what I would run. We run four times a day as a default. Once a week is probably better for full backups. Debbie -----Original Message----- From: Brett Barabash [mailto:BBarabash at tappeconstruction.com] Sent: Wednesday, February 04, 2004 10:48 AM To: 'accessd at databaseadvisors.com' Subject: [AccessD] OT - SQL Server transaction log size Forgive me for not posting this to the other list. However, my hunch is that there are many like myself who only subscribe to AccessD. For those of you in charge of the care & feeding of your SQL Server databases, how are you managing the transaction log file size? We have a very active system that has generated log files in excess of 6 GB (even bigger than the data file!). We have a weekly shrink database job that runs on data and log files, but my impression was that it just rearranges fragmented data and truncates unused pages. Is this correct? In Enterprise Manager, if I select the Restrict file growth option, will it automatically truncate old entries, or does it act like SS 6.5 and halt all new transactions until the log file is dumped? Ideally, we would like to retain any transactions that occured between nightly backups. Are there any utilities that can assist in this? If not, what is an appropriate log file size for a 5 GB database? The reluctant dba, Brett Barabash, MCP Tappe Construction, Co. Eagan, MN bbarabash at tappeconstruction.com (651) 256-6831 "One thing a computer can do that most humans can't is be sealed up in a cardboard box and sit in a warehouse." -Jack Handey ---------------------------------------------------------------------------- ---------------------------------------- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. This footer also confirms that this email message has been scanned for the presence of computer viruses. Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority, states them to be the views of Tappe Construction Co. Scanning of this message and addition of this footer is performed by SurfControl E-mail Filter software in conjunction with virus detection software. _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com - JENKENS & GILCHRIST E-MAIL NOTICE - This transmission may be: (1) subject to the Attorney-Client Privilege, (2) an attorney work product, or (3) strictly confidential. If you are not the intended recipient of this message, you may not disclose, print, copy or disseminate this information. If you have received this in error, please reply and notify the sender (only) and delete the message. Unauthorized interception of this e-mail is a violation of federal criminal law. This communication does not reflect an intention by the sender or the sender's client or principal to conduct a transaction or make any agreement by electronic means. Nothing contained in this message or in any attachment shall satisfy the requirements for a writing, and nothing contained herein shall constitute a contract or electronic signature under the Electronic Signatures in Global and National Commerce Act, any version of the Uniform Electronic Transactions Act or any other statute governing electronic transactions. _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -------------------------------------------------------------------------------------------------------------------- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. This footer also confirms that this email message has been scanned for the presence of computer viruses. Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority, states them to be the views of Tappe Construction Co. Scanning of this message and addition of this footer is performed by SurfControl E-mail Filter software in conjunction with virus detection software.