Ask Slashdot: Getting Exchange and SQL Experience?

First time accepted submitter william.meaney1 writes "I'm the sole network admin at a 25 person company. I was lucky enough to get the opportunity less than a year after getting a technical degree in IT. I've had some huge opportunities here (for a first time network admin). After my schooling, I went ahead and I'm now CompTIA A+, Network+, and CCNA certified. Now, being hired out of school, I was grateful for the job, and the boss hired me for peanuts (Less than $30,000/year) I've been living at home, using that money for loan payments, car payments, and certification expenses. I've started looking for other work, and I feel more than qualified for most of the requirements I'm seeing. The big hurdle I'm coming across that EVERYONE seems to want is experience with SQL databases, and Microsoft Exchange. I was wondering if anyone had any ideas for getting usable experience on a low budget. I have some SQL experience, I deployed a source control program here that uses a SQL express backend, but what else do you need to know for database maintenance?"

Comments

Just do it

[gewalker]

Install some critical app (without permission if necessary) on your current corp. network that uses SQL server -- Presto, instant experience.

Re:Just do it

[erpbridge]

"I see here on your resume that you have SQL experience. Can you tell me about some of the SQL deployments and experience that you were doing in your last job? How did you integrate that into your business requirements?"

Its exactly THIS sort of question, which I'm getting a bit, which trips people up who self learn. I'm getting it with VMware... I had VMware experience building, maintaining, updating machines... but never anything server side, and never anything on the farm level of things like vMotion. After I was let go at end of contract after 5 years on build team/CMDB remediation team, all the interview screen questions tended to focus toward vmWare and Exchange. So, I went out, got myself a beefy machine, installed vSphere 5.1 on it, and have done quite a few things with it... but that experience means SQUAT when you're sitting in front of a board which includes interviewing manager, vmWare SME, and a couple other general members of the IT team who are trying to probe you for you BUSINESS level experience.

There's a heck of a lot difference between test lab, and business level, and interviewers can ferret that out REAL quick.

Re:Just do it

[pastafazou]

You keep following the path you're on, you're liable to get burned....

Re:Just do it

[DuckDodgers]

I think the ability to learn on your own is itself a skill - and an essential one if you want to be good. Get SQL Server Express. Install it. Then use the official web documentation or a highly rated book on it. Start at page 1 and walk through the features. When it gets to a section on setting up foreign keys, use your SQL Server Express to set up foreign keys. When it describes backups, set up backups.

However, this is only half the work required. If he can't point to work experience with SQL Server, then a lot of potential employers don't care what he claims to know from self-study.

Join MSDN Technet

[David E. Smith]

Nothing beats hands-on experience, so get some on the cheap. Get an MSDN Technet subscription; for $199 a year, you'll get free personal/learning licenses of SQL Server, Exchange, and just about every other big Microsoft program. Play with them. Set them up. Try to break them, then fix them.

Re:Join MSDN Technet

[tekiegreg]

^^^ This

I'd also like to add that if your budget is zero, SQL server express editions exist for free, they have a few restrictions on things such as DB Size, but should suit you well enough.

Re:Join MSDN Technet

[raydobbs]

Sadly, personal experience != 'experience' in the corporate sense. I've had this fight with IT recruiters and headhunters - they want experience in a corporate setting with corporate problems, not 'I dorked with it at home for x months or years'. Of course, people who actually know what the hell they need value ANY experience, so its not a complete waste - just getting to interview with them versus the HR drone can be the biggest problem.

Good advice on TechNet though - helps you get a leg up on new OSes and obscure software without having to buy those licenses separately. BIG COST SAVINGS!

Re:Join MSDN Technet

[jerpyro]

Personal experience can be 'experience' on your resume. What you need to do is to put them as 'personal projects' or 'side projects' instead of listing them as your job functions. Then, they will still trigger the keyword search, and it's enough to justify saying you have 'entry level experience' (which is MUCH better than not listing them at all). Better yet, once you have a little experience with them do a little consulting that makes use of that skill set.

ALWAYS work on your skill set. Don't wait for a position to come along to allow you to do it.

"Just do it"?

[ArcadeMan]

Nike would like to have a word with you.

[OT] A+ = F

[Anonymous Coward]

Offtopic, but I'd drop the A+ certification from your resume. When we get applicants with A+ listed, then we assume that they don't know enough to know that it means nothing and we bin them.

Re:[OT] A+ = F

[alta]

