Heh... there must be a disturbance in the force. I've been asked to do something similar about 2 weeks ago. Because I have to kill a bunch of data and make it so not only will there be a refresh from prod but have to allow the devs to drop and restore a given point in time so they can do comparisons between a copy with old methods on it (current production methods) and the new methods they want to test, I'm going to have to do things a bit differently.
We're also looking at a cloning feature for the refresh from prod that's built into our SAN.
Just a thought for killing all connections... I don't recommend the "Kill All Spids" method. Instead, I recommend setting the database to single user with the ROLLBACK IMMEDIATE option... nothing is missed that way and nothing that should be killed is.
Anyway, thanks for writing this series.
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.
"Change is inevitable... change for the better is not".
"Dear Lord... I'm a DBA so please give me patience because, if you give me strength, I'm going to need bail money too!"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)