Copy/Refresh a database in the night

  • Comments posted to this topic are about the item Copy/Refresh a database in the night

  • Exactly what I was looking for, so thank you for posting the article. (http://www.sqlservercentral.com/scripts/backup+restore+log+shipping/68673/)

    Quick question - Is it common for most DBAs to have different passwords for accounts in the development or test environments?

  • hi,

    Thanks for your script.

    Is that this script is works on single machine? Where can I pass the parameter if the DB's are sitting in differnt physical servers?

    And one more thing to confirm, the script is doing backup the whole db from source system and restore into destignation system?

  • This is based on one serve host. If you want to run this script between server A and server B (and your backup files could be on either one or network somewhere) You have to use linkserver and UNC path to specify A and B. If you spend several minutes, you could figure it out.

    Madhu, This is a teaching script. Modify refactor for your own needs (publish back to us after). If you have a custom need, I will be happy to construct a contract business deal with you. At that point, we can write for you anything you desire.

  • I have never had the same passwords in production as test/dev

  • We have a slightly more complicated scenario...

    Our production database is backed up up using a 3rd party system which does not appear in the msdb tables, on top of that the log files are backed up every 15 minutes.

    Is it possible to use this approach (but introducing a SQL backup to the steps) to backup and restore the database without the backup truncating the logs?

    The database is unfortunately SQL 2000 but running in SQL 7 compatibility mode.

    Thanks...

  • Really liked the concept, but I ran into one issue. The object backupmediafamily.physical_device_name is nvarchar(260) so I changed @filename to nvarchar(260).

    Thanks for the clear and concise article(s).

    Larry

  • GRussell31 (7/16/2010)


    We have a slightly more complicated scenario...

    Our production database is backed up up using a 3rd party system which does not appear in the msdb tables, on top of that the log files are backed up every 15 minutes.

    Is it possible to use this approach (but introducing a SQL backup to the steps) to backup and restore the database without the backup truncating the logs?

    The database is unfortunately SQL 2000 but running in SQL 7 compatibility mode.

    Thanks...

    Where do they store backup info? You just use the same concept and change code to accommodate the scenario. The script operates entirely on backup only. Nothing to do with [backup truncating the logs?]

  • Hi jswong05,

    My understanding is that when a backup is performed it will truncate the transaction logs (and I couldn't find a way to stop this), as trancating the logs will mean that the 3rd party system which backs them up every fifteen minutes would be missing some information.

    Hope that helps explain things?

    jswong05 (9/30/2010)


    GRussell31 (7/16/2010)


    We have a slightly more complicated scenario...

    Our production database is backed up up using a 3rd party system which does not appear in the msdb tables, on top of that the log files are backed up every 15 minutes.

    Is it possible to use this approach (but introducing a SQL backup to the steps) to backup and restore the database without the backup truncating the logs?

    The database is unfortunately SQL 2000 but running in SQL 7 compatibility mode.

    Thanks...

    Where do they store backup info? You just use the same concept and change code to accommodate the scenario. The script operates entirely on backup only. Nothing to do with [backup truncating the logs?]

  • GRussell31 (10/1/2010)


    Hi jswong05,

    My understanding is that when a backup is performed it will truncate the transaction logs (and I couldn't find a way to stop this), as trancating the logs will mean that the 3rd party system which backs them up every fifteen minutes would be missing some information.

    Hope that helps explain things?

    It does not stop you from using this script as long as your backup files can be worked with RESTORe command; if not, that is your pain of using 3rd party.

  • @filename to nvarchar(260).

    It is true, however that Microsoft guy did not know if you use multiples of binary number, you save space allocation. When do you have a device name over 255 characters (Unicode), and why he chose 260?

  • Quick question - Is it common for most DBAs to have different passwords for accounts in the development or test environments?

    Refresh in layman's language means make that database the same. You do have to take care of users after refresh. You can script a job step after database refresh. I will never use the same login on production and QA, Test.

Viewing 12 posts - 1 through 11 (of 11 total)

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