We have a custom workflow engine and process for a lot of our business needs at my company. I wrote it a few years ago, but recently a lot of our existing projects have been migrated over to use the framework. Everyone loves it but our DBAs. Usually I ignore their advice since they still believe that stored procs run faster than parameterized SQL in 2005/2008 databases and consistently have problems keeping transactional logs and such in check.
Long story short... they do not like that we use a database table for our work queue. It runs fast and we have proper transactional locks and such to keep it running with with multiple instances and threads all querying it at the same time. They are asking we change it to something else... but they have no idea what.
Are they just being crazy and I should continue to fight to keep our database structure, or am I really crazy for using a database and should be using something else instead for the queue?