Backup Timeout

  • I am tring to backup a database from Enterprise Manager by generating a TSQL command as follows:

    backup database mesonet to disk = 'c:temp\m.bak"'

    Nothing happens. I also recieve [Microsoft] [ODBC SQL Driver] Timeout Expired

    Any advice would be appreciated.....

    Thanks

  • I assume you are running the backup via QA. If so increase your connections "Login Timeout" setting under "Tools" - "Options" then click on the connections tab.

    Gregory Larsen, DBA

    If you looking for SQL Server Examples check out my website at http://www.geocities.com/sqlserverexamples

    Gregory A. Larsen, MVP

  • That seem to work great! Thanks, One more question?? The only thing now is I'm noticing the transaction log has doubled in size. My database size is 435 MB which encompasses one file titled mesonet_data=435MB. The transaction logs (800mb) are as follows: mesonet_ log=201,

    mesonet_1_log = 195mb, mesonet_2_log=24mb, mesonet_3_log=186mb, mesonet_4_log=195mb

    My question is: How do I handle transaction file growth?? At what point can I delete them? What is the best course of action for backing up data?

    Thanks

  • Typically transaction log growth is handled by periodically truncating the log. I would try to perform some action that truncates the log, at least daily. More frequent if your logs are growing quickly.

    Keep in mind how you would recover your data and the backups you have or plan to have, and build in you log truncation process around these backups and your recovery needs.

    Gregory Larsen, DBA

    If you looking for SQL Server Examples check out my website at http://www.geocities.com/sqlserverexamples

    Gregory A. Larsen, MVP

  • If I understand correctly, 1st I would perform a complete backup of the database and also of the transaction log. At this point in time, I would have transactions up to this point. I would then backup log NO_LOG or TRUNCATE_ONLY which would clear out the transaction log??? Is this correct?

  • It is my understanding that when you do a transaction log backup the inactive portion of the transaction log is truncated. I'd do a search on "Using Transaction log backups with database backups" in BOL. I think this information will help you understand more about how to handle truncating transaction logs.

    Gregory Larsen, DBA

    If you looking for SQL Server Examples check out my website at http://www.geocities.com/sqlserverexamples

    Gregory A. Larsen, MVP

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply