First of all I would like to thank Steve for making mention of SQL on Call.

I admit that a remote DBA is not always 100% of the time the best way to go. Developers for instance that may need some face to face time learning their ways around SQL. When we speak to a perspective client we try to make sure that we express that we are a tool that they can use so that the other resources they already do have can be used more efficiently.

Think of it this way. You had a staff of 2 DBA's but one of them is spending most of the work day checking backups, error logs, jobs, replication and so on. Then that same DBA is creating user accounts and completing work that really is not helping the company "make money". If you could free up this DBA's time so that they are focused more on the aspect of moving the company forward while someone else helps to "keep the lights on". You now have hired an on call DBA that will help you produce more.

For single DBA shops we are the backup or even the assistant. Or a sounding board to help with issues that come along.

Thanks,