backup database when it is in use ?

  • Hi Everyone,

    Is it possible to take a backup of the SQL Server 2000 database when the database is in use ?

    Thanks,

    Ganesh

  • Dear Ganesh,

     

    As per my knowledge you can take backups of database but and uncommited data in the database will give problem later while trying to retrieve it.

    Thanks & Regards,

     

    Faheem

     

     

  • Yes. SQL Server backup commands are designed to allow you to backup the databases while they are being used. Using those commands also cause very little impact on your users.

    The backup does a 'point-in-time' backup. In other words....the backup is of the data AS IT IS at the moment the backup begins. Any uncommitted (on-going) transactions are not backed up. That's why you should also do Transaction Log backups. But if you don't do log backups, those transactions will be backed up with your next full backup.

    Refer to the BOL for more information, use the Index tab and enter BACKUP DATABASE.

    -SQLBill

    BOL=Books OnLine=Microsoft SQL Server's HELP

    Installed as part of the Client Tools

    Found at Start>Programs>Microsoft SQL Server>Books OnLine

  • Been backing up for 10 years and never stopped a database for a backup yet. Restores work without a flaw.

  • In Inside SQL Server 2000, the section on backups implies that the backup data is the state of the database when the backup ends, not at the beginning as that stated by SQLBill.

    Excerpt:

    To maintain consistency for either a full or a differential backup, SQL Server records the current log sequence number (LSN) at the time the backup starts and then again at the time the backup ends. This allows the backup to also capture the relevant parts of the log. The relevant part starts with the oldest open transaction at the time of the first recorded LSN and ends with the second recorded LSN.

    SQL BAK Explorer - read SQL Server backup file details without SQL Server.
    Supports backup files created with SQL Server 2005 up to SQL Server 2017.

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

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