Not sure who's rating this down but I agree with it. A+ screams geeksquad. We look at A+ as people who have low expectations in life. It's a pretty poor way to look at it, but that's life.

Self teaching, followed by volunteer work

[they_call_me_quag]

I see this as a three step process:

(1) Use the other resources mentioned above to teach yourself SQL server and Exchange.

(2) Find a nonprofit agency in your area who needs help with their computing environment. Offer to help them on a volunteer (ie, unpaid) basis. Be sure this help includes working with SQL Server and Exchange. Be picky about this. Do not get involved with an agency where the work will not help you build your practical skill set. Also be sure that there is someone at the nonprofit agency who is willing to act as a reference for you at some point in the future. You don't have to explicitly ask this upfront, just be sure that the senior most person you can find knows enough about who you are to say nice things about you.

(3) Use this real life experience to help you land the next job on your way up the ladder.

(4) Optional: Continue working with the nonprofit agency if it makes you happy.

BTW... you can do steps 1 & 2 in parallel, ie start looking for a nonprofit while you are learning SQL Server and Exchange. Both steps might take a little time.

Start with SQL proper.

[Let's All Be Chinese]

Start at the beginning. Too many SQL users (including developers!) haven't a clue how to properly use it. As a DBA, you'll be called upon to provide that, among other things. So start with the theory and practice of SQL. Especially since it actually is founded upon fairly solid theory, meaning that if you know the theory the practice suddenly becomes a lot smoother. The rest will follow from that.

See db-class.org for a MOOC intro. If you've worked your way through that you'll know where to start looking for learning about the DBA-type things you'll need to do: Schemata, indices, query tuning, and then the subtler tuning like moving tables and indices around on disk or solid state or in-memory or what-have-you. And the basic knowledge will be useful any time a user asks for your DBA-hatted help.

As to exchange, it's crap, and you'll be better off knowing less about its internals. It's hairy and quirky and apt to eat your mail. In fact, it's not even a proper mail server: It's a suitable server for outlook, just as outlook is not a proper email client, but a suitable client to exchange. The combination means a lot of interop trouble that could've easily been avoided.

Since you'll be called upon to make it play ("nicely" is not in the books) with the rest of the world, again, start from principles. Learn how to set up an MTA, know how SMTP and IMAP work. Send yourself an email by telnet. Know what the various headers do. That MTA set up with matching IMAP server, don't have to be exchange at first, in fact it's better not to. Once you know how the rest of the world does it, you can learn how exchange fscks it all up, and how to keep the thing on a leash.

For bonus points, learn how to provide everything that exchange purports to provide ("collaboration" and calendaring and "syncing" and so on, as well as half-assed not-entirely-unlike-email type "messaging") using open-source software. Get that down smoothly (there are several ways and alternatives available these days) and you have another selling point: Providing a better experience with less cost.

That was what you're looking for, right? Points to sell yourself with?

Re:Work for a local IT company

[kullnd]

That's a bit extreme of an example - but yes - you are failing to take into account everything that goes into running these types of operations such as Software Licensing (Which is crazy expensive for their ticketing systems and remote management tools), tools, rent, utilities, insurance (General liability and Errors / Omissions, Bonding (really good idea if you have employees in this type of business), your benefits, your payroll taxes, marketing, the cost of doing sales (i.e. not making money to get money) ... the list goes on. If you think it's such a great deal for the owner, why don't you try it yourself - It's a lot harder to get by than you think.

Re:Work for a local IT company

[kullnd]

Considering I was being paid $20 an hour and when the company I was working for charged $95 an hour. I do believe that there is a problem.

$95/hr is split into:

Your $20/hr + (Plus any benefits, Federal taxes, blah, blah)
Plus the time that someone spent getting that client you just did $95 worth of work for
Plus the money that was spent marketing to get that client you just did $95 worth of work for
Plus the admin time that will be spent billing that client
Plus dealing with the clients that don't pay
Plus office rent, utilities, other office overhead that you probably have no clue about
Plus tools used to perform the work (ticketing system, remote access tools?) . Again, you probably have no clue how much that actually costs
Plus you were paid to drive to that client, and if using your own vehicle should have gotten mileage
In addition to the drive, you are likely not billing 100% of your time anyway - Company still pays you when you are not billable right?

Believe it or not, the Margin on those accounts is not that much. Does it make money? Well I hope so or your company will no longer exist - Does it make someone filthy rich? Probably not.