Database problems can not only be annoying, they can disrupt an organization’s ability to do even the most basic of work. Relying on StackOverflow answers to resolve critical system issues isn’t tenable when customers’ satisfaction is on the line. The database is blamed for a lot of issues, but no one seems to be able to say exactly why or how. Being able to add the expertise of a skilled database administrator to your team can save a lot of time, money, and headaches.
My name is John McCall and I’m a guy who happens to love databases - more than enough for the both of us. I even spend my free time helping people on dba.stackexchange with their database inquiries to stay sharp and give back to the SQL Server community.
Over the past ten years, I’ve focused my education and career on database systems of all types. For seven of those years, I’ve specialized in Microsoft’s SQL Server. And the entire time I strived to create new value in the role of a database administrator.
Many people think of a DBA’s role as performing backups, handling security, and architecting installations. Today, however, I believe that a good DBA should be able to understand system internals, tune queries and application code, be a strong member of a devops team, and have an eye for data architecture.
In short, regardless of what type of issue you’re having, I’m ready and excited to help you solve it.
We start with a 30 minute GoToMeeting or phone call consultation to review your problem and its scope, free of charge.
Whether you want me to fix the entire problem or just diagnose the root cause and let your team do the rest, I’ll create a strategic plan for getting the problem solved.
After we’ve tackled your issue, I provide a write-up of future recommendations, best practices, and resources so that your team can avoid the issue in the future and increase their database-fu.