Post reply

What do u mean by DB Refresh

  • May 30, 2013 at 9:32 am

    #274374

    What do u mean by DB Refresh..What r the steps to perform this task...

  • May 30, 2013 at 9:40 am

    #1619764

    in my shop, it would mean grabbing another backup of the "production" database and restoring it over the top of the Test Database that the developers and QA groups use for testing.

    that way that database has the "latest" changes.

    the process would involve either finding an existing backup + log files, or taking a new full back, maybe or maybe not with copy only, and then restoring it on whatever is considered the "test'd atabase.

    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!

  • May 30, 2013 at 9:50 am

    #1619768

    In somecases the developers request only the structural differences and least bothered about data (database refresh). In that case you need to compare the current copy of production database vs staging/UAT/Pre-UAT databases and script out only the different DDLs and run them on the appropriate environment. Redgate too SQL Compare helped me a lot with such requests.

    “If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams

  • May 30, 2013 at 9:07 pm

    #1619950

    It means simply we r taking the backup and restoring in Test server..There must be some prerequisites to perform this task...

  • June 2, 2013 at 9:21 am

    #1620326

    Where can be a Test Server ? Do i need a separate physical server for this testing or I can place it in the same machine where my production server is available but as a different instance..?

  • June 2, 2013 at 11:39 am

    #1620338

    Skppani (6/2/2013)

    I can place it in the same machine where my production server is available but as a different instance..?

    Do you want the testing to impact your production server's performance? Do you want deployment errors to possibly break your production database? If yes, then sure put them on the same server.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • June 2, 2013 at 10:18 pm

    #1620376

    No I don't want to....Any way thanks for the information..

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

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