DBAs versus SQL Server
-
What is the database administration ratio of SQL Server database servers (one instance per server) to SQL Server DBAs? Or, would it be put in terms of number of databases to DBAs?
Thank you
-
If you ask a DBA, it should be more.
Ask the bean counters, DBA's are not required. The servers just work...
Cheers,
Crispin
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
-
Our company has over 60 SQL Servers and only 2 DBA's. Even if you automate all the maintenance, monitoring, and patches/service packs, etc., you still need people to support the servers.
Thank you
-
To some people, two is one to many.
I am constantly fighting for more money for hardware. Our machines are getting old.
Peolpe think if it's working, don't touch it. Never mind the event log full of disk warnings.)
Problem is when something happens and data is lost, who gets the blame? The two overworked DBA's.
Don't get me wrong, I love my job, just enjoy venting every now and then. 🙂
Cheers,
Crispin
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
-
Venting good.
We have several SQL Server databases and one system DBA and I'm helping out as a part-time Apps DBA. It takes a lot of coordination to keep everyone happy.
Patrick
Quand on parle du loup, on en voit la queue
-
I am the only DBA/Developer at my organisation and I am currently looking after 7 Servers with several databases on each plus one large Data Warehouse. They never had a DBA before they hired me 6 months ago and only decided they needed one when they went ahead with the Warehouse and the consultants they had in told them they really should hire a DBA. Never had a problem getting better hardware though, thank goodness.
Cheers,
Angela
-
Crappy, keep on writing reports, explaining the problems, estimates, if not getting your heads of the sand scenario I have warned you, disk full, lost data, cost to resolve. How to resolve and costs.
Tell users to speak to the manager.
Maybe send report to boss's boss.
-
🙂 What I'll do is next time I take leave (Ummm, might retire by then) I'll dialin and stop the service randomly. Blame it on the disks, old server etc...
Cheers,
Crispin
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
-
It depends on the role the dba is supposed to perform. I my case I'd describe it as firefighting. Every day is a supprise
.I manage +- 60 sqlservers most oltp. When the dba is supposed to ad value in design/development-time this ratio (imho) cannot be kept. In my previous job we were mandatory member of the design/development-process and we were with 6 dba for +- 100 databases.
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data/code to get the best help[/url]- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
-
The term DBA covers a variety of tasks.
- Basic routine tasks such as back-ups.
- Development and design specialists.
- Highly technical installation and configuration specialists.
- Data warehousing specialists.
If you just need the routine stuff then I would say you need to allow for the DBA being off sick, on holiday, job interviews for a more challenging role etc.
Development and Design specialists will depend on your development load.
Highly technical specialists depend on the size and complexity of your organisation. I would suggest that for small to medium size organisations this level of speciality is a buy it in when you need it item rather than a permanent position.
Start by defining what you need your DBA to do and try to estimate the quantity of work. That will give you a better idea than trying some formula to do with number of servers and number of databases.
-
Thank you!
-
I work for a utility company. We have 18 SQL Server servers running 25 instances, 42 Oracle servers running 58 instances, and ADABASE on the mainframe. There are 3 of us. Adequate to keep things running, not good enough to insure no data loss. Not good enough to keep up with Patches and new features that might save data and time.
-
I work for a large company. We have 38 SQL Server servers running 365 databases (3 Terabytes of Data) and 118 Oracle servers running 128 instances. There are 2 of us. We are Oracle and SQL Server certified and it is difficult to keep things running. We are running on so many dofferent OS environments. Two years ago we had 4 DBAs just for the Oracle application only. We do keep up with our patches and new application implementation. Most of our day to day stuff are automated by scripts.
I would say 100 databases per SQL Server DBA and 20 databases per Oracle DBA...
-
We have 39 servers running 42 instances. We have over 600 databases. There are three clustered servers. There is one full time DBA, one junior DBA and the manager of the group is a part time DBA. We hardly ever get involved in development DB design (no time). We spend most of our time doing normal maint (backups, etc) and planning consolidations, upgrades and patches. We have gone from 92 servers two years ago to what we have today. Management wants us below 20 by next year. Good thing hardware just keeps getting faster.
-
I don't think that exists a rule for that. As others say, there are different kinds of enviroments. If you are a 'fire fighting' DBA, maybe a few instances are enough to
justify your headaches. I currently administer 60 dbs over 10 servers, and have most of the maintenance tasks automated...
.Viewing 15 posts - 1 through 15 (of 26 total)
You must be logged in to reply to this topic. Login to reply