ASP.NET Question And Answer 5

SQL Server interview questions
A visitor of
M oskalyuk.com/jobs
writes: Here are some SQL Server DBA/Developer
interview questions I faced myself personally and/or heard from people. I will try to
answer these questions briefly here, but be advised that these answers may not be
complete and it will be better for you to go through text books, books online and other
resources on the net.
Before you go fo r the interview, be prepared to explain the database design of one of
your latest projects. Don't be surprised if the interviewer asks you to draw ER diagrams.
W ell, here are some questions for you. Hope this helps you prepare for your interview.
W ish you all the best in your job hunt! Feel free to email me 'interview questions' that
you've faced.
Questions are categorized under the following sections, for your convenience:
1. Database design (8 questions)
2. SQL Server architecture (12 questions)
3. Database administration (13 questions)
4. Database programming (10 questions)
5. Database design
W hat is normalization? Explain different levels of normalization?
ñ
Check out the article Q100139 from Microsoft knowledge base and of
o
course, there's much more information available in the net. It'll be a good
idea to get a hold of any RDBMS fundamentals text book, especially the
one by C. J. Date. Most of the times, it will be okay if you can explain till
third normal form.
W hat is denormalization and when would you go for it?
ñ
As the name indicates, d enormalization is the reverse process of
o
normalization. It's the controlled introduction of redundancy in to the
database design. It helps improve the query performance as the number of
joins could be reduced.
How do you implement one-to-one, on e-to-many and many-to-many relationships
ñ
while designing tables?
One-to-One relationship can be implemented as a single table and rarely
o
as two tables with primary and foreign key relationships. One-to-M any
relationships are implemented by splitting the data into two tables with
primary key and foreign key relationships. M any-to-M any relationships
are implemented using a junction table with the keys from both the tables