Post reply

Copy Database Wizard

  • January 16, 2013 at 9:50 am

    #267112

    Hello

    I want to make a copy of the production database for a developer.

    My backup schedule is nightly - one full (Friday) 6 differentials (Sat to Thurs)

    I can't do a backup because it will break the log chain.

    Can I use the copy database wizard and not break the log chain?

    My steps with SQL 2005 Standard -

    right click database

    Tasks | Copy Database...

    with the option "Use the SQL Management Object method" selected

    Is this safe for my recovery?

    Thanks

    Dave

  • January 16, 2013 at 9:55 am

    #1577927

    As I understand it, a full backup will never break the log chain .

    for me, i just do a backup with copy only for these situations.

    BACKUP DATABASE [SandBox] TO DISK = N'F:\SQLData\DEV223\Sandbox.bak'

    WITH COPY_ONLY,

    NOFORMAT,

    NOINIT,

    NAME = N'SandBox-Full Database Backup',

    SKIP,

    NOREWIND,

    NOUNLOAD,

    STATS = 10

    GO

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • January 16, 2013 at 9:55 am

    #1577928

    You can backup with the COPY_ONLY clause which won't break the backup chain.

  • January 16, 2013 at 9:56 am

    #1577930

    Ha, beat me to it 🙂

  • January 16, 2013 at 9:57 am

    #1577933

    Gazareth (1/16/2013)

    Ha, beat me to it 🙂

    lol fast fingers today my friend,, but am i correct about a full backup not breaking the log chain?

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • January 16, 2013 at 10:01 am

    #1577935

    ok my memory is solid, even if my confidence in it is not:

    http://www.sqlmatters.com/Articles/Creating%20a%20copy%20only%20backup%20to%20avoid%20breaking%20a%20backup%20chain.aspx

    Important : You might have noticed that I've not mentioned transaction log backups or log chains at all. This is because full backups do *not* break the transaction log backup chain whether they are 'copy only' backups or not. It's a common misconception that a full backup will break the transaction log chain, but this is not the case. A full backup does not truncate the transaction log and only contains sufficient transaction log information to restore a consistent database.

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • January 16, 2013 at 10:20 am

    #1577949

    Yep, good clarification on the log chain.

  • January 16, 2013 at 10:42 am

    #1577961

    Thanks to all for the help.

    Dave

Viewing 8 posts - 1 through 7 (of 7 total)

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