RealGM

I was looking for jobs in Florida involving Ticketmaster and the one that popped up was "Database Marketing Manager" for the Orlando Magic.

http://www.nba.com/magic/career_opportu ... -2128.html

I'm graduating from Florida Southern College in Lakeland on Saturday with a Business Administration degree. I just finished a 10-week full time internship where I spent two weeks of it working with Ticketmaster.

Looking at the job qualifications, is it really possible for them to find someone that can fulfill every single one?

QUALIFICATIONS

If you're applying for a position with "Database" in the title and you have no knowledge of SQL, to the point you don't even know what it is...don't bother applying, you're screwed.

Nobody fulfills all of the requirements on a resume, but I'd imagine that knowing SQL is a major key to getting the position.

If you don't know SQL you better be proficient enough with computer programming to pick it up quickly. Depending on how complex of things your working with though SQL can be very difficult.

Do you honestly think you can diagnose problems with a database (a necessary qualification)? How do you speed up a search that sifts through millions of entries in a table? Do you know anything about indexing structures (whether the high level details most people know, or the low level only DBA's typically know: for instance, B+ trees)?

Some of the things on that list, like any resume, are able to be learned on the fly, quickly trained, etc. But, you'll probably need a couple of months to become only somewhat proficient with SQL, depending on how significant the position is with DB related material, it'll take much longer.

SQL isn't that hard to learn. I learned it in 2 weeks. You can teach yourself it in no time. Don't ask me how to do anything with it now. I haven't done any major database work in like 5 years. I'm very rusty with SQL now. I guess when you don't use it you lose it....

Bigmagicfan82 wrote:SQL isn't that hard to learn. I learned it in 2 weeks. You can teach yourself it in no time. Don't ask me how to do anything with it now. I haven't done any major database work in like 5 years. I'm very rusty with SQL now. I guess when you don't use it you lose it....

No, you didn't "learn" it in 2 weeks. You cook booked it 2 weeks.

I know people that do intensive things and need to consult manuals despite years of experience.

Besides, the SQL isn't necessarily the bad part -- he doesn't even know what SQL is, he doesn't know the concepts behind it, and that type of thing. Otherwise, he'd know what it is. Most technical people if they hear "Database" they pretty immediately think "SQL."

I'd love to see someone that doesn't know what SQL is tell me how to diagnose and fix problems with my database; despite SQL likely having nothing to do with anything. This position seems almost like a poor man's DBA position; if you don't know what SQL even is you ain't qualified.

Go ahead and try though, maybe they're being overzealous in their needs (doesn't seem it though, they want 4 years of database experience, you clearly do not have it). If they do need someone to use SQL and diagnose problems with their databases though, and you manage to get a second interview, feel free and let us know. I'll eat my hat.

database programming is not for me.....or any other programming
maybe mhec could take a crack at it?

N4U|Redux wrote:-= original quote snipped =-



No, you didn't "learn" it in 2 weeks. You cook booked it 2 weeks.

I know people that do intensive things and need to consult manuals despite years of experience.

Besides, the SQL isn't necessarily the bad part -- he doesn't even know what SQL is, he doesn't know the concepts behind it, and that type of thing. Otherwise, he'd know what it is. Most technical people if they hear "Database" they pretty immediately think "SQL."

I'd love to see someone that doesn't know what SQL is tell me how to diagnose and fix problems with my database; despite SQL likely having nothing to do with anything. This position seems almost like a poor man's DBA position; if you don't know what SQL even is you ain't qualified.

Go ahead and try though, maybe they're being overzealous in their needs (doesn't seem it though, they want 4 years of database experience, you clearly do not have it). If they do need someone to use SQL and diagnose problems with their databases though, and you manage to get a second interview, feel free and let us know. I'll eat my hat.

N4U. the dream crusher.


who's next?

databases are yucky, and get very complex. You can learn a lot about them relatively quickly, but not enough to fake four years of proficiency. Anyone can learn the simple select, insert, update commands, but when you get into foreign keys, joining and normalizing huge tables to eliminate redundancy, it can be a lot more difficult (and these are still relatively simple examples). Good luck to you. Id never want to be a DBA.

if u get a job with ticketmaster..make a backdoor password to the system to get us realgm fans lowerbowl centercourt seats for $10...

lol

MagicalMan wrote:databases are yucky, and get very complex. You can learn a lot about them relatively quickly, but not enough to fake four years of proficiency. Anyone can learn the simple select, insert, update commands, but when you get into foreign keys, joining and normalizing huge tables to eliminate redundancy, it can be a lot more difficult (and these are still relatively simple examples). Good luck to you. Id never want to be a DBA.

This guy summarizes my points earlier much more concisely.

Nicely put.

Bigmagicfan82 wrote:SQL isn't that hard to learn. I learned it in 2 weeks. You can teach yourself it in no time. Don't ask me how to do anything with it now. I haven't done any major database work in like 5 years. I'm very rusty with SQL now. I guess when you don't use it you lose it....

NotForYou wrote:No, you didn't "learn" it in 2 weeks. You cook booked it 2 weeks.

