accidenly dropping production

  • rk1980factor

    SSCommitted

    Points: 1681

    What are the proper and idol steps to take if developer working off hours accidentally drop major production database?

  • Thom A

    SSC Guru

    Points: 98022

    Are you talking from experience here, or in the event of? If the latter your developer shouldn't have access to be able to DROP a production database; they are developers after all. After that problem is solved then the issue can't happen.

    If the former, the first thing you need to do is get your system back up and running. You'll need to restore the latest backup of your database, which if you are using transaction logs hopefully won't be too old. After that ensure you have documented how much potential data you have lost; for example if you perform a transaction log backup every 10 minutes and the DROP occurred at 19:05 then you probably had 5 minutes of lost data. What you do about that is up to the business, as we have no exposure to the information you're working with. If you have logs that record the actions taken on the application else where, then it's time to start trawling through those to try and recover as much data as possible.

    Then, finally, you need to see my initial point; revoke the permissions of your developers, they should not be able to DROP a production database. It's then up the the business to decide if any re-training, disciplinary action is taken against the developer, DBA, responsible persons (in my view, the developer is not solely at fault).

    Thom~

    Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.

  • Jeff Moden

    SSC Guru

    Points: 993644

    Again, this sounds like another interview question.  Again, I'll only provide hints because if you're applying for a DBA job, it's YOU that has to learn and simple memorization isn't going to do it.

    First of all, Developers shouldn't have the privs to drop anything in production, period.

    Second, COMMUNICATE immediately.

    Third, you really need to study things like BACKUP, RESTORE, RPO, RTO, and, possibly, SAN snapshots.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
    "If you think its expensive to hire a professional to do the job, wait until you hire an amateur."--Red Adair
    "Change is inevitable... change for the better is not."
    When you put the right degree of spin on it, the number 3|8 is also a glyph that describes the nature of a DBAs job. 😉

    Helpful Links:
    How to post code problems

  • Eric M Russell

    SSC Guru

    Points: 124935

    Step 1, notify the DBA, and explain in detail how you as a developer were able to drop a production database in the first place, so the DBA can revoke that permission.

    Step2, polish up your resume and start apply for a new job first thing in the morning.

    "Do Not Seek To Follow In The Footsteps Of The Wise. Seek What They Sought." - Matsuo Basho

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

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