Is this a 'design' DBA role or a 'support' DBA role? Design role is for application design, defining standards, defining data elements, assisting with SQL coding, assisting with debugging, etc. Support DBA is focused on managing DBs that are installed and providing service to the users. It is role that requires more detailed knowledge of the specific product (DB2, Oracle, MYSQL, MS-SQL etc.). The support DBA ensure backups are done, the data can be restored, does restores from backups when needed, tune the settings of the product for optimum performance, troubleshoot when problems.

 

Sometimes these roles are differentiated by the terms 'logical DBA' and 'phyiscal DBAs'.

 

I hope this helps.

Thank you!

 

It includes elements from both but specifically dealing with new clients that are converted over to our product.

 

We are on Microsoft SQL 2008. I gained a few admin functions and the ability to query out db's late last fall and I guess I've picked up on it quick enough that they are interested in me. Going to be quite a change if I accept and LOTS to learn.

I am a DBA, but it depends on what specific job you are talking about.

 

I am a Database Administrator that is responsible for the upkeep and report writing etc. for the agencies I work with. Was an Oracle DBA but we just recently switched to Microsoft SQL Server Database.

 

If this is what you are talking about, it's not too bad of a field to get into. The biggest learning curve will be learning the language. Once you get the sql syntax's down you're on your way.

 

As Bluegrass stated, it depends on whether you will be support or design side of fence. I perform both duties (and yes I am way underpaid lol). Once you have your DB's up and backups established and running, the maintenance side doesn't take up much of my time, the report writing etc. is what takes up most of my time.

 

Thank you. This sounds closer to what I'll be doing. I have a proficient knowledge of T-SQL right now.

 

By the question, seems like you may be taking a pretty big leap. Be sure to have a fallback plan if things don't work out!

 

Very big one. Especially as I'm about to be promoted in the department I'm currently in. They don't want to lose me, but know I have a great interest in becoming a DBA. My current department said and I believe them that they will welcome me back with open arms if I choose to leave.

Thank you. This sounds closer to what I'll be doing. I have a proficient knowledge of T-SQL right now.

It sounds like your story is very close to mine and how I came to be a DBA, although my official title is Systems Administrator, but with what I actrually do it's apples to apples.

 

I started at this company and moved up to become a supervisor and then we were about to change software vendors and all our applications were moving to Windows based. I was on the comittee that was responsible for choosing the vendor after the RFP was sent out. signed a contract with the new software vendor.

 

This software we ran needed a "systems administrator" to oversee the day to day management of the applications. We never had one before so the powers that be at the place of my employment didn't think one was needed so they tried to move forward with no one in that position. Well as we were getting ready to go live I discovered that the people who were supposed to be populating the database with all the records and personel information as well as all the other infomration that needed to be imported into the database was not being done. so on top of my other job of being a shift supervisor, the training officer etc. I was also doing the work to get us ready to cut over with the new software. I was basically working 80+ hours a week....nightmare.

 

Long story short, this new software ran off of Oracle and I along with 2 others (the 2 who were supposed to be doing all this prep work in the first place but didn't do squate...they are no longer employed here btw) went to Huntsville Al to learn Oracle and basically became a Oracle DBA. Once we went live with the new software it was easy for the powers to be to just load all the work on me on top of my regular duties. after working 70- 80 hrs a week for the next 2 years I had enough. Told them I couldn't do it anymore, it was too much work. Basically I was running all the software, backups, DBA duties as well as cartogrpaher for the county since the new software we used was map based. That is when they officially promoted me as system administrator and have been doing the work ever since.....13 years now.

 

So it sounds like you are in the same boat I was sort of, you are learning the basics and once you get the handle of that you will pickit up pretty fast. I will tell you we just changed from Oracle to Sql server and I love Microsfot sql server, although both are similar in many ways as far as syntax etc. SQL is much easier to work with using Sql Server Managment Studio. I also had to learn C++ and use Visual Studio a lot.

 

Funny how you become and end up doing something totally different than what you start out doing for some companies. I really got lucky, I was in the military and didn't get a chance to go to college so I had to work my butt off learning all this stuff on the job and now am at a point where if I retired they would have to hire someone with a college degree. Guess I got lucky to fall into at the right time because I don't know of any company that would hire a DBA without a college degree anymore.

Thank you!

 

It includes elements from both but specifically dealing with new clients that are converted over to our product.

 

We are on Microsoft SQL 2008. I gained a few admin functions and the ability to query out db's late last fall and I guess I've picked up on it quick enough that they are interested in me. Going to be quite a change if I accept and LOTS to learn.

 

Sounds like a good challenge. Getting skills in MS-SQL should serve you well. Seeing a lot of it out there. It is giving the big products (Oracle, IBM DB2) a challenge in the mid-market. It is the DB of choice in the Windows environments. Once you master it, other RDB products should be much easier to pick-up. Good luck.

 

DBAs will always be needed. (And most know it!)....

Thank you. This sounds closer to what I'll be doing. I have a proficient knowledge of T-SQL right now.

If you need training, Safaribooksonline.com offers free 30-day trials and gives you access to thousands of IT books and videos. I am no longer a subscriber but I was for several years.

 

The amount of free, quality training materials that are available is pretty amazing. Many of the videos are on Youtube, but there are other very good sites as well. I don't know if they have any MS SQL videos, but thenewboston.com hosts a pretty good selection of IT tutorials.

 

When you are comfortable with SQL, you might want to wade into a no-SQL database such as Mongo. I plan to move toward noSQL application development myself over the next few months. There are enough free training aids to become proficient with MongoDb development without spending a dime.

There are a couple of free e-books online that I have found extremely useful.

 

My favorite is at the Red Gate book store - Troubleshooting SQL Server: A Guide for the Accidental DBA by Jonathan Kehayias and Ted Krueger. Just get the free pdf version. I've found it invaluable.

 

I know Jonathan through my membership in the Tampa Bay SQL Server Usergroup. He does presentations occasionally at the monthly meetings and at SQL Saturday events across the country. We have this meeting after the meeting at the Courtside Grill every month and he's helped me out a couple of times over drinks when I've been stuck formulating a complex query. Smart guy. Hyper as hell. He's a Microsoft MVP and has a couple of blogs. Just google his name.

I was a DBA for years, but have been in Management for about the past 15. DBA skills are a very portable in the business world. Even more so than developers or System analyst. Very good developers and System Analyst usually have become "semi-" experts in their field. If they are working the Consumer Package Goods industry, they usually have picked up key business processes and how those should be done. Same with someone in IT supporting Medical, or Insurance etc. DBA's while it always helps knowing/understanding the business you are supporting, it is not as critical.

 

When I am looking to hire Developers I look as much at the Business knowledge as I do the technical side. For DBA's that I look much more at the Technical expertise.

 

You can learn about 80% of what you need to be a successful DBA (especially SQL Server) in a relatively quick time (6 - 8 months). To learn the final 20% takes years.

 

The one negative I will mention is that most DBA's have to work off hours and weekends to do maintenance and upgrades. All in all I think you will not be sorry if you move into the DBA role. Good Luck!