I tell people it's black magic. We had a cross-server query that was talking an inordinately long amount of time. The query was running from server A and joining (or sub-querying - I forgot now) data from server B. The only change we made was to run the query from server B and it sped up about 500% - and that's not an exageration.

Not4Me wrote:I'd love to see someone that doesn't know what SQL is tell me how to diagnose and fix problems with my database; despite SQL likely having nothing to do with anything. This position seems almost like a poor man's DBA position; if you don't know what SQL even is you ain't qualified.

MS (could be Oracle also, never used it - but I strongly dislike like Larry Ellison for some reason) is to blame with the GUI - Enterprise Manager.

I cut my teeth on Sybase SQL server - which MS partnered with and developed SQLServer from. All isql based - no GUIs.

I still prefer to use Query Analyzer - using dbcc and sp_ commands. Except when there needs to be string of commands to add users, server roles, etc ...

I'm an OG DBA.

lightheaded wrote:maybe mhec could take a crack at it?

Probably could ... it's strange that they list a degree in marketing but also want the tech skills.

Seems like they want a marketing person who is able to pull numbers from a database so they can email, spam, telemarket and snail-mail people.

Kinda of a mix of positions really. I guess they can't afford a true DBA and also get a Marketing person with all the money they are paying Rashard.

MagicalMan wrote:databases are yucky, and get very complex. You can learn a lot about them relatively quickly, but not enough to fake four years of proficiency. Anyone can learn the simple select, insert, update commands, but when you get into foreign keys, joining and normalizing huge tables to eliminate redundancy, it can be a lot more difficult (and these are still relatively simple examples). Good luck to you. Id never want to be a DBA.

What level of normalization are we talking about here?

I enjoy all that stuff you mentioned - as well as coding apps and web slinging.

Jeebus, you're a nerd



/me turns off router, afraid of mhec.

*log off

on topic:

PHYSICAL DEMANDS
None.

Yep, I could apply.

zuppafly wrote:Jeebus, you're a nerd

And proud!!

mhectorgato wrote:-= original quote snipped =-



Probably could ... it's strange that they list a degree in marketing but also want the tech skills.

Seems like they want a marketing person who is able to pull numbers from a database so they can email, spam, telemarket and snail-mail people.

Kinda of a mix of positions really. I guess they can't afford a true DBA and also get a Marketing person with all the money they are paying Rashard.

That is exactly what I am trying to say.

Your typical business major doesn't have specific tech skills like the ones they're asking for, you need training. And people with all those tech skills graduate with some form of technical degree, not a business degree.

This seems like a job that needs two people (or a whole department) to get it done, or the Magic have to be open to training someone on either the business aspect of the job or the technical aspect.

mhectorgato wrote:-= original quote snipped =-



What level of normalization are we talking about here?

I enjoy all that stuff you mentioned - as well as coding apps and web slinging.

Im talking about normalizing a database to eliminate redundant information/fields. Im not going to try an explain it so here you go:

http://en.wikipedia.org/wiki/Database_normalization

mhectorgato wrote:-= original quote snipped =-



Probably could ... it's strange that they list a degree in marketing but also want the tech skills.

Seems like they want a marketing person who is able to pull numbers from a database so they can email, spam, telemarket and snail-mail people.

Kinda of a mix of positions really. I guess they can't afford a true DBA and also get a Marketing person with all the money they are paying Rashard.

that aint how my name is espelled

OG DBA/Nerd wrote:What level of normalization are we talking about here

MagicalMan wrote:Im talking about normalizing a database to eliminate redundant information/fields. Im not going to try an explain it so here you go:

http://en.wikipedia.org/wiki/Database_normalization

There are different forms - as listed by the Wiki document.

First normal form
Second normal form
Third normal form
Boyce-Codd normal form
Fourth normal form
Fifth normal form
Domain/key normal form

Each different level/form has different rules to specify how the data is spliced up.

I used "level" instead of "form", my bad.

BTW - I don't strictly follow the prescribed "forms" when I architect my database/tables.

BTW2 - This goes back to the original response of N4U/Re2: Experience teaches how you to configure/tune/maintain/etc a database. Reading a book and using it for 2 weeks hardly scratches the surface.

It's like saying I read a book on basketball, so I now definitively know how the Magic should run their offense.

(sorry for the multiple edits ...)

ctorres wrote:That is exactly what I am trying to say.

Your typical business major doesn't have specific tech skills like the ones they're asking for, you need training. And people with all those tech skills graduate with some form of technical degree, not a business degree.

This seems like a job that needs two people (or a whole department) to get it done, or the Magic have to be open to training someone on either the business aspect of the job or the technical aspect.

Which is why I wrote:

I guess they can't afford a true DBA and also get a Marketing person with all the money they are paying Rashard.

For it to be a valid thread on RealGM, that has to be brought up somewhere in the thread, or the forum would implode.

If I were you ctorres, I would just try and intern with the Magic. I know, I know, you already have your degree and you want the money, but it's a great foot in the door. It shows that even though you already have your degree, you're humble enough that you know you have a lot to learn and are willing to do anything to get a good job. You have 18 months from your graduation date.

Hey N4U|Redux, do you run websites?