September 16, 2010 at 12:15 am
Hi All,
Can any one explain that, What are MSSQL DBA Lines are there in field, I am new in DBA field. Pls pass comments,
Ali
MCTS SQL Server2k8
September 16, 2010 at 12:39 am
In my experience, the term DBA (Database Administrator) ends up falling into 3 camps, which you have to read the actual job description for to figure out what they want... because while we're all working on the same box, expertise is different.
1) The administrator: This is the default thinking of DBA from outside. We setup jobs, make some SSIS packages, watch for errors, patch servers, and optimize poorly performing code. They dabble in some development work because of optimization, and architecture so they know what to look for when the systems break. They setup the cluster and deal with the services, and usually handle all the login and communications, as well as overall security, of the boxes. A small team of these people, who are very good at their jobs, can handle entire datacenters.
2) The architect: This person is usually someone who understands as much theory as they do hardware, and the architect falls into two possibilities. One's the system architect. He knows his servers, his cpus, his RAID systems, and can design the platform for SQL server well. This part of the job also overlaps with above, the administrator. The other half of the architect is core principal and core design, knowing how to organize data intelligently for both the necessary data algorithms to produce business results and the data tables themselves to make sure the system runs well. They're usually working in ERWIN, Visio, or any one of a number of external organization apps to create ERDs and the like. They tend to work mostly at the beginning of a project to lay the groundwork for the next group. They work, mostly, a single project at a time for longer periods of time, and then they're gone for the next big job.
3) The Procmaster/Datadude/developer/running target: This is the guy in the day to day trenches on any specific number of projects. So far I find that usually for every 2-4 applications, you have one of these folks. He'll be dealing with bug fix tickets from business, new modules to attach to the core design, feature design work, and the day to day bad data in load, go find it type things. Most people in SQL get their start here. It's dirty work, but it's more compact and bite sized, and where most new people should be looking to start out. You can concentrate on one proc, or one idea at a time, without trying to put an entire world in your head at once.
There's a fourth position that's becoming more common, but doesn't get stuck under the generic DBA tag, and that's a Report writer. Exactly what it says, they're usually more proficient in SSRS and SSAS then they are in the SQL Server engine itself, and ride on top of a well formed database. They may, or may not, be under the 'datawarehouse specific experience' some jobs will desire.
Now, I'm sure other people will have different opinions, but that's my take on it. 🙂
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
September 16, 2010 at 12:45 am
Historically, I've seen two major divisions:
1. Production support - these folks start caring about things from the database level up... they are concerned with performance, backups, hardware, jobs, etc. The starting point for them is the database as a whole.
2. Development support - these folks care about everything in the database, and only the database. These folks will be the ones writing the code (T-SQL developers), designing the database (data modelers), etc.
In recent years, and with the expansion of SQL into BI, there have developed a few other areas:
1. SSIS - everything concerning ETL.
2. SSRS - everything concerning reports.
3. SSAS - everything concerning data warehousing databases
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
September 16, 2010 at 12:45 am
In addition to what Craig has listed, there are the DBA's that must fill all of the roles listed by Craig. Sometimes, there is just no way around having to take care of all of the dev stuff, the architect stuff, prod maintenance and the warehouse.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
September 16, 2010 at 1:04 am
CirquedeSQLeil (9/16/2010)
In addition to what Craig has listed, there are the DBA's that must fill all of the roles listed by Craig. Sometimes, there is just no way around having to take care of all of the dev stuff, the architect stuff, prod maintenance and the warehouse.
You're correct as always, I should have added the last, unofficial title: Dude in corner talking to himself pulling his own hair out while waving a chicken at the server hoping it stays up just one more day so he can finish those other 5 projects before swapping the raid out.
[Double checks his bald spots and makes sure his chicken is still in place.]
No idea what you're talkin' about there, tho'... really. 😉
The SQL Server Handiman, whatever you need, I'm there for... but please, only 90 hours a week? I'd like to sleep on Sunday. You do end up with one of the strangest SQL educations in that job, though. Kinda spastic and swiss-cheesish, however, without a good mentor... which might explain a lot. 😉
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
September 16, 2010 at 1:14 am
well you may have a flavour of SSRS and SSIS Bussiness Intelligence
but specifically in DBA track, i think you may go for multi RDBMS
September 16, 2010 at 1:21 am
fawwad (9/16/2010)
well you may have a flavour of SSRS and SSIS Bussiness Intelligencebut specifically in DBA track, i think you may go for multi RDBMS
Hm, that's true, there are more positions these days for dedicated DTS/SSIS builders, but they usually fall into the developer category eventually.
As to multiple RDBMS studies, I would recommend heavily against that, at least at first. While knowing the capabilities of some of the common software is a good idea so when you're asked as the resident database expert "Why are we spending all this money when MySQL is free?!", it's hard enough to get *one* system under your belt well enough at first.
That, and fully understanding a single system well will help when you approach other systems, as you'll have a better understanding of the underlying ideas and you can figure out where the other software excels, and where it fails, compared to the one you're already strong in.
It can be hard enough getting the complexities of SQL Agent, at first, for example, then to try to couple that with CRON, Windows Scheduler, and any number of other methods.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
September 16, 2010 at 1:29 am
Thanks Craig Farrell and All Others, its enough to me, to get an idea of DBA lines.
thanks
Ali
MCTS SQL Server2k8
September 16, 2010 at 1:33 am
Ali Tailor (9/16/2010)
Thanks Craig Farrell and All Others, its enough to me, to get an idea of DBA lines.thanks
A pleasure, good luck to you.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
September 16, 2010 at 11:11 am
Craig Farrell (9/16/2010)
CirquedeSQLeil (9/16/2010)
In addition to what Craig has listed, there are the DBA's that must fill all of the roles listed by Craig. Sometimes, there is just no way around having to take care of all of the dev stuff, the architect stuff, prod maintenance and the warehouse.You're correct as always, I should have added the last, unofficial title: Dude in corner talking to himself pulling his own hair out while waving a chicken at the server hoping it stays up just one more day so he can finish those other 5 projects before swapping the raid out.
[Double checks his bald spots and makes sure his chicken is still in place.]
No idea what you're talkin' about there, tho'... really. 😉
The SQL Server Handiman, whatever you need, I'm there for... but please, only 90 hours a week? I'd like to sleep on Sunday. You do end up with one of the strangest SQL educations in that job, though. Kinda spastic and swiss-cheesish, however, without a good mentor... which might explain a lot. 😉
Nice summation.
I need to get me that chicken. I'll bypass the rubber chicken and go for the live chicken. That should be symbolic enough of the live servers err prod servers.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
September 16, 2010 at 11:14 am
Ali Tailor (9/16/2010)
Thanks Craig Farrell and All Others, its enough to me, to get an idea of DBA lines.thanks
You're welcome.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply