DBA horror stories
i trying horror stories poor dba practices have encountered or witnessed on years colleagues or maybe yourselves in younger years starting out dba’s, on poor administration/naïve dba’s can wrong in sql server can have negative consequences on availability , performance of vital databases drive key business applications. examples have come across, or “set , forget it” type admin practices youve witnessed , happen negatively , impact that’s had on db section/business interesting hear.
hi,
most of them related backups , security.
1. dba never ran backup because he , employer believed raid5 protect against : viruses, asteroid striking earth,
ntfs corruption, tyranosaurus attack, name it! a stupid mistake far more common might imagine.
2. choosing trivial passwords 'sa' , administrator accounts.
3. never tested dr strategy (including clusters, log shipping, replication, dump all tables csv , whatever). once disaster arrived, dba didn't know
how restore data, parts of missing (like logins , scheduled jobs, ssis packages, ssrs reports, long list of "etc...") or out of sync. plain disaster.
4. keeping dev , prod on the same box (that goes against common sense 101)
sebastian sajaroff senior dba pharmacies jean coutu
SQL Server > SQL Server High Availability and Disaster Recovery
Comments
Post a Comment