January 19, 2011 at 11:45 am
Craig Farrell (1/19/2011)
Hm, interesting find, Ninja.There are a number of concerns, from my perspective, with that posting. For reference I'll post it here with notes:
Disclaimer: All quoted material being used for reference here comes from the link http://jobs.sqlservercentral.com/job/database-administrator-developer-chicago-il-west-loop-iclops-f1a5482dce/?d=1&source=site_search_featured. It is used without permission and I have no direct professional association with either SSC nor ICLOPS.
Alright, the Overview is nice, but it's aimed at the wrong target.
Reading through this job description is enough work for 3 unique level II employees. Good luck to this company unless they're offering god salaries.
Wow I didn,t expect you to pick out so much stuff in it... I gotta go read that ref now.
Thanks a mil!
January 19, 2011 at 12:22 pm
Craig Farrell (1/19/2011)
Hm, interesting find, Ninja.There are a number of concerns, from my perspective, with that posting.
In summary, and with additional comments based on recent job adverts I've seen..
Don't ask for the kitchen sink. You are NOT going to find a SQL DBA with 8 years admin experience who can develop applications, write SSIS, develop reports, architect systems and manage a team (well, you might, but you wouldn't be able to afford them)
Target your job requirements and don't be greedy. Think realistically about what kind of skills people are going to have.
I recently helped tidy up a job advert into something reasonable. It started out asking for someone with the following skill ratings (out of 5)
VB 6 (4)
VB.net (4)
C# (4)
SQL (4)
Biztalk (3)
Windows Server 2008 (4)
SSRS (3)
SSIS (3)
I started out by asking the developer who put this together how many of those requirements he fulfilled. It was about half. An hour or so later it was actually a realistic set of required and preferred skills.
Worth a read.
http://thomaslarock.com/2010/09/a-better-dba-job-description-for-everyone/
In short, don't ask for a combination of skills that no one could possibly have then complaint that there are no SQL experts around. There are, we're just smart enough not to apply for jobs that look like they'll have us working 80+ hours a week for far too little.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 19, 2011 at 12:27 pm
Ninja's_RGR'us (1/19/2011)
Wow I didn,t expect you to pick out so much stuff in it... I gotta go read that ref now.Thanks a mil!
Yeah, that's a disturbing job requirement. Now and then one of my consulting firms will run a job requirement past me, asking me what level of technician they think they'll need to successfully fill that position. As a courtesy I'll usually help them out within reason.
In this case, I would recommend they go to microsoft.com, look under the MCM list, and start making phone calls directly. It's not a matter of the skills they need, it's the volume of them that will require mastery (not competence) to sucessfully perform within a reasonable time frame. Mere competence would be the three Level II's to make up for the single master. I personally don't have enough mastery to even attempt this, especially in the BI, SSRS, and SSAS arenas. Also, the reverse engineering work, while I find incredibly fun and interesting, is a heavily focused task that requires a lot of concentration and research time.
It's far too heavy a task to usually do other than alongside backing up the regular DBA teams during crunch times. It's more data analyst and architect than anything else, because you have to know the target system inside and out before you can figure out what you want from the source.
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
January 19, 2011 at 12:34 pm
GilaMonster (1/19/2011)
Target your job requirements and don't be greedy. Think realistically about what kind of skills people are going to have.Worth a read.
http://thomaslarock.com/2010/09/a-better-dba-job-description-for-everyone/
I've seen that link before. I think it's actually an inspiration to one of the articles I'm slowly writing, and more than likely I think you posted it. 😀 It's a very good read, and I recommend anyone following along on this thread to take Gail's advice and take a look at it.
In short, don't ask for a combination of skills that no one could possibly have then complaint that there are no SQL experts around. There are, we're just smart enough not to apply for jobs that look like they'll have us working 80+ hours a week for far too little.
This. It's blunt, but true. Put the offer up front, let us know you're serious about paying for that insane skillset, with a real number. A number that shows that you're trying to combine 3 other people's salaries together to get that one person.
Everyone else screws around with us when we can do it. We don't trust any of 'em anymore.
Paraphrased conversation I once had:
Job: We need this god, can you do it?
Me: Yes. Here's all your proof.
Job: Great, wow, you can. Alright, 70k/year
Me: Seriously? This is two jobs in one, with on call and weekend deployment. 150k.
Job: I'm sorry, but 75k is the most we can offer. You'd make more than your manager otherwise.
Me: Then let him manage two people worth that price. Thank you for your time.
Job: ... ... *door closes* Oh, crap.
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
January 19, 2011 at 12:36 pm
Doug Lane (1/19/2011)
Have you tried announcing it at a local users group meeting? If I needed to hire someone or was looking for a job myself, I'd be sure to mention it there.
Ditto. We always have recruiters show up at our local users group.
Also, if you're talking to computer contracting agencies that are referring you to Monster and Dice, it may be time to find other agencies. Tek Systems, Modis, Robert Half (the only three I know for sure are national) tend to find people for companies directly, not force everyone to go through employment sites. Check out the temporary employment agency section of your yellow pages and look at the first that offer recruiting services for IT people. They might be able to help you better.
January 19, 2011 at 12:40 pm
Brandie Tarvin (1/19/2011)
Also, if you're talking to computer contracting agencies that are referring you to Monster and Dice, it may be time to find other agencies. Tek Systems, Modis, Robert Half (the only three I know for sure are national) tend to find people for companies directly, not force everyone to go through employment sites. Check out the temporary employment agency section of your yellow pages and look at the first that offer recruiting services for IT people. They might be able to help you better.
Monster and Dice just require some sifting. But I agree, the agencies should do that.
Tek Systems is solid, but they have a LOT of consultant recruiter churn. It can be hard for the consultant side to keep an ongoing dialogue with them, at least locally.
Robert Half are painful to work through, consultant wise. They actively market their consultants. This is a good thing, until you realize the double submittal to a final client is the death of any attempt you might have to be employed there. Thus, you're either locked into Robert Half, or you're the last person they contact when the rest of their consultant pool doesn't measure up to the position, because you keep them from actively marketing you without consulting you first.
I'm afraid I can't recommend any Chicago based firms, I haven't done any work through there.
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
January 19, 2011 at 12:41 pm
Craig Farrell (1/19/2011)
In this case, I would recommend they go to microsoft.com, look under the MCM list, and start making phone calls directly. It's not a matter of the skills they need, it's the volume of them that will require mastery (not competence) to sucessfully perform within a reasonable time frame.
Agreed. I could do all of the technical requirements in that job offer, though I have no experience in healthcare (one of the few industries I haven't worked in) but there is no way I would even consider applying for that job (if I lived in Chicago, which I don't)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 19, 2011 at 12:46 pm
Looking over the job description, it definitely sounds like a "One Stop Shop" type of job where there will be maybe one or two DBAs tasked with doing everything.
January 19, 2011 at 12:50 pm
I've heard both good and bad things about both Tek and RH. Even worked for RH for two contracts before I found my current full time position. As in all things, it depends on who you're working with as to whether they're good for your career or bad for your career.
January 19, 2011 at 1:10 pm
Brandie Tarvin (1/19/2011)
I've heard both good and bad things about both Tek and RH. Even worked for RH for two contracts before I found my current full time position. As in all things, it depends on who you're working with as to whether they're good for your career or bad for your career.
'eh, my only true complaint about Tek is usually they're about 10% under the rest of the market if they're marketing the same position. They do get some exclusives though so I don't tend to write them off. It's just the consultant relationship I usually hold in higher regard... they're my "in", so to speak, with the final client. Remarketing myself constantly gets annoying.
RH isn't bad per-se. It's just that I had established relationships elsewhere so I didn't want them haphazardly throwing my resume all over the place. I never did end up working with them so that was the extent of my involvement, besides doing some technical testing with them.
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
January 19, 2011 at 1:24 pm
Wow, flurry of info, thanks.
First, the job descriptions posted were NOT for my job. I was not trying to turn this into a "anyone want a job", i was really looking for insight, and I have received a lot.
I was going to point to our Dice posting, but I do not see it. My guess is it expired, we have a posting out there for an infrastructure manager, but (yikes) it shows us in Hillside not Oak Brook, so someone is not keeping updated right.
Anyway... do I gather it is OK to post one here?
After seeing the other one dissected, I should run and hide perhaps, but you don't learn if you do not take a shot so here goes, for brevity the intro and job description part not the boilerplate (and apologies for the format, did not take time to pretty up).
[font="Arial Narrow"]Responsible for all physical and some logical administration of Microsoft SQL Server databases, this position will also be a backup DBA for i5/OS DB2/UDB on the IBM System i (AS/400). Both environments involve multi-terabyte databases, and this highly technical position will manage their performance and availability while also coordinating projects with development groups as well as packaged software vendors, advising on schema design for both OLTP and OLAP systems. Administer database object enhancements using internal change control procedures. The chosen candidate must be a team player, be a self-starter and possess an eagerness to learn and adapt in a diverse environment. other analysts and programmers. This position requires demonstrated analytical skills, and excellent verbal and written communications in English.
1.Install, configure and administer database software in production and development environments.
2.Plan for and when needed execute high availability and disaster recovery configurations and procedures.
3.Assume primary responsibility for physical monitoring, performance tuning, and work with the development groups to improve logical tuning. Prepare capacity plans for future growth and manage to budget and workload.
4.Document database system configurations.
5.Work with project teams to analyze user needs and develop comprehensive project plans.
6.In conjunction with the development groups, model data, design logical and physical databases, review database design changes and assess impact of changes.
7.Establish and administer database security.
8.Perform validity and integrity checks, and work with developers to ensure data quality and integrity throughout the enterprise.
9.Design, implement and test database backup and recovery procedures.
10.Design, code, test, implement, document and maintain database applications.
11.Evaluate, recommend, install and configure packaged application software that will enhance the database environments.
12.Perform project management duties for small to large database projects.
13.Transfer knowledge to other analysts and programmers to promote professional growth within the department.
14.Work with the technical experts within vendor organizations to resolve problems as well as propose new, or changes to existing, database systems.
15.Develop and implement database change management procedures consistent with overall development and production needs.
16.Configure ETL and database linkages between heterogeneous database environments.
[/font]
Comments, in retrospect -- the iSeries DB2 aspect is not a deal killer, though we would like someone flexible enough to learn that. We would not need them to know DB2 as they come into the door.
The bigger issue -- which again in retrospect is not reflected well here -- is that we are going to have transactional databases in the 1-2 TB range, and BI related ones in the several TB range, with a mixture of heavy duty transaction and ad hoc workloads.
Are we dreaming to find this in one body?
To other comments -- no, I wasn't planing to pay $75k. And no I wasn't planning to pay $250k either.
And fundamentally we need someone who understands what they do. So many DBA's know what to do, but not why. And so they do not know whether what they are doing really applies -- just it said "this is best practice". To handle our data volume and business we need to be creative at times, and I want someone who can keep up with creative developers, and have at least sometimes will say "Microsoft says do X, but in this case I think Y is better and here is why".
I cannot tell you the number of times I have butted heads with a DBA that went like "you need to do X". I do not want to do X, I need an alternative. "But you need to do X". Why? "Because it is the best practice". But here is the problem I am trying to solve, and X does not solve it -- give me an alternative. "You need to do X". Lather, rinse, repeat.
Fundamentally I need someone who will tell me why I need to do X, help me find an alternative if X does not work based on science and research and facts, and generally speaking knows what they are talking about, not just have a good memory for Microsoft blog postings and white papers (though having that is nice also).
FWIW. And really -- thanks for all this feedback.
PS. If I seem a bit disconnected from the search, the position does not report directly to me, so the hiring manager and the recruiting firm hopefully already know where the job is posted. I'm just seeking out some insight given how long it has taken.
January 19, 2011 at 1:43 pm
You asked. I'll try and be gentle.
Ferguson (1/19/2011)
Responsible for all physical and some logical administration of Microsoft SQL Server databases, this position will also be a backup DBA for i5/OS DB2/UDB on the IBM System i (AS/400). So we're looking for a DBA, an administrator. Fine so far Both environments involve multi-terabyte databases, and this highly technical position will manage their performance and availability while also coordinating projects with development groups as well as packaged software vendors, advising on schema design for both OLTP and OLAP systems. And a bit of database design/database architecture Administer database object enhancements using internal change control procedures. The chosen candidate must be a team player, be a self-starter and possess an eagerness to learn and adapt in a diverse environment. other analysts and programmers. This position requires demonstrated analytical skills, and excellent verbal and written communications in English. Blah, blah, blah1.Install, configure and administer database software in production and development environments. Standard DBA stuff
2.Plan for and when needed execute high availability and disaster recovery configurations and procedures. Standard DBA stuff, going to be a challenge with multy TB, but that's the fun part
3.Assume primary responsibility for physical monitoring, performance tuning, and work with the development groups to improve logical tuning. Prepare capacity plans for future growth and manage to budget and workload. From experience, this could easily be a full time job by itself. It was when I worked at the bank on a 1 TB database
4.Document database system configurations.
5.Work with project teams to analyze user needs and develop comprehensive project plans. Project management? Business Analysis? I thought this was a DBA position.
6.In conjunction with the development groups, model data, design logical and physical databases, review database design changes and assess impact of changes. Database architect, database developer
7.Establish and administer database security. Standard DBA work, maybe. Some large systems have separate security administrators
8.Perform validity and integrity checks, and work with developers to ensure data quality and integrity throughout the enterprise. Vague. Dunno what this entails
9.Design, implement and test database backup and recovery procedures. Standard DBA work. No probems
10.Design, code, test, implement, document and maintain database applications. This could easily be a full time development job and a full time maintenance job
11.Evaluate, recommend, install and configure packaged application software that will enhance the database environments.
12.Perform project management duties for small to large database projects. Project management again. Find me a DBA who's a competent project manager as well. I'll wait.
13.Transfer knowledge to other analysts and programmers to promote professional growth within the department.
14.Work with the technical experts within vendor organizations to resolve problems as well as propose new, or changes to existing, database systems.
15.Develop and implement database change management procedures consistent with overall development and production needs. This is a development/development management/change control management position. Depending on size and audit requirements this could also be a full time job.
16.Configure ETL and database linkages between heterogeneous database environments. And now SSIS as well.
So in summary you need:
A database administrator who can monitor and tune a multi TB database while doing all DBA duties including but not limited to testing backups, planning and implementing HA and security, while designing databases, developing other applications, testing, implementing, maintaining said applications and who does business analysis and project management somewhere between 2am and 4am on a sunday morning for yet more applications and manages change control for the environment on the sunday afternoon.
Oh, and has to find some time to train and document as well. Maybe tuesday 1am
Have I about got that right? 😉
Are we dreaming to find this in one body?
Yes.
Looks to me like there are at least 3 jobs there.
1) Hotshot DBA, deep technical skills.
2) Database developer/architect/app developer
3) Business analyst/project manager
The performance monitoring/tuning would be spread between 1 and 2. 3 might be able to do change control as well, maybe.
If this is a company is subject to the SOX audit requirements, the developer, the administrator and the change control manager CANNOT be the same person. Separation of responsibilities.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 19, 2011 at 1:54 pm
GilaMonster (1/19/2011)
You asked. I'll try and be gentle.So in summary you need:
A database administrator who can monitor and tune a multi TB database while doing all DBA duties including but not limited to testing backups, planning and implementing HA and security, while designing databases, developing other applications, testing, implementing, maintaining said applications and who does business analysis and project management somewhere between 2am and 4am on a sunday morning for yet more applications and manages change control for the environment on the sunday afternoon.
Oh, and has to find some time to train and document as well. Maybe tuesday 1am
Have I about got that right? 😉
Are we dreaming to find this in one body?
Yes.
Thank you. Very helpful.
Project management -- good issue, but I was not intending to imply a general project manager. More specific example -- I want a project, early in this person's visit, to review ever single SQL instance they can find, and make sure it is (a) in use, (b) being backed up, (c) is it a candidate for consolidation to a better home, etc. I'd like someone who can understand that, and then track it, including when they get feedback from the ops group, etc. I.e. they need to not require a babysitter. Maybe the term was bad.
Analysis and user interaction -- fair point, but let me give an example from literally today. The users want to extend dramatically how much data they retain in one specific database. Doing it some ways may affect performance. Doing it others may affect applications. It may affect data integrity.
This person needs to be a player in these conversations -- not someone who is played.
>>>You edited after I posted. We are not SOX, we are private. I have two dedicated internal Business Analysis positions, several outsourced, and one dedicated project manager position, as well as several managers who are project managers. But I take to heart that maybe the mixture of physical administration and development input really is asking too much in one body.
But again, thanks for the insight. Maybe I am aiming too high. Other opinions?
January 19, 2011 at 1:58 pm
Okay, I'm going to offer my $.02 here, although I'm not as technically experienced as any of the folks who have already posted here, and I'm not qualified for your posting because I don't have experience with databases on that scale. I am however very active in the SQL Server community, so I think I do have some good advice to offer.
As others have said, Monster, DICE, and job boards are all okay for finding people, but the top people aren't looking there because they don't have to. Recruiters and technical placement agencies are okay as well and probably better than the job boards because the good recruiters ARE going to local user groups and making contacts there, thus they may have contacts that will get you a senior person who has the experience you are looking for.
You did ask how we (or those who are really good and I don't necessarily want to be myself in that category) would look if we were unemployed. First off, it isn't likely that anyone really good is unemployed and if they are it won't be for long. Secondly, I would first contact the people I know in the industry to let them know I am looking and exactly what I'm looking for. In my, albiet limited, experience, the best jobs never make it to recruiters or a job board. Odds are the people I know will know of something that I'd be interested in doing.
So my advice, which I think has already been offered by someone else, is to contact the local PASS Chapter (www.sqlpass.org/chapters) and get the position in front of their members. People that are going to chapter meetings on their time are the people you want working for you because they care and they want to learn the why's of things. The best way to get it in front of the members is to get someone to go to the meetings.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
January 19, 2011 at 2:11 pm
Ferguson (1/19/2011)
Wow, flurry of info, thanks.First, the job descriptions posted were NOT for my job. I was not trying to turn this into a "anyone want a job", i was really looking for insight, and I have received a lot.
I was going to point to our Dice posting, but I do not see it. My guess is it expired, we have a posting out there for an infrastructure manager, but (yikes) it shows us in Hillside not Oak Brook, so someone is not keeping updated right.
Anyway... do I gather it is OK to post one here?
Yep, you're in the employment section.
After seeing the other one dissected, I should run and hide perhaps, but you don't learn if you do not take a shot so here goes, for brevity the intro and job description part not the boilerplate (and apologies for the format, did not take time to pretty up).
I'll... ummmm... try to be gentle, after taking into account your other comments below.
Responsible for all physical and some logical administration of Microsoft SQL Server databases, this position will also be a backup DBA for i5/OS DB2/UDB on the IBM System i (AS/400).
This is the first sentence, thus the leadin on most summaries, for your job description. You must be clear you're willing to train someone on DB2. There is no way in heck I could production support DB2, even if I once upon a decade stared at some underlying Paradox structures.
You have lost probably over half of your applicants simply because they didn't get past the summary, and thus didn't click your link. AS400 and SQL Server have significantly parted ways. You will find it more and more difficult, to nearly impossible, to find crossover talent. You will also find it more difficult to find anyone willing to learn a 'turtle'. There is a shrinking market for a DBA in that. It's like finding work as a COBOL programmer now. It's out there, but really... would you go learn it?
You need to split this into two positions, really. Don't ask your SQL expert, if you want an expert, to divide his attention. King of the mountain or the trailguide, take your pick. Both is out of your expected payscale.
Both environments involve multi-terabyte databases, and this highly technical position will manage their performance and availability while also coordinating projects with development groups as well as packaged software vendors, advising on schema design for both OLTP and OLAP systems.
Well stated overview. This will help... if it wasn't for that DB2 thing. Note, I wouldn't even have read this far if I wasn't analyzing this with your explaination.
Administer database object enhancements using internal change control procedures.
First reaction: Oh lord, they specifically mention this in the opening paragraph. They must have some seriously anal change control. I'll be spending a day a week doing ticket documentation.
The chosen candidate must be a team player, be a self-starter and possess an eagerness to learn and adapt in a diverse environment. other analysts and programmers.
Believe it or not, this screw up in the primary paragraph on the 'professional' request will also turn off some folks. It's an obvious typo, but if you didn't care enough about re-reading and refining your request, why should I care enough about making sure I match up to what you've said you needed?
Also, the phrasing here, if my interpretation is accurate, should be "Can work well with multiple teams simultaneously and work with little managerial oversight". Why? Self-starter is overused and trite (it's become a buzzword of it's own, my eyes almost glide over it at this point), and team player usually means just within the DBA team, and taking on other people's work. It's expected, to be sure, but it's one more "Oh, jeez, really?" that you might be turning folks off with.
This position requires demonstrated analytical skills, and excellent verbal and written communications in English.
That'll cure some issues.
1.Install, configure and administer database software in production and development environments.
2.Plan for and when needed execute high availability and disaster recovery configurations and procedures.
3.Assume primary responsibility for physical monitoring, performance tuning, and work with the development groups to improve logical tuning. Prepare capacity plans for future growth and manage to budget and workload.
First two are fine.
#3: This means that you don't HAVE a SQL DBA. There's no monitoring policies in place. What else are they looking for? (In the back of my DB2 guy's head: "Do I know enough SQL Server to pull that off?") Are they hiring me as the Senior SQL DBA? There's no mention of that, and they asked for a team player before. Will they pay me to be a Senior?
4.Document database system configurations.
Yeah yeah, documentation. We all know that's fallen to the wayside for years, and it will for me too as soon as I get busy. Sure sure...
5.Work with project teams to analyze user needs and develop comprehensive project plans.
Apply brakes, right now. You want a DB2 DBA, a SQL Server DBA who's not senior but is acting like one, AND now you want a project manager? We're outta here. You've jumped skillsets.
Yes, DB Architects are usually proficient in creating technical and business specifications, but even they aren't project managers. You've added in a second job here, besides the whole DB2 learning curve.
6.In conjunction with the development groups, model data, design logical and physical databases, review database design changes and assess impact of changes.
Senior level or Expert level peer reviews of coder DB development. Always fun, like trying to clean sludge. But it'll keep my systems clean so I'm happy to do that. Hopefully they'll give me proper priority to actually research what they're doing rather then glance at it and pray it's good.
7.Establish and administer database security.
ESTABLISH?! Great, Dev vs. DBA wars. This'll be fun. Are they SURE this isn't a senior position? (double checks the headings) No? Oh lovely.
8.Perform validity and integrity checks, and work with developers to ensure data quality and integrity throughout the enterprise.
Ah, well, this goes with the code reviews hopefully, and they're not expecting me to be a local, already paid for trainer. There's a lot of work that goes into training presentations and the like. A lot of this will just have to be the hammer of god until THEY'RE trained to understand MY(/Our? It still seems like I'm solo here...) reasons.
9.Design, implement and test database backup and recovery procedures.
DBA task, no worries...
10.Design, code, test, implement, document and maintain database applications.
The hell? That's a DB Dev job, and (looks up) multiple BI systems and a few front end ones. When do I do the rest of this? That's a full time job for a db dev or two in its own right. Nope, I'm outta here (again).
11.Evaluate, recommend, install and configure packaged application software that will enhance the database environments.
Between developer code reviews, training, architecture structures, and documentation... I'll do this when? The evaluation is the problem child, everything else is either automatable through the network team (I hope... gods I hope) or out of my hands after I spend a day writing up the recommendation in Executive Speak.
12.Perform project management duties for small to large database projects.
Well, that's a whole different job. I wonder if they'll require PMI certification. I wonder if they're going to tack on PM pay to my salary.
13.Transfer knowledge to other analysts and programmers to promote professional growth within the department.
Ah, yep. Why can't they just keep these lines together so you can have a better idea? This is also a training position. Once a month brown bags or is this more intense? Will have to interview at the interview on this topic.
14.Work with the technical experts within vendor organizations to resolve problems as well as propose new, or changes to existing, database systems.
Always fun, the vendors just so love someone else mucking with their systems and showing them their mistakes that they just RUN to be cooperative. Ah well, can't hurt to try.
15.Develop and implement database change management procedures consistent with overall development and production needs.
Yeah yeah, follow standards. Didn't they mention that above? Twice now, change management. That must be one heck of a pain in the A$$ papertrail they write.
16.Configure ETL and database linkages between heterogeneous database environments.
AND SSIS development. In my spare time. On Sunday, I guess, about 4-9AM?
Comments, in retrospect -- the iSeries DB2 aspect is not a deal killer, though we would like someone flexible enough to learn that. We would not need them to know DB2 as they come into the door.
It needs to die, or you need to market to DB2 developers who know SQL. It's dying, if not dead. Most new professionals don't know anything about it other than it's an antique that was used before we got real RDBMS.
Oh, yeah, toss the PM components or you're really going to feel the pain.
The bigger issue -- which again in retrospect is not reflected well here -- is that we are going to have transactional databases in the 1-2 TB range, and BI related ones in the several TB range, with a mixture of heavy duty transaction and ad hoc workloads.
Are we dreaming to find this in one body?
In a word: Yes.
To other comments -- no, I wasn't planing to pay $75k. And no I wasn't planning to pay $250k either.
You'll probably be paying a lot more than that. About 4 50-80k positions from what I read here, if the task volume is significant. You need some seriously disparate skillsets that you won't find easily in one body, and that's JUST the SQL Server parts.
And fundamentally we need someone who understands what they do. So many DBA's know what to do, but not why. And so they do not know whether what they are doing really applies -- just it said "this is best practice". To handle our data volume and business we need to be creative at times, and I want someone who can keep up with creative developers, and have at least sometimes will say "Microsoft says do X, but in this case I think Y is better and here is why".
Then you're seriously going to pay, or have bad systems. There are two types of people who understand the engine this well. One *thinks* they do, and they're novices with knowledge. They're going to topple your systems. The other are people (to name very few) like Paul White, Jeff Moden, Gail Shaw, and others. These are people who have done extensive testing and beating on the engine in *particular areas*, spoken directly with microsoft about their findings to further refine the results, and then started writing books.
Which lead directly to those 'best practices'. While they know the alternatives and know when they should be applied, you are still breaking 'best practices' under those circumstances. They've just examined more often when and why you'd do it.
I cannot tell you the number of times I have butted heads with a DBA that went like "you need to do X". I do not want to do X, I need an alternative. "But you need to do X". Why? "Because it is the best practice". But here is the problem I am trying to solve, and X does not solve it -- give me an alternative. "You need to do X". Lather, rinse, repeat.
This is a fundamental problem with some DBAs. It's the nature of the beast, but not all are like that. However, when you start dealing with strange and interesting techniques that are unproven, or go against the grain, that's the standard answer UNLESS your DBA has significant time to research the results of going against best practice on every other database/application on that server.
What I see above, that person's going to be too busy to notice if the sun goes Nova.
Fundamentally I need someone who will tell me why I need to do X, help me find an alternative if X does not work based on science and research and facts, and generally speaking knows what they are talking about, not just have a good memory for Microsoft blog postings and white papers (though having that is nice also).
And thus, you want to find yourself a nice Microsoft MVP who has, and is continued to be given, the time to keep up to date at that level and experiment with new techniques. Something none of them will do considering the task load you're expecting them to take on.
FWIW. And really -- thanks for all this feedback.
PS. If I seem a bit disconnected from the search, the position does not report directly to me, so the hiring manager and the recruiting firm hopefully already know where the job is posted. I'm just seeking out some insight given how long it has taken.
Hopefully that will help give you some insight as to the problems.
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
Viewing 15 posts - 16 through 30 (of 114 total)
You must be logged in to reply to this topic. Login to reply