Absolutely! I worked with a DBA once who was non-functional. We had an issue with the amount of data in a database. Our backup to tape process (across a network) was taking over 24 hours. The other DBA told the business group they were saving too much data and needed to delete some data so the backup would take less than 24 hours. The business rule was to keep 7 years of data, which is all they had in the database. DBA1 kept telling them they had to delete data and keep less than 7 years worth. I pointed out to the group that they had other options, since the amount of data they had should be able to be backed up in less than 24 hours....buy a backup system (drives or tapes) that could be connected directly to the server instead of going over the network, allow a Full Backup over the weekend and differentials the rest of the week (a business rule required full backups daily), or accept they won't have backups daily.

I would consider the other DBA non-functional.....they couldn't see any other solution and it was basically their way or no way - regardless of how it affected the business. They didn't care what the business required, they only cared about being able to get their job done.

As I said before, a Functional DBA can be defined (in my opinion) as one who can operate in a way that keeps the business functioning successfully. We as DBAs have to understand not only SQL Server Best Practices, but also the needs of the business. Sometimes, the needs of the business have to over-rule the Best Practices.

-SQLBill