January 19, 2011 at 3:10 pm
Craig Farrell (1/19/2011)
Side note: How does one become a MS SQL MVP? My google-fu is failing miserably.
You get a nice little email from MS on the first day of the quarter saying "Congratulations, you've been awarded MVP for <current year>" 😉 😛
Seriously...
You need to be nominated, then the MVPGA (global admin) review your community contributions to see if they think you make the bar. If they do, you get the email. If they don't, you never know a thing.
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 3:16 pm
GilaMonster (1/19/2011)
Craig Farrell (1/19/2011)
Side note: How does one become a MS SQL MVP? My google-fu is failing miserably.You get a nice little email from MS on the first day of the quarter saying "Congratulations, you've been awarded MVP for <current year>" 😉 😛
Seriously...
You need to be nominated, then the MVPGA (global admin) review your community contributions to see if they think you make the bar. If they do, you get the email. If they don't, you never know a thing.
Ah hah. Well, that makes it a little more interesting. Also explains why I'm not finding much about it. Neat though.
Anyone know what brand of cookies (or cigars) the current MVPGA likes? 😉
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 3:27 pm
Craig Farrell (1/19/2011)
Anyone know what brand of cookies (or cigars) the current MVPGA likes? 😉
Bribing a committee is an expensive proposition. :hehe:
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 3:31 pm
GilaMonster (1/19/2011)
Craig Farrell (1/19/2011)
Anyone know what brand of cookies (or cigars) the current MVPGA likes? 😉Bribing a committee is an expensive proposition. :hehe:
Bribing witnesses can be even more expensive. 😀
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
January 19, 2011 at 3:54 pm
Alvin Ramard (1/19/2011)
GilaMonster (1/19/2011)
Craig Farrell (1/19/2011)
Anyone know what brand of cookies (or cigars) the current MVPGA likes? 😉Bribing a committee is an expensive proposition. :hehe:
Bribing witnesses can be even more expensive. 😀
Bribing the judge is usually the cheapest and most effective option, overall. :Whistling:
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 3:54 pm
This should make a lot of those who help others, know that someone appreciates all the work they do
http://www.sqlservercentral.com/Forums/Topic1050398-391-1.aspx
January 20, 2011 at 5:23 am
Koen (da-zero) (1/19/2011)
WayneS (1/19/2011)
This thread has made me realize that I suck in deciphering job descriptions. Craig, hurry up with your articles - I need the help!!!At my place, job descriptions are awful. They are always looking for some sort of superman, but a cheap one.
I saw a job description once that very specifically asked for 5 years experience in SQL 2005.
That was in May of 2005.
January 20, 2011 at 5:25 am
Brandie Tarvin (1/20/2011)
I saw a job description once that very specifically asked for 5 years experience in SQL 2005.That was in May of 2005.
So they were specifically targetting the SQL Server development team? 🙂
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
January 20, 2011 at 5:40 am
Brandie Tarvin (1/20/2011)
I saw a job description once that very specifically asked for 5 years experience in SQL 2005.That was in May of 2005.
5 years experience on a product that was still in Beta? (it was released Nov 2005) That's extreme.
A job ad I helped fix recently asked for 4 years experience in SQL 2005 and SQL 2008. Now 4 years of SQL 2005 is fine but I don't think I even have 4 years of SQL 2008 experience and I was playing with it from first public CTP. When I pointed that out, the time requirement was suddenly reduced
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 20, 2011 at 5:41 am
Koen (da-zero) (1/20/2011)
Brandie Tarvin (1/20/2011)
I saw a job description once that very specifically asked for 5 years experience in SQL 2005.That was in May of 2005.
So they were specifically targetting the SQL Server development team? 🙂
Oh, it gets better. They also asked for people who knew both SSRS and SQL Reporting Services.
It was obvious to me that the people who wrote that job description didn't have a clue what all the acronyms meant.
January 20, 2011 at 5:44 am
Brandie Tarvin (1/20/2011)
Koen (da-zero) (1/19/2011)
WayneS (1/19/2011)
This thread has made me realize that I suck in deciphering job descriptions. Craig, hurry up with your articles - I need the help!!!At my place, job descriptions are awful. They are always looking for some sort of superman, but a cheap one.
I saw a job description once that very specifically asked for 5 years experience in SQL 2005.
That was in May of 2005.
My favorite was one that wanted 5+ years experience in VB.Net in 2001.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
January 20, 2011 at 5:46 am
Brandie Tarvin (1/20/2011)
Koen (da-zero) (1/20/2011)
Brandie Tarvin (1/20/2011)
I saw a job description once that very specifically asked for 5 years experience in SQL 2005.That was in May of 2005.
So they were specifically targetting the SQL Server development team? 🙂
Oh, it gets better. They also asked for people who knew both SSRS and SQL Reporting Services.
It was obvious to me that the people who wrote that job description didn't have a clue what all the acronyms meant.
I always like interviews where it is clear they just threw in a bunch of buzzwords. You almost never see the requirement of SSIS without SSAS and SSRS. They probably think they always go together. When you're in the interview it is clear that they don't use SSRS and don't know what SSAS is.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
January 20, 2011 at 5:48 am
GilaMonster (1/20/2011)
Brandie Tarvin (1/20/2011)
I saw a job description once that very specifically asked for 5 years experience in SQL 2005.That was in May of 2005.
5 years experience on a product that was still in Beta? (it was released Nov 2005) That's extreme.
That's pretty much what I said when my SO pointed the job description out to me (I was job hunting at the time). I was like "It's not even out yet!" And he replied "Maybe they meant SQL 2000".
Then I noticed the other requirements (SSRS & SQL Reporting Services and lots of other doozies) and decided it really wasn't worth my time to apply.
January 20, 2011 at 5:54 am
Brandie Tarvin (1/20/2011)
GilaMonster (1/20/2011)
Brandie Tarvin (1/20/2011)
I saw a job description once that very specifically asked for 5 years experience in SQL 2005.That was in May of 2005.
5 years experience on a product that was still in Beta? (it was released Nov 2005) That's extreme.
That's pretty much what I said when my SO pointed the job description out to me (I was job hunting at the time). I was like "It's not even out yet!" And he replied "Maybe they meant SQL 2000".
Then I noticed the other requirements (SSRS & SQL Reporting Services and lots of other doozies) and decided it really wasn't worth my time to apply.
I've found that when you get jobs that were advertised like that, you often have free reign for tools used, timelines, proceeses, pretty much everything. They don't know what to use or what to do, so they let you tell them while "managing" you. Essentially you find out what they want as an end result and have pretty open paths to get them there, if you handle it correctly.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
January 20, 2011 at 6:00 am
I was new to SQL Server, having only held two short term contracts before this. I didn't know what to expect and figured 5 years experience put me out of consideration anyway. Fortunately, I found a job right after that which was willing to hire a trainable junior DBA. And I'm still here, going on my sixth year with the company. I love my employer. Stupid things happen from time to time, but the atmosphere and the leadership is fantastic.
I'll keep your comment (about those types of job descriptions) in mind the next time I have to go job hunting, though. That'll would be nice, to be able to dictate the tools and timelines.
Viewing 15 posts - 23,326 through 23,340 (of 66,749 total)
You must be logged in to reply to this topic. Login to reply