Need Advice for hiring a SQL Server guru

[Rexolio]

We have a web site that runs from a database backend (SQL Server 7.0). I do most of the frontend work, but don't know what I need to know about SQL Server. My company is wanting to hire someone to go through our database and make sure tables are set up appropriately, i.e. relations, id's, etc., to create stored procedures, compress tables, etc. We're not too concerned about degrees and so forth, but would like to know some basic procedures that a someone should know if we're to consider hiring them. Can anyone help me out with that? We really don't know what to ask and we don't want to sound stupid (of course).
rexolio@bellsouth.net
"I'm not dumb. I just have a command of thoroughly useless information." - Calvin, of Calvin and Hobbes

 

[SQLSister]

One of the questions we ask all our dba and development inteviewees is to describe what a relational database is. You'd be amazed at how many can't answer the question.

Other questions to ask would be:

Describe how to normalize a database and when might you want to denormalize a database?

Describe how you go about determining a backup stategy.

Describe how you manage the permissions in a database.

What steps would you take to find the cause of a databse slowdown?

What steps would you take to improve the performance of a stored procedure?

Get a sample of a stored procedure the person wrote and have them explain every line of the code to you. Again you'd be amazed at the people who either can't find a good sample, bring in one that is very simple or can't actually explain what every line of code does.

Alternatively, give them one of your stored procedures and have them explain it to you.

Ask how they would go about debugging a stored procedure.

What are the considerations in maintaining high availibility of a web site which uses a database backend?

What tasks do you think are important to perform in order to maintain a database?

Get them to explain in detail exactly what tasks they perform in their current job concerning the databases they maintain.

Why would you want to maintain permissions through the use of roles instead of individual permissions?

How would you manage a change to a production database without affecting users?

Oh, you didn't want the answers to these questions did you? By the way, I loved your signature.

 

[Rexolio]

SQL Sister,

AWESOME!!! Thanks for the great info! I appreciate you taking the time to help me out.



Thanks a million!!!
rexolio@bellsouth.net
"I'm not dumb. I just have a command of thoroughly useless information." - Calvin, of Calvin and Hobbes

 

[Rexolio]

BTW, if you WANT to answer them, that's great. But by no means do I expect you to do that if it takes too long. Thanks again!!!!
rexolio@bellsouth.net
"I'm not dumb. I just have a command of thoroughly useless information." - Calvin, of Calvin and Hobbes

 

[SQLSister]

THe answers are left as an exercise for the student!