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.
is pronounced "ree-bar
" and is a "Modenism
" for R
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. 😉
How to post code problems