• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 709
  • Last Modified:

SQL Interview Questions - Need 2 mid, 2 junior

I'm an AD guy and have been interviewing a lot of people that claim to be experts in AD.  I give them the softball question like "what are the FSMO roles".  People bomb out on that and I'm talking for a job paying over 100k.

So I'm trying to figure out what is the similar question for SQL (or a few on the lower level then if someone didn't get it they would pretty much be ruled out)

I saw this page that seemed good  http://blog.sqlauthority.com/2007/04/15/sql-server-interview-questions/

....but from that what should anyone claiming to "know" SQL should know.

Question and Answer would be awesome :)

Thanks

Mike
0
Mike Kline
Asked:
Mike Kline
  • 4
  • 3
  • 2
  • +1
2 Solutions
 
spiderwilk007Commented:
Here is another whole slew of things a DB Admin should know.

http://www.pinaldave.com/sql-download/SQLServer2008InterviewQuestionsAnswers.pdf
0
 
Mike KlineAuthor Commented:
I included that link in my original question :)  Looking for real world guys here :)
0
 
spiderwilk007Commented:
I would be a little gentler on the Junior Admins, but they should know the basics of how to create proceedures, views, and triggers. How to successfully backup, and restore a database. They should know all basic terminology and how to do common SQL scripting. I would ask them about past projects and database designs they have done in the past, have them provide portfolios if possible.
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 
spiderwilk007Commented:
Make up senarios and have them provide SQL to solve the problem or get the desired output.
0
 
Mike KlineAuthor Commented:
I'm looking for junior to mid level questions (just 2 each) that a senior person should know cold.

...so similar to asking "what are FSMO roles" for Active Directory.  People that are junior may not know but I'm getting senior folks missing that.

0
 
Patrick MatthewsCommented:
For your jr guys, show them the xkcd comic "exploits of a mom".

If they can explain why it's funny, continue the interview.  If not, show them the door right away.
0
 
spiderwilk007Commented:
Q: How would you recover the Master Database(in SQL Server) in the event it becomes corrupt?
A: Use the Rebuild Wizard (Rebuildm.exe), located in the Program Files => Microsoft SQL Server80ToolsBINN directory

Q: What is the first line you would use when creating a stored proceedure?
A: CREATE PROCEDURE {Proceedure name} or CREATE PROC {proceedure name}

0
 
sachitjainCommented:
Junior
Q 1. Explain various entities involved in SQL Server security architecture like logins, users, roles, credentials and certificates etc?
Q 2. What is the purpose of various system databases in SQL server?

Medium
Q 1. How would you restrict access of a user to a particular job but not all over a server?
Q 2. It could be any scenario based question based on given Production environment.
0
 
Mike KlineAuthor Commented:
thanks guys,  

@sachitjanin, can you provide answers to those, (not the scenario one)

Thanks

Mike
0
 
sachitjainCommented:
There is no one liner answer to these questions but these links would definitely help you

For Q1
http://www.sqlservercentral.com/articles/Security/sqlserver2005logins/2474/

For Q2
http://www.mssqltips.com/tip.asp?tip=1420

For Q3
Steps to be followed to give access to a user to a particular job but not all over a server:
1.      Create a SQL login.
2.      Create a SQL User (with login created as in step 1) into msdb db and give it access over sp_start_job and sp_stop_job procedures.
3.      Create a credential (with Identity as one windows account that has system level privs)
4.      Create proxy using credential created in step 3.
5.      Add SQL User created in step 2 to principals of proxy created in step 4.
6.      Add proxy created in step 4 to RUN AS in desired job.
7.      Make SQL User created in step 2 as owner of job.
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 4
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now