Why did you decide to become a DBA/SQL Programmer?
-
For me it just sort of happened. I had been working as a Windows NT installer for about 2 years and felt I knew all I was likely to learn in that position. This was with Telos Corporation. At the time I was looking for something else a position openned up to help maintain the database for which I and 15 others had been supplying data during our installs (we were providing to the DBA's a list of components with serial numbers as we installed computer systems and set up networks).
After returning from a two week trip, I was surprised to learn that the Senior DBA/Analyst had left the company and the assistant DBA had recommended me for the position. I applied and was givin the position based on the fact that I knew what hardware should be recorded in the database and that I could learn fast. They had seen me learn Windows NT over the past 2 years. When initially hired, I had no knowledge nor experience with Windows NT and only one 5 day class of experience with networks.
I was surprised to be recommended for the position since I had no database experience and even more surprised when accepted. I didn't know what I was getting into and previous to this thought I would like to be a system engineer and get an MCSE certification. I started as a DBA/Analyst May 1999.
In May 2000 I got a job at bigdough.com as an SQL Programmer.
I find I like developing a lot more than administering. I currently have administrative duties, however most of my day is spent developing and improving SQL code.
Robert Marda
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems -
Similar really, started out as VB programmer, even mobile SMS apps required good DB skills (allbeit MS Access V2). Natural project progression through MS Access to SQL-SVR. Now (in a couple of weeks funny enough) I am off on a SQL-SVR 2000 Administration course. Been at it about 5 years now but still want to do the course for myself and not just formalities. (Helps secure my future a little bit since UK is tightening up at present)
Regards
Andy P
Andy P -
I started coding professionally in QuickBasic 4.0 back in the 80s, writing doors for BBS and conversions for different BBS configuration files while still in high school. When I went to college, I chose to be a physics/math dual major and forego comp sci because I really loved those two subjects so much. But I needed a job the summer of my junior year so I could stay in Charleston, SC, and became a VB programmer (4.0).
Fast forward to graduation. I had an Air Force commission and rather than making me a programmer considering my professional experience or a physicist based on my schooling, I was put managing computer contracts. Oh joy! I pleaded with management to give me something technical, even if was an "additional duty." So I was made a webmaster. Web technology in '95 was just getting started. Eventually we got into dynamic sites with DB backends. Front ends using IIS and ASP. The more I got into coding against databases (Access at first), the more I loved it.
I got out of the AF with web, sysadmin, and DB experience. I found a job as a sysadmin first. I continued to work on my other two areas and completed my MCSE, knowing I wanted to do web and db work. My next job was as a web developer where strong DB skills were needed. I eventually progressed into the role as a DBA because that's where I wanted to go. I love my databases.
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
Edited by - bkelley on 01/08/2002 3:06:43 PM
Edited by - bkelley on 01/08/2002 3:07:43 PM
K. Brian Kelley
@kbriankelley -
Another factor that moved me toward the DBA position I took was I wanted to stop traveling (as an installer I traveled two weeks out of every three) and the DBA position was a non traveling position. I am glad I made the move from networking to databases even though at the time I didn't understand the full scope of databases (I thought a database was simply a group of spreadsheets). I've also found that some of what I learned as an installer has helped me with administering databases.
Robert Marda
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems -
I started as a network admin. Got a client-server app dumped in my lap that did not work and spent many, many hours babysitting this app to reboot the server (sql server 4.3 on os/2) and spent time trying to provie the server was a piece of s#$^. I went to software development and did some work with SQL Server and decided I liked it. Also, if I did my job well, then I was not too busy and could pretty much decide what I wanted to do each day.
Managed a small company IT shop (3 people) and decided to get out of mgmt and into DBA.
The rest is history. Been full-time DBA for 5 years and enjoying it.
Steve Jones
-
For me it just kind of snuck up on me while my back was turned!
I started out life as a Programmer in a VAX VMS environment. After many years as programmer, A/P and Senior A/P I ended up covering for the DBA for the VAX based databases when she went on extended sick leave. So I went from never having any DBA experience to upgrading for Y2K compliance, creating whole new systems all within about 6 weeks - good job I was quick on the uptake! But I enjoyed it - in a manic sort of way.
When the DBA got back it was pretty obvious she was not intending to stick around and she never really got back into it fully. So when she left I took it on again (in addition to my Senior A/P role!)
While all this was going on we had a chap dropped into our department to set up an intranet and e-commerce solution. The intranet was SQL Server based. So when he announced that he was leaving guess who got the SQL Server system admin and DBA tasks heaped on her pile - you got it - me
Well there are 24 hours in a day after all.This gets us up to today, and here I am about to be dragged off into the backroom to join the Techies! But seeing that it can't possibly be a full time job looking after 10 Vax based databases and 8 SQL Servers I am being given the role of Network Support Analyst/DBA! Well the management here are just so database oriented (NOT) that I bow to their superior wisdom - but there are still 24 hours a day and I'm sure they can find me something else to do as well!
But I guess I have myself to blame - I did some NT training because I wanted to get a better understanding of SQL Server and how it affected/ was affected by NT - talk about digging a hole for yourself!
-
I started out at college, doing the basics with spreadsheets, word processors & databases (DBase III - I think!) as well as programming in Basic, Pascal then onto C. From there moved into a development role in VB4/Unix C++/Borland C++. Then took a major step backwards working on some ropey basic system of which I cannot recall the name. Stayed there for two and a half years on the false hope of the company switching to Oracle which it did eventually, but too slow for my liking, so moved onto my current position (April 99) as a VB Developer. Job also included support for FoxPro apps, JDE, PC support etc. However, after deciding that we'd use SQL Server 7, nobody here knew about it at all so i was learning it from scratch from a developers view. Then after the importance was realised, I started looking at the DBA role more closely and got to like it a lot...and BOOM...here I am... DBA with bits of development (VB/ASP) and JDE (AS/400) support/integration. There you go..the story of my life! Now workig towards MCDBA :o)
-
This next comment from me probably shows my newness of working with databases. I thought there would be more people that set out to be dba's and achieved that. It seems more people than I thought got into being a dba because they were in the right place at the right time
(or the wrong place at the wrong time depending on how you want to look at it ).Robert Marda
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems -
I've always been interested in the database side of the IT world but started my career doing Win95 support at an outsourcer. Then I did a major shift to a large consulting firm where I was taught COBOL, DB2, IMS and CICS and took that through the infamous Y2K programming for about two years. After that i knew I needed to get out of the mainframe world. So I started learning SQL Server on my own at home. Since my employer didn't do much training and said they couldn't "sell" me at something I had no experience at I went out to find my own job.
Well, I found a great company that had 3 small vendored SQL systems and saw it growing. So here I am 1 1/2 years at the company and we're up to about 20 systems and looking for another SQL person.
I love what I do but I miss the programming (even on the mainframe) I need to learn VB, and ASP soon! Our systems I'm basically just maintaining vendored applications but more and more they're wanting to customize them and it's a large learning curve for me..
Any suggestions? on where to tackle the programming side (w/ SQL experience in mind?)
BTW - It's great to find this site! I've read so much in the last few days and I'm looking forward to the PASS conference.
-
For tackling the programming, I'd suggest reading lots of articles and practicing what is written. Modify it for your environment. Build yourself some tools, even if you throw them away, you will learn something.
For Robert, I think that most DBAs I know "fell" into the job. Not too many start out with that in mind, but then again, before you got a computer career going, had you even heard of DBA as a job?
Steve Jones
-
While working as a Lead Systems Engineer, I worked closely with the DBA's. I was very curious to what they did and slowly worked more and more with Databases. I liked it so much I moved to that department and started over in senority to learn Database Adminstration. I have never regreted my move, and I love working with SQL Server.
-JG
-JG -
Steve, you have a good point. Before getting into networking I didn't know a DBA existed. I had worked doing data entry and data conversion for the Post Office but I never thought about how everything was developed and maintained.
Robert Marda
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems -
I have read with interest the postings here. I am called the back-end developer. I enjoy T-SQL, and have sort of drifted further & further to the back as time goes on. I usually end up doing nearly all of the database developement as well as the server side COMS. Strangely, all the people I work with think it is dull to be in the back end and take no interest in it at all. I think they see me as some sort of geek. This forum makes me think they are wrong, and I'm not the only one like me!! Just wish I knew more!!
-
Most people I know think my job is boring. Maybe bacause I am cautious and move slow. Anything I do wrong usually has more far reaching effects than something a developer does. Plus when the sh** hits the fan, I see WAY more pressure than a developer does.
Another thing is that I've met lots of people who worked with DBAs that were real a**es. Ego maniacs or control freaks. Having done this for a few years, I understand their desire to ensure control and prevent problems, which developers might introduce when writing code without thinking it through. I try to avoid coming off like that and work with others to solve problems. I hope I am successful, but I also document my actions. If someone makes a change without me (like a developer did while I was on vaction) I don't get upset. I let them know my feelings about the change and remind them that if they cause a problem with their actions, I will not take responsibility and let them explain why they did not wait for me or discuss it. so far I think it's working here.
Steve Jones
-
Here is one I haven' read here but myself, and several of my friends are going this route. I started out programming on the mainframe MVS. My first months as a programmer, I grew a very deep interest in relational theory, James Martin, Bachman, etc. and I ended up taking the IBM DB2 manuals home to read. I was hooked. I then went from DB2 to DB2 and DB2/2 using DRDA and OS2. Was a database analyst for a company using Access and moving to SQLSERVER 6.5. I then was a DBA for 6.5 in another startup company. Company wanted to grow but didn't want to spend the bucks to do it. Now I am using DB2, SQLSERVER 7.0 and some ORACLE. I try to stay abreast of all the staying technically vital issues. By the way the first database I ever used was IMS which is Hierarchical. It is amusing to have watch relational theory be debassed enough to add referential integrety. A true sin to any truly relational database advocate.
William H. Hoover
Louisville, Ky
William H. Hoover
Louisville, Ky
sweeper_bill@yahoo.com
(or the wrong place at the wrong time depending on how you want to look at it 
).Viewing 15 posts - 1 through 15 (of 55 total)
You must be logged in to reply to this topic. Login to reply