At Quest Software, my official job title is Domain Expert.  That means I’m supposed to be the master of my domain – my domain being SQL Server, storage area networks, and virtualization.  Ideally, I’m also supposed to be pretty good at the Quest products for that stuff, too.

I don’t have a written job description (as far as I know) but my daily routine revolves around:

• Learning the latest and greatest tools and tricks for SQL Server DBAs
• Teaching other people about those tools and tricks (customers, developers, support staff, etc)
• Influencing product direction by pointing out things DBAs need help with
• Testing Quest products to see if we’re getting it right

I interact with a lot of SQL Server people at Quest – developers, support, marketing, execs, and so on.

If you’ve run into challenges with Quest, whether it’s people, products or processes, and you haven’t been able to get ’em fixed through normal channels, let me know about it.  I can’t be the first person you call for tech support, and I can’t get you special discounts on software, but there’s usually something I can do to help when things aren’t going well.  I’ve heard from a few community members that they had questions, but they didn’t want to bother me – by all means, feel free!  If there’s something I can do to help, I’m all over it.

I am by no means a figurehead here for Quest: the things you read here are my own poorly-thought-out opinions alone, and do not represent Quest’s official viewpoints on anything.  Just think of me as a buddy who works for the company.