Don't try this at work !
As a DBA for hire I'm mostly thrown into the deep with dozens if not hundreds of SQL Servers and SA rights. This is usually ok, I do have some DBA skills through my years of experience and I'm not one of those cowboy developers :-)
Sometimes though I get myself, and occasionally also the customer, in trouble by doing something silly.
This session is not about best practices.
I'll show you what can go wrong during day to day DBA stuff and how to fix it.
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.