Post reply

Moving Databases to New Dedicated Server

  • March 11, 2005 at 10:23 am

    #109876

    My company hosts a number of SqlServer databases on remote dedicated servers.  We are looking to move to another dedicated server because of issues we've had recently with the hosting company. 

    We are trying to calculate how much disk space will be required to move the databases.  The current database sizing can be attained by looking at the properties of each database in Enterprize manager.  However this seems to show extremely large log file sizes:

    Database1: (data file: 24 mb, log: 147 mb)

    Database 2: (data file:16mb, log file: 673mb)

    Is the log file size allocated dynamically depending upon available disk space? Or is there an issue with not truncating the log files during the regular backup process?

    Can anyone advice me on a strategy for doing this or point me to some reference documentation.

    Many Thanks

     

  • March 14, 2005 at 8:00 am

    This was removed by the editor as SPAM

  • March 14, 2005 at 12:04 pm

    #546904

    You're most likely right to change your hosting company.

    For a database in full recovery (or bulk logged) mode the log file grows and grows

    until it reaches the specified maximum size (which isn't set by default) or until

    there is no more disk space.

    When you backup your transaction log (not the database) the backed up part of the

    transaction log is marked as overwritable and the now free segments of the transaction

    log are reused.

    So it looks, as if your hosting company never makes transaction log backups.

    I myself make transaction log backups at least before every full backup.

    Note: Books Online state, that the transaction log is backed up as part of a full backup.

    This is misleading: Only the active part of the transaction log is backed up with a full

    backup and this part is not (and cannot be) marked asoverwritable.

    Juergen.Leis@Web.DE

     

  • March 14, 2005 at 2:49 pm

    #546944

    if you have set up your database option as to grow log file automatically without specifying the maximum size, it can take all your space depending on your system.

    Along with baking up log file,if you have some maintainance downtime for your system then shrinking the log file will help you in reducing size of your log file.

Viewing 4 posts - 1 through 3 (of 3 total)

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