Practicing earthquake safety at home and creating a disaster safety kit before the next earthquake is crucial to your family’s safety. Just enough time so you can Drop, Cover, and Hold On before the shaking begins.Įarthquake safety involves being prepared and knowing what to do. I'd probably go with the script route, but again good sign to see someone concerned about preventing this.Home > Earthquake Risk > Personal Preparedness > Seven Steps to Earthquake Safety The Seven Steps to Earthquake SafetyĮven with California’s MyShake earthquake phone app, you may only have between 10-60 seconds to get ready for a major earthquake. I am sure there are other approaches you can take. Again a bit of a pain but something to consider. Different passwords in each, and get into the habit of always using that to restore from.
In Production you can call it Prod_Restorer or whatever you like. Use a different account for restores - Create a SQL Authenticated account and always do restores as that account.Kind of a pain depending on what you do on a day to day basis, and depending on what that looks like, it may be too much of a burden to take, but something to consider. And when you truly require SA rights, or need to do a restore, etc. So you could create a set of permissions for every day use and put a "DBA_Normal" AD group into that. And that AD group is empty except for when someone truly requires DBA access. In some instances of this, you'll have a DBA_SA AD group. It is so much easier for a DBA to have SA rights, but in some organizations the DBAs don't have it. Lower Your Default Permissions In Prod Many financial institutions require this for compliance already.
Now when you have to restore and your CIO is standing behind you rapping her fingers on your cube wall repeatedly saying "is it done yet?" you don't have the added stress of doing the process a different way. You are also preparing yourself for emergencies, by having a process, having a script and having an ability to use the same approach each time. So this code may not be exactly what you do, but the point is - you are requiring a positive step to identify where you think you are and checking to see if you are where you think you are.īy using a Script you are also requiring yourself to type out items like the database you wish to restore, you are forcing yourself to look things over, pay attention to the SSMS window and see which server, etc. You could do something like check your and have some logic in there to require a positive action.
You can write and test restore scripts ahead of time. Your milage may vary but some ideas to get you thinking: There are potentially a few things you can do, though. I've seen people burned by an "oops" restore before. I like that you are worrying about protecting from your ability to make such a mistake. If you are granted SA rights, there really isn't much to do there to prevent it.
0 kommentar(er)
