I’m the new DBA, and I’m locking down development servers
As the new DBA, I’m here to fix things for you. I’m going to take care of the things that keep causing fires and outages and slowdowns….and I’m locking down your dev environment. Here’s why.
As the new DBA, I’m here to fix things for you. I’m going to take care of the things that keep causing fires and outages and slowdowns….and I’m locking down your dev environment. Here’s why.
Every IT shop has its problems with performance: some localized, and some that span a server, or even multiple servers. Technologists tend to treat these problems as isolated incidents – solving one, then another, and then another. This happens especially when a problem is recurring but intermittent. When a slowdown or error happens every so often, it’s far too easy to lose the big picture.
Some shops suffer from these issues for years without ever getting to the bottom of it all. So, how can you determine what really causes performance problems?
The number one cause of instability in most database environments is SQL Server permissions. Specifically the problem is that people have more access to systems than they should. Let me walk you through a typical lockdown.