I have now labored in a couple of tech companies varying from 10 individuals to ~150 and I have never experienced a genuine DBA. How large does a business want to get before it merits obtaining a DBA? Do you know the criteria that should be met?

You will find no strict rules, however, many indications you'll need DBA might be:

  1. Higher level of company formality – if you've ISO or CMMI introduced, you may have some strict methods about implementing software. DB deployment will be carried out by DBA.

  2. Large amount of servers – in case your company has large amount of servers, DBA is going to be needed only to maintain then, tune them or patch them. Simply to take care of them.

  3. Difficult programs – in case your company has hard to maintain programs, you will have to employ a couple of maintenance men, among whom is going to be most likely DBA.

  4. High availability programs – will most likely take some DBA simply to be on-site. Just just in case.

  5. Designers unfamiliar with DB particulars – in case your designers know only how you can code, and just how to create table, you'll need DBA to deal with other DB related stuff.

When the database turns into a real bottleneck.

The requirement for a DBA is fairly subjective.

As lengthy as you've databases, you'll have to some maintenance that goes together with it, although SQL Server reacts well generally.

The requirement of a DBA is dependent on how big the information IO a lot more than how big the labor force.

You'll also have administrative tasks with this database that a person needs to do, effectively adding the DBA feather within their cap.

Accept Smok1's answer, just added a couple of points.

Check how big your log file, if it's much bigger compared to database, you most likely require a dba because clearly your backup policy isn't working properly.

And if your queries frequently break, you've designers who frequently write cursors, or customers complain about how exactly slow the application is, you most likely require a dba to performance tune.

Generally if you're creating an intricate data-driven application, you ought to have a dba and/or database developer specialist in your team. Databases would be the heart of the very business programs and really should be created by specialists who understand relational design, set-based queires and gratifaction tuning not application developers who generally make poor database design options particularly when they struggle to create relational databases fit an item oriented model as opposed to the relational model that they're enhanced for.

Time to employ the dba or data analyst is when you begin creating, not once you have tens of millions of records and each query occasions out. A sizable part of performance problems are due to a poorly designed structure which is harder and much more pricey to repair once you have arrived at the stage where everybody knows how slow it's.

We've DBAs mostly for separation of responsibilities concerns. Designers can't run any scripts around the production databases. Our designers not have write accessibility databases they support, unless of course it's granted for them for normal use of the applying. So, if you are concerned about control, a DBA may help.

I'd say inside a company where collecting and mining information is the core business.

A few things you are able to consider when determining.

Guy energy:

  1. Do your designers be aware of database platform utilized by programs delicately?
  2. Could they be capable of singing the overall function that the DBA does (administrative tasks)?
  3. Can your developer handle the administrative tasks additionally for their current work?

If so, allow the designers handle it. Hides

Server Work-load:

  1. Have you got 30 different databases across 20 different servers that replicate to 50 other servers?

Obtain a DBA!

Most software engineers know a minimum of fundamental database maintenance. It might be valuable to employ an worker devoted to database administration when databases become an problem and also you (or worker(s) whom you trust to keep the database) can no more spare the time to do-it-yourself (themselves).

Wherever information is a main issue with a company's business (bank, insurance providers, air carriers, etc) you will see many dba's.

Most likely most software houses have no need for a dba.