SQL Server Interview Questions 1
SQL Server Interview Questions 1
I ran across this and thought it would be helpful for those of you looking for a DBA
job - Original article from http://vyaskn.tripod.com/iq.htm
Questions are categorized under the following sections, for your convenience:
What is bit datatype and what's the information that can be stored inside a bit
column?
Bit datatype is used to store boolean information like 1 or 0 (true or false). Untill SQL
Server 6.5 bit datatype could hold either a 1 or 0 and there was no support for NULL.
But from SQL Server 7.0 onwards, bit datatype can represent a third state, which is
NULL.
A key formed by combining at least two or more columns is called composite key.
What type of Index will get created after executing the above statement?
Non-clustered index. Important thing to note: By default a clustered index gets
created on the primary key, unless specified otherwise.
What's the difference between DELETE TABLE and TRUNCATE TABLE commands?
DELETE TABLE is a logged operation, so the deletion of each row gets logged in the
transaction log, which makes it slow. TRUNCATE TABLE also deletes all the rows in a
table, but it won't log the deletion of each row, instead it logs the deallocation of the
data pages of the table, which makes it faster. Of course, TRUNCATE TABLE can be
rolled back.
What are the new features introduced in SQL Server 2000 (or the latest release of
SQL Server at the time of your interview)? What changed between the previous
version of SQL Server and the current version?
This question is generally asked to see how current is your knowledge. Generally
there is a section in the beginning of the books online titled "What's New", which has
all such information. Of course, reading just that is not enough, you should have
tried those things to better answer the questions. Also check out the section titled
"Backward Compatibility" in books online which talks about the changes that have
taken place in the new version.
Types of constraints: NOT NULL, CHECK, UNIQUE, PRIMARY KEY, FOREIGN KEY
For an explanation of these constraints see books online for the pages titled:
"Constraints" and "CREATE TABLE", "ALTER TABLE"
Whar is an index? What are the types of indexes? How many clustered indexes can be
created on a table? I create a separate index on each column of a table. what are the
advantages and disadvantages of this approach?
Indexes in SQL Server are similar to the indexes in books. They help SQL Server
retrieve the data quicker.
Indexes are of two types. Clustered indexes and non-clustered indexes. When you
create a clustered index on a table, all the rows in the table are stored in the order of
the clustered index key. So, there can be only one clustered index per table. Non-
clustered indexes have their own storage separate from the table data storage. Non-
clustered indexes are stored as B-tree structures (so do clustered indexes), with the
leaf level nodes having the index key and it's row locater. The row located could be
the RID or the Clustered index key, depending up on the absence or presence of
clustered index on the table.
If you create an index on each column of a table, it improves the query performance,
as the query optimizer can choose from all the existing indexes to come up with an
efficient execution plan. At the same time, data modification operations (such as
INSERT, UPDATE, DELETE) will become slow, as every time data changes in the table,
all the indexes need to be updated. Another disadvantage is that, indexes need disk
space, the more indexes you have, more disk space is used.
What are the steps you will take to improve performance of a poor performing query?
This is a very open ended question and there could be a lot of reasons behind the
poor performance of a query. But some general issues that you could talk about
would be: No indexes, table scans, missing or out of date statistics, blocking, excess
recompilations of stored procedures, procedures and triggers without SET NOCOUNT
ON, poorly written query with unnecessarily complicated joins, too much
normalization, excess usage of cursors and temporary tables.
Some of the tools/ways that help you troubleshooting performance problems are:
SET SHOWPLAN_ALL ON, SET SHOWPLAN_TEXT ON, SET STATISTICS IO ON, SQL
Server Profiler, Windows NT /2000 Performance monitor, Graphical execution plan in
Query Analyzer.
Download the white paper on performance tuning SQL Server from Microsoft web
site. Don't forget to check out sql-server-performance.com
What are the steps you will take, if you are tasked with securing an SQL Server?
Again this is another open ended question. Here are some things you could talk
about: Preferring NT authentication, using server, databse and application roles to
control access to the data, securing the physical database files using NTFS
permissions, using an unguessable SA password, restricting physical access to the
SQL Server, renaming the Administrator account on the SQL Server computer,
disabling the Guest account, enabling auditing, using multiprotocol encryption,
setting up SSL, setting up firewalls, isolating SQL Server from the web server etc.
Read the white paper on SQL Server security from Microsoft website. Also check out
My SQL Server security best practices
What is a deadlock and what is a live lock? How will you go about resolving
deadlocks?
Deadlock is a situation when two processes, each having a lock on one piece of data,
attempt to acquire a lock on the other's piece. Each process would wait indefinitely
for the other to release the lock, unless one of the user processes is terminated. SQL
Server detects deadlocks and terminates one user's process.
A livelock is one, where a request for an exclusive lock is repeatedly denied because
a series of overlapping shared locks keeps interfering. SQL Server detects the
situation after four denials and refuses further shared locks. A livelock also occurs
when read transactions monopolize a table or page, forcing a write transaction to
wait indefinitely.
Read up the following topics in SQL Server books online: Understanding and avoiding
blocking, Coding efficient transactions.
How to restart SQL Server in single user mode? How to start SQL Server in minimal
configuration mode?
SQL Server can be started from command line, using the SQLSERVR.EXE. This EXE
has some very important parameters with which a DBA should be familiar with. -m is
used for starting SQL Server in single user mode and -f is used to start the SQL
Server in minimal confuguration mode. Check out SQL Server books online for more
parameters and their explanations.
As a part of your job, what are the DBCC commands that you commonly use for
database maintenance?
DBCC CHECKDB, DBCC CHECKTABLE, DBCC CHECKCATALOG, DBCC CHECKALLOC,
DBCC SHOWCONTIG, DBCC SHRINKDATABASE, DBCC SHRINKFILE etc. But there are
a whole load of DBCC commands which are very useful for DBAs. Check out SQL
Server books online for more information.
What are statistics, under what circumstances they go out of date, how do you
update them?
Statistics determine the selectivity of the indexes. If an indexed column has unique
values then the selectivity of that index is more, as opposed to an index with non-
unique values. Query optimizer uses these indexes in determining whether to choose
an index or not while executing a query.
Look up SQL Server books online for the following commands: UPDATE STATISTICS,
STATS_DATE, DBCC SHOW_STATISTICS, CREATE STATISTICS, DROP STATISTICS,
sp_autostats, sp_createstats, sp_updatestats
What are the different ways of moving data/databases between servers and
databases in SQL Server?
There are lots of options available, you have to choose your option depending upon
your requirements. Some of the options you have are: BACKUP/RESTORE, dettaching
and attaching databases, replication, DTS, BCP, logshipping, INSERT...SELECT,
SELECT...INTO, creating INSERT scripts to generate data.
What is database replicaion? What are the different types of replication you can set
up in SQL Server?
Replication is the process of copying/moving data between databases on the same or
different servers. SQL Server supports the following types of replication scenarios:
• Snapshot replication
• Transactional replication (with immediate updating subscribers, with queued
updating subscribers)
• Merge replication
See SQL Server books online for indepth coverage on replication. Be prepared to
explain how different replication agents function, what are the main system tables
used in replication etc.
How to determine the service pack currently installed on SQL Server?
The global variable @@Version stores the build number of the sqlservr.exe, which is
used to determine the service pack installed. To know more about this process visit
SQL Server service packs and versions.
What are cursors? Explain different types of cursors. What are the disadvantages of
cursors? How can you avoid cursors?
Cursors allow row-by-row prcessing of the resultsets.
Types of cursors: Static, Dynamic, Forward-only, Keyset-driven. See books online for
more information.
Disadvantages of cursors: Each time you fetch a row from the cursor, it results in a
network roundtrip, where as a normal SELECT query makes only one rowundtrip,
however large the resultset is. Cursors are also costly because they require more
resources and temporary storage (results in more IO operations). Furthere, there are
restrictions on the SELECT statements that can be used with some types of cursors.
Most of the times, set based operations can be used instead of cursors. Here is an
example:
If you have to give a flat hike to your employees using the following criteria:
In this situation many developers tend to use a cursor, determine each employee's
salary and update his salary according to the above formula. But the same can be
achieved by multiple update statements or can be combined in a single UPDATE
statement as shown below:
Another situation in which developers tend to use cursors: You need to call a stored
procedure when a column in a particular row meets certain condition. You don't have
to use cursors for this. This can be achieved using WHILE loop, as long as there is a
unique key to identify each row. For examples of using WHILE loop for row by row
processing, check out the 'My code library' section of my site or search for WHILE.
Write down the general syntax for a SELECT statements covering all the options.
Here's the basic syntax: (Also checkout SELECT in books online for advanced
syntax).
SELECT select_list
[INTO new_table_]
FROM table_source
[WHERE search_condition]
[GROUP BY group_by_expression]
[HAVING search_condition]
[ORDER BY order_expression [ASC | DESC] ]
Types of joins: INNER JOINs, OUTER JOINs, CROSS JOINs. OUTER JOINs are further
classified as LEFT OUTER JOINS, RIGHT OUTER JOINS and FULL OUTER JOINS.
For more information see pages from books online titled: "Join Fundamentals" and
"Using Joins".
What is an extended stored procedure? Can you instantiate a COM object by using T-
SQL?
An extended stored procedure is a function within a DLL (written in a programming
language like C, C++ using Open Data Services (ODS) API) that can be called from
T-SQL, just the way we call normal stored procedures using the EXEC statement. See
books online to learn how to create extended stored procedures and how to add
them to SQL Server.
Yes, you can instantiate a COM (written in languages like VB, VC++) object from T-
SQL by using sp_OACreate stored procedure. Also see books online for
sp_OAMethod, sp_OAGetProperty, sp_OASetProperty, sp_OADestroy. For an example
of creating a COM object in VB and calling it from T-SQL, see 'My code library' section
of this site.
What is the system function to get the current user's user id?
USER_ID(). Also check out other system functions like USER_NAME(),
SYSTEM_USER, SESSION_USER, CURRENT_USER, USER, SUSER_SID(),
HOST_NAME().
What are triggers? How many triggers you can have on a table? How to invoke a
trigger on demand?
Triggers are special kind of stored procedures that get executed automatically when
an INSERT, UPDATE or DELETE operation takes place on a table.
In SQL Server 6.5 you could define only 3 triggers per table, one for INSERT, one for
UPDATE and one for DELETE. From SQL Server 7.0 onwards, this restriction is gone,
and you could create multiple triggers per each action. But in 7.0 there's no way to
control the order in which the triggers fire. In SQL Server 2000 you could specify
which trigger fires first or fires last using sp_settriggerorder
Triggers can't be invoked on demand. They get triggered only when an associated
action (INSERT, UPDATE, DELETE) happens on the table on which they are defined.
Triggers are generally used to implement business rules, auditing. Triggers can also
be used to extend the referential integrity checks, but wherever possible, use
constraints for this purpose, instead of triggers, as constraints are much faster.
Till SQL Server 7.0, triggers fire only after the data modification operation happens.
So in a way, they are called post triggers. But in SQL Server 2000 you could create
pre triggers also. Search SQL Server 2000 books online for INSTEAD OF triggers.
Also check out books online for 'inserted table', 'deleted table' and
COLUMNS_UPDATED()
There is a trigger defined for INSERT operations on a table, in an OLTP system. The
trigger is written to instantiate a COM object and pass the newly insterted rows to it
for some custom processing. What do you think of this implementation? Can this be
implemented better?
Instantiating COM objects is a time consuming process and since you are doing it
from within a trigger, it slows down the data insertion process. Same is the case with
sending emails from triggers. This scenario can be better implemented by logging all
the necessary data into a separate table, and have a job which periodically checks
this table and does the needful.
Here's an advanced query using a LEFT OUTER JOIN that even returns the employees
without managers (super bosses)