Transaction Logs - Limited Size and optimizations

  • Hi,

    We have SQL Server 2000 setup in various sites across the world, but everything gets backed up and sent to a central site once a week - via tape for an offsite backup. We are looking at ways of doing transaction log backups but the size of the log files tend to be too long to send across our 512K limited network. Now assuming that we cannot do anything about the network (for the moment anyway), is there a way to dump out transaction logs at a particular size, rather than every 10 minutes per say? I believe this is possible in Oracle, but I'm not sure if this is the case in SQL Server.

    Another problem we are having is we shut down sql server agent, perform an integrity check, do optimizations then do a complete backup. When we restart sql server agent we get a massive transaction log. I don't know whether this is because of the optimizations or because of not truncating the logs. If I should be truncating logs when should this be done

    Thanks in advance.

  • I'm an idiot - as a first timer I didn't release this was administration for Notification services.

    I'll be moving my question to Backup -> Admin

Viewing 2 posts - 1 through 1 (of 1 total)

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