How do you manage a large environment?
I was a DBA for more than 400 instances.
- Did I do all that by myself?
- Was the whole environment standardised ?
- Did nothing ever go wrong?
- Did I look through all the error logs on a daily basis by hand?
Of course the answer to all these questions is a big fat NO.
I'll explain how managing a large environment like this works, and I'll do it in such a way that even if you have 5 instances, this should still be useful.
Expect 50% processes and war stories and 50% scripts and demos (lots of PowerShell of course, but not everything)
I’m a SQL Server consultant based in the Netherlands. I’m a SQL Server MVP and I’m the co-founder and current chairman of the Dutch PASS Chapter and a member of the volunteer team for the Dutch SQL Saturday’s. I’ve done a whole lot of pure DBA work managing 100′s of servers and learning something new every day.
These days I spend a lot of time on just a few servers containing some large databases and the better part of the day is spent with SSIS. In both roles I’ve been using Powershell a lot. I joke sometimes that I replaced myself with a powershell script when leaving the DBA role, but these days I automate so much that I have to watch myself and not actually do just that
- Session Files Explorer
The network name cannot be found.