SQL Server 2000 DBA Median Salary
-
Does anyone know what the Median Salary for DBAs in the Richmnd, Virginia area? Say for a SQL Server 2000 DBA with 6 years experience (Programming 6, Administration 4) and with Replication and DB Migration Experience. Also, possess a SQL Server 7 Admin MCP (but no other Certifications.)
-
Not sure, might try http://www.justsqlserverjobs.com/. I'd guess you're less expensive than Denver. I'd say avg $70-75k here.
-
It would depend upon the size of the company. I work in McLean VA for a small company about 3 hours from Richmond. I have 5 years experience in SQL 7.0 and 2 years in SQL 2000. No programming though. I make just a little over 50K.
-
You might want to try salary.com.
-
I am an Oracle DBA working for a city goverment and I make about $58K. I also server as the SQL Server DBA, now my CIO seems to think there are no SQL Server DBA's!
(He looked me in the eye and said that not kidding at all!) so I guess it is a good thing I also am an Oracle DBA! -
this is, once again, the mentatity of management. they migrate to SQL Server because they have this perception that "a monkey can do it" as far as implementing and maintaining. after all, a manager can download the code and install it in less than 30 minutes. try doing that with oracle - although I must say, even oracle has gotten pretty simple, at least, sometimes
a good dba should make 100K - 130K in a development environment. A junior DBA should make 40K in production. if the developer does the job right including documentation and training, you don't need a senior dba in production. the software is getting better and better, easier to use, even fixing itself, which is exactly the reason I have decided to shift my perspective a bit. Data architecture remains hot... as does application development.
I know that there are many who will not agree with me on some of these statements... I have been in the business since 1968, and been an Oracle dba since 1982 (versions 2 through 10i), and SQL Server since the late 90s (versions 6.5 to 2005). In addition I have experience in and/or exposure to just about every relational product along the way.
I think the handwriting is on the walls. better software, more automation, better documentation and training... junior dbas, fresh out of college that have "touched" SQL before... and off-shoring to India (which I think is a mistake, only time will tell); but I would not plan on being a dba for a whole career. No sir! I would not.
-
David
You are absolutly correct! Got to stay nimble.
Thanks for your insight
Ken
-
This is not real encouraging for someone just getting involved with SQL.
Rod
-
Also inaccurate. Three years on, and there is still healthy demand for SQL DBA's and good rates - I'm doing OK at the moment.
http://90.212.51.111 domain
-
I worked for three companies that did not have any SQL Server DBA. So all the developers had to wear the DBA hat.
However since all these companies could get by without a DBA, they are not going to hire any DBA !!!!!!!
I should stop moonlighting as a DBA!!!!!!!
-
david russell-253790 (11/27/2005)
this is, once again, the mentatity of management. they migrate to SQL Server because they have this perception that "a monkey can do it" as far as implementing and maintaining. after all, a manager can download the code and install it in less than 30 minutes. try doing that with oracle - although I must say, even oracle has gotten pretty simple, at least, sometimes <img src='images/emotions/smile.gif' height='20' width='20' border='0' title='Smile' align='absmiddle'>
a good dba should make 100K - 130K in a development environment. A junior DBA should make 40K in production. if the developer does the job right including documentation and training, you don't need a senior dba in production. the software is getting better and better, easier to use, even fixing itself, which is exactly the reason I have decided to shift my perspective a bit. Data architecture remains hot... as does application development.
I know that there are many who will not agree with me on some of these statements... I have been in the business since 1968, and been an Oracle dba since 1982 (versions 2 through 10i), and SQL Server since the late 90s (versions 6.5 to 2005). In addition I have experience in and/or exposure to just about every relational product along the way.
I think the handwriting is on the walls. better software, more automation, better documentation and training... junior dbas, fresh out of college that have "touched" SQL before... and off-shoring to India (which I think is a mistake, only time will tell); butI would not plan on being a dba for a whole career. No sir! I would not.
This is a great experience summary from a veteran.I do agree that when offshoring is done to India,sometimes even freshers are hired to touch your databases.Well offshoring was a buisness decision.but I will not agree that all the Database projects that have been offshored to India are poorly managed.Talented resources and buisness model are two factors that i think are the deciding the offshoring of jobs.Its just a question of dollor vs lower currency.
-
david russell-253790 (11/27/2005)
this is, once again, the mentatity of management. they migrate to SQL Server because they have this perception that "a monkey can do it" as far as implementing and maintaining. after all, a manager can download the code and install it in less than 30 minutes. try doing that with oracle - although I must say, even oracle has gotten pretty simple, at least, sometimes <img src='images/emotions/smile.gif' height='20' width='20' border='0' title='Smile' align='absmiddle'>
a good dba should make 100K - 130K in a development environment. A junior DBA should make 40K in production. if the developer does the job right including documentation and training, you don't need a senior dba in production. the software is getting better and better, easier to use, even fixing itself, which is exactly the reason I have decided to shift my perspective a bit. Data architecture remains hot... as does application development.
I know that there are many who will not agree with me on some of these statements... I have been in the business since 1968, and been an Oracle dba since 1982 (versions 2 through 10i), and SQL Server since the late 90s (versions 6.5 to 2005). In addition I have experience in and/or exposure to just about every relational product along the way.
I think the handwriting is on the walls. better software, more automation, better documentation and training... junior dbas, fresh out of college that have "touched" SQL before... and off-shoring to India (which I think is a mistake, only time will tell); butI would not plan on being a dba for a whole career. No sir! I would not.
Sorry to bring up such an old thread. I was researching SQL Server salaries (to see how I compare) and this thread popped up on the first page of links.
It is from 2005 and I cannot help but notice that the market seems to be going to exact opposite direction that this thread predicted. The only jobs available seem to be for "senior" level people with tons of experience on multiple versions of SQL Server. I see many jobs requesting 2000, 2005 and 2008 experience. I don't often see positions for junior DBAs. If they exist, I beleive junior roles are often offered to internal candidates, such as developers, looking to get into the DBA role.
As for offshoring, I used to worry about that a lot back in the 2003-2005 period of time. But it seems like the DBA role is just about the least likely position to be outsourced. So many companies consider their databases to be critical and too important to be allowed out of the control of the company. They may outsource development projects. But the DBA role seems to be one of those positions that doesn't leave the company. That has been my observation in the past 10 years. I am sure some people can point to a few alternative examples.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply