SQL Server Interview Questions

  • (5.0)
  •   |   4900 Ratings

SQL Server Interview Questions

Last Updated: May 23rd, 2018

If you're looking for SQL Server Interview Questions for Experienced or Freshers, you are at right place. There are lot of opportunities from many reputed companies in the world. According to research, the average salary for SQL Server ranges from approximately $69,674 pa. So, You still have the opportunity to move ahead in your career in SQL Server certification guide. Mindmajix offers Advanced SQL Server Interview Questions & Answers 2018 that helps you in cracking your interview & acquire dream career as SQL Server Developer.

SQL Server Interview Questions & Answers

Q1) What is the Difference between MySql Vs SQL Server Performance?

MySQl Server Vs SQL Server
Function MS SQL Server MySql
Developer Microsoft Oracle
License  Commercial OpenSource
Cloud-based No No
Implementation Language C++ C & C++
XML Support  Yes Yes
Supported Programming Lang It supports C#, PHP, Python, Ruby, R, Visual Basic, Java etc It supports c++, C#, Java, PHP, Perl, Python, Ruby, Tcl, Delphi, D etc
Server-Side Scripting. Net & TransaScripting. Yes, it supports
Concurreny It supports ,yes It supports ,yes
Consistency Concept's It enables immediate consistency It enables immediate consistency
Transaction concepts It supports ACID It supports ACID

Q2) What is normalization? Explain different levels of normalization?

It is the way to eliminate redundant data

  1. Reduces null value
  2. Enables efficient indexing
  3. 1NF – Removes duplicated attributes, Attribute data should be atomic, and attribute should be same kind.
  4. 2NF – Should be in 1NF and each non-key is fully dependent on the primary key.
  5. 3NF – Should be in 2NF and all the non-key attributes which are not dependent on the primary key should be removed. All the attributes which are dependent on the other non-key attributes should also be removed. Normalization is done in OLTP.

Q3) What is denormalization and when would you go for it?

  1. It is the reverse process of normalization.
  2. It increases the query performance by reducing the joins.
  3. It is used for OLAP applications.

Q4) How do you implement one-to-one, one-to-many and many-to-many relationships while designing tables?

  1. One to One –It can be implemented as a single table. Rarely it is implemented in two tables. For each instance in the first entity there is one and only one in the second entity and vice versa.
  2. One to Many –For each instance in the first entity there can be one or more in the second entity. For each instance in the second entity there can be one and only one instance in the first entity.
  3. Many to Many –For each instance in the first entity there can be one or more instance in the second entity and moreover, for each instance in the second entity there can be one or more instance in the first entity.

Q5) Difference between Primary key and Unique key.

Primary Key

  • 1.Enforces uniqueness of the column in a table
  • 2.Default clustered index
  • 3.Does not Allow nulls

Unique Key


  • 1.Enforces uniqueness of the column in a table
  • 2.Default non-clustered index.
  • 3.Allows one null value

Q6) Define following keys:

Candidate key, Alternate key, Composite key.

  • 1.Candidate key –Key which can uniquely identify a row in table.
  • 2.Alternate key –If the table has more than one candidate keys and when one becomes a primary key the rest becomes alternate keys.
  • 3.Composite key –More than one key uniquely identify a row in a table.

Q7) What are defaults? Is there a column to which a default can’t be bound?

1.It is a value that will be used by a column if no value is supplied to that column while inserting data.
2.I can’t be assigned for identity and timestamp values.

Q8) What are user defined data types and when you should go for them?

Lets you extend the base SQL server data types by providing a descriptive name and format to the database.

E.g. Flight_num appears in many tables and all these tables have varchar(8)
Create a user defined data-type

Q9) What is a transaction and what are ACID properties?

A transaction is a logical unit of work in which, all the steps must be performed or none. ACID stands for Atomicity, Consistency, Isolation, and Durability. These are the properties of a transaction.

Q10) What part does database design have to play in the performance of a SQL Server-based application?

It plays a very major part. When building a new system, or adding to an existing system, it is crucial that the design is correct. Ensuring that the correct data is captured and is placed in the appropriate tables, that the right relationships exist between the tables and that data redundancy is eliminated is an ultimate goal when considering performance. Planning a design should be an iterative process, and constantly reviewed as an application is developed. It is rare, although it should be the point that everyone tries to achieve, when the initial design and system goals are not altered, no matter how slightly. Therefore, a designer has to be on top of this and ensure that the design of the database remains efficient..

Learn how to use SQL Server, from beginner basics to advanced techniques, with online video tutorials taught by industry experts. Enroll for Free SQL Server Training Demo!

Q11) What can a developer do during the logical and physical design of a database in order to help ensure that their database and SQL Server-based application will perform well?

A developer must investigate volumes of data (capacity planning), what types of information will be stored, and how that data will be accessed. If you are dealing with an upgrade to an existing system, analyzing the present data and where existing data volumes occur, how that data is accessed and where the current response bottlenecks are occurring, can help you search for problem areas in the design.

A new system would require a thorough investigation of what data will be captured, and looking at volumes of data held in other formats also will aid design. Knowing your data is just as important as knowing the constituents of your data. Also, constantly revisit your design. As your system is built, check relationships, volumes of data, and indexes to ensure that the physical design is still at its optimum. Always be ready to check your system by using tools like the SQL Server Profiler.

Q12) What are the main steps in Data Modeling?

  • 1.Logical – Planning, Analysis and Design
  • 2.Physical – Design, Implementation and Maintenance


Q13) What are cursors? Explain different types of cursors. What are the disadvantages of cursors? How can you avoid cursors?

Cursors allow row-by-row processing of the result sets.

Types of cursors:

Static – Makes a temporary copy of the data and stores in tempdb and any modifications on the base table does not reflected in data returned by fetches made by the cursor.
Dynamic – Reflects all changes in the base table.
Forward-only – specifies that cursor can only fetch sequentially from first to last.
Keyset-driven – Keyset is the set of keys that uniquely identifies a row is built in a tempdb.

Disadvantages of cursors:

Each time you fetch a row from the cursor, it results in a network roundtrip, whereas a normal SELECT query makes only one roundtrip, however large the result set is. Cursors are also costly because they require more resources and temporary storage (results in more IO operations). Further, 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:

Salary between 30000 and 40000 — 5000 hike
Salary between 40000 and 55000 — 7000 hike
Salary between 55000 and 65000 — 9000 hike

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:

UPDATE tbl_emp SET salary =
WHEN salary BETWEEN 30000 AND 40000 THEN salary + 5000
WHEN salary BETWEEN 40000 AND 55000 THEN salary + 7000
WHEN salary BETWEEN 55000 AND 65000 THEN salary + 10000

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.

Q14) Write down the general syntax for a SELECT statement covering all the options.

Here’s the basic syntax: (Also checkout SELECT in books online for advanced syntax).
SELECT select_list
[HDEV:INTO new_table_]
FROM table_source
[HDEV:WHERE search_condition]
[HDEV:GROUP BY group_by_expression]
[HDEV:HAVING search_condition]
[ORDER BY order_expression [ASC | HDEV:DESC] ]

Q15) What is a Join and explain different types of Joins?

Joins are used in queries to explain how different tables are related. Joins also let you select data from a table depending upon data from another table.

Q16) Can you have a nested transaction?


Q17) 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.
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.

Q18) What is the system function to get the current user’s userid?

USER_ID(). Also check out other system functions like USER_NAME(), SYSTEM_USER, SESSION_USER, CURRENT_USER, USER, SUSER_SID(), HOST_NAME().

Q19) 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 – INSTEAD OF triggers.
Virtual tables – Inserted and Deleted form the basis of trigger architecture.

Q20) What is a self join? Explain it with an example.

Self join is just like any other join, except that two instances of the same table will be joined in the query. Here is an example: Employees table which contains rows for normal employees as well as managers. So, to find out the managers of all the employees, you need a self join.

empid int,
mgrid int,
empname char(10)
INSERT emp SELECT 1,2,’Vyas’
INSERT emp SELECT 2,3,’Mohan’
INSERT emp SELECT 4,2,’Shridhar’
INSERT emp SELECT 5,2,’Sourabh’
SELECT t1.empname [HDEV:Employee], t2.empname [HDEV:Manager]
FROM emp t1, emp t2
WHERE t1.mgrid = t2.empid

Here’s an advanced query using a LEFT OUTER JOIN that even returns the employees without managers (super bosses)
SELECT t1.empname [HDEV:Employee], COALESCE(t2.empname, ‘No manager’) [HDEV:Manager]
FROM emp t1
emp t2
t1.mgrid = t2.empid

Explore SQL Server Sample Resumes! Download & Edit, Get Noticed by Top Employers!Download Now!

Q21) Write a SQL Query to find first Week Day of month?


Q22) How to find 6th highest salary from Employee table?

SELECT TOP 1 salary FROM (SELECT DISTINCT TOP 6 salary FROM employee ORDER BY salary DESC) a ORDER BY salary

Q23) How can I enforce to use particular index?

You can use index hint (index=index_name) after the table name. SELECT au_lname FROM authors (index=aunmind)

Q24) What is ORDER BY and how is it different than clustered index?

The ORDER BY clause sorts query results by one or more columns up to 8,060 bytes. This will happen by the time when we retrieve data from database. Clustered indexes will physically sort data, while inserting/updating the table.

Q25) What is the difference between a UNION and a JOIN?

A JOIN selects columns from 2 or more tables. A UNION selects rows.

Q26) What is the Referential Integrity?

Referential integrity refers to the consistency that must be maintained between primary and foreign keys, i.e. every foreign key value must have a corresponding primary key value

Q27) What is the purpose of UPDATE STATISTICS?

It updates information about the distribution of key values for one or more statistics groups (collections) in the specified table or indexed view.

Q28) What is the use of SCOPE_IDENTITY() function?

It returns the most recently created identity value for the tables in the current execution scope.

Q29) What do you consider are the best reasons to use stored procedures in your application instead of passing Transact-SQL code directly to SQL Server?

First and foremost, a stored procedure is a compiled set of code, where passing T-SQL through languages such as VB, Visual FoxPro, etc., means that the set of code needs to be compiled first. Although T-SQL within VB, etc., can be prepared before running, this is still slower than using a stored procedure. Then, of course, there is the security aspect, where, by building a stored procedure, you can place a great deal of security around it. When dealing with sensitive data, you can use an encrypted stored procedure to hide sensitive columns, calculations, and so on. Finally, by using a stored procedure, I feel that transactional processing becomes a great deal easier and, in fact, using nested transactions become more insular and secure. Having to deal with transactions within code that may have front end code, will slow up a transaction and therefore a lock will be held for longer than necessary.

Q30) What are some techniques for writing fast performing stored procedures?

Fast performing stored procedures are like several other areas within T-SQL. Revisiting stored procedures every six months or so, to ensure that they are still running at their optimum performance is essential. However, actual techniques themselves include working with as short a transaction area as possible, as lock contention will certainly impact performance. Recompiling your stored procedures after index additions if you are unable or not wishing to restart SQL Server, will also ensure that a procedure is using the correct index, if that stored procedure is accessing the table which has received the new index. If you have a T-SQL command that joins several tables, and it takes a long time to return a value, first of all check out the indexes. But what you may find tends to help, is to break down the code and try to determine which join it is that is causing the performance problem. Then analyze this specific join and see why it is a problem.
Always check out a stored procedure’s performance as you build it up by using the SHOWPLAN commands.
Also, try to use EXISTS, rather than a JOIN statement. An EXISTS statement will only join on a table until one record is found, rather than joining all the records . Also, try to look at using sub queries when you are trying to find a handful of values in the sub query statement, and there is no key on the column you are looking up on.

Q31) When should SQL Server-based cursors be used, and not be used?

SQL Server cursors are perfect when you want to work one record at a time, rather than taking all the data from a table as a single bulk. However, they should be used with care as they can affect performance, especially when the volume of data increases. From a beginner’s viewpoint, I really do feel that cursors should be avoided every time because if they are badly written, or deal with too much data, they really will impact a system’s performance. There will be times when it is not possible to avoid cursors, and I doubt if many systems exist without them. If you do find you need to use them, try to reduce the number of records to process by using a temporary table first, and then building the cursor from this. The lower the number of records to process, the faster the cursor will finish. Always try to think “out of the envelope”.

Q32) What alternatives do developers have over using SQL Server-based cursors? In other words, how can developers perform the same function as a cursor without using a cursor?

Perhaps one of the performance gains least utilized by developers starting out in SQL Server are temporary tables. For example, using one or more temporary tables to break down a problem in to several areas could allow blocks of data to be processed in their own individual way, and then at the end of the process, the information within the temporary tables merged and applied to the underlying data. The main area of your focus should be, is there an alternative way of doing things? Even if I have to break this down into several chunks of work, can I do this work without using cursors, and so result in faster performance. Another area that you can look at is the use of CASE statements within your query. By using a CASE statement, you can check the value within a column and make decisions and operations based on what you have found. Although you will still be working on a whole set of data, rather than a subset found in a cursor, you can use CASE to leave values, or records as they are, if they do not meet the right criteria. Care should be taken here though, to make sure that by looking at all the data, you will not be creating a large performance impact. Again, look at using a subset of the data by building a temporary table first, and then merging the results in afterwards. However, don’t get caught out with these recommendations and do any of them in every case. Cursors can be faster if you are dealing with small amounts of data. However, what I have found, to be rule number one, is get as little data in to your cursor as is needed.

Q33) If you have no choice but to use a SQL Server-based cursor, what tips do you have in order to optimize them?

Perhaps the best performance gain is when you can create a cursor asynchronously rather than needing the whole population operation to be completed before further processing can continue. Then, by checking specific global variables settings, you can tell when there is no further processing to take place. However, even here, care has to be taken. Asynchronous population should only occur on large record sets rather than those that only deal with a small number of rows. Use the smallest set of data possible. Break out of the cursor loop as soon as you can. If you find that a problem has occurred, or processing has ended before the full cursor has been processed, then exit. If you are using the same cursor more than once in a batch of work, and this could mean within more than one stored procedure, then define the cursor as a global cursor by using the GLOBAL keyword, and not closing or deallocating the cursor until the whole process is finished. A fair amount of time will be saved, as the cursor and the data contained will already be defined, ready for you to use.

Q34) 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 lot of reasons behind the poor performance of a query. But some general issues that you could talk about would be:

  1. No indexes
  2. No Table scans
  3. Missing or out of date statistics
  4. Blocking
  5. Excess recompilations of stored procedures

Q35) What is an ER Diagram?

An ER diagram or Entity-Relationship diagram is a special picture used to represent the requirements and assumptions in a system from a top down perspective. It shows the relations between entities (tables) in a database.

Q36) What is a prime attribute?

A prime attribute is an attribute that is part of a candidate key.

Q37) What are the properties of a transaction?

The ACID properties. Atomicity, Consistency, Isolation, and Durability.

Q38) What is a non-prime attribute?

A non-prime attribute is an attribute that is not a part of a candidate key.

Q39) What is Atomicity?

This means the transaction finish completely, or it will not occur at all.

Q40) What is Consistency?

Consistency means that the transaction will repeat in a predictable way each time it is performed.

Q41) What is Isolation?

The data the transactions are independent of each other. The success of one transaction doesn’t depend on the success of another.

Q42) What is Durability?

Guarantees that the database will keep track of pending changes so that the server will be able to recover if an error occurs.

Q43) What is a DBMS?

A DBMS is a set of software programs used to manage and interact with databases.

Q44) What is a RDBMS?

It is a set of software programs used to interact with and manage relational databases. Relational databases are databases that contain tables.

Q45) What is business intelligence?

Refers to computer-based techniques used in identifying, extracting, and analyzing business data, such as sales revenue by products and/or departments, or by associated costs and incomes.

Q46) What is normalization?

Database normalization is the process of organizing the fields and tables of a relational database to minimize redundancy and dependency.

Q47) What is a relationship?

The way in which two or more concepts/entities are connected, or the state of being connected.

Q48) What are the different types of relationships?

One to one, one to many, many to many, many to fixed cardinality.

Q49) What is the difference between a OLTP and database?

An OLTP is the process of gathering the data from the users, and a database is the initial information.

Q50) What are the different kinds of relationships?

Identifying and non-identifying.

Q51) What is an entity?

Something that exists by itself, although it need not be of material existence.

Q52) What is a conjunction table?

A table that is composed of foreign keys that points to other tables.

Q53) What is a relational attribute?

An attribute that would not exist if it were not for the existence of a relation.

Q54) What are associative entities?

An associative entity is a conceptual concept. An associative entity can be thought of as both an entity and a relationship since it encapsulates properties from both. It is a relationship since it is serving to join two or more entities together, but it is also an entity since it may have its own properties.

Q55) What is the difference between a derived attribute, derivedpersistent attribute, and computed column?

A derived attribute is a attribute that is obtained from the values of other existing columns and does not exist on it’s own. A derived persistent attribute is a derived attribute that is stored. A computed attribute is a attribute that is computed from internal system values.

Q56) What are the types of attributes?
Simple, composite (split into columns), multi-valued (becomes a separate table), derived, computed, derived persistent.

Q57) Is the relationship between a strong and weak entity always identifying?

Yes, this is the requirement.

Q58) Do stand alone tables have cardinality?


Q59) What is a simple key?

It is a key that in composed of one attribute.
Give/ recite the types of UDF functions.
Scalar, In-line, Multi

Q60) Describe what you know about PK, FK, and UK.

Primary keys – Unique clustered index by default, doesn’t accept null values, only one primary key per table.
Foreign Key – References a primary key column. Can have null values. Enforces referential integrity.
Unique key – Can have more than one per table. Can have null values. Cannot have repeating values. Maximum of 999 clustered indexes per table.

Q61) What do you mean by CTEs? How will you use it?

CTEs also known as common table expressions are used to create a temporary table that will only exist for the duration of a query. They are used to create a temporary table whose content you can reference in order to simplify a queries structure.

Q62) What is a sparse column?

It is a column that is optimized for holding null values.

Q63) What would the command: DENY CREATE TABLE TO Peter do?

It wouldn’t allow the user Peter to perform the operation CREATE TABLE regardless of his role.

Q64) What does the command: GRANT SELECT ON project TO Peter do?

It will allow the SELECT operation on the table ‘project’ by Peter.

Q65) What does the command: REVOKE GRANT SELECT ON project TO Peter do?

It will revoke the permission granted on that table to Peter.

Q66) New commands in SQL 2008?

Database encryption, CDCs tables – For on the fly auditing of tables, Merge operation, INSERT INTO – To bulk insert into a table from another table, Hierarchy attributes, Filter indexes, C like operations for numbers, resource management, Intellisense – For making programming easier in SSMS, Execution Plan Freezing – To freeze in place how a query is executed.
What is new in SQL 2008 R2?
PowerPivot, maps, sparklines, data bars, and indicators to depict data.

Q67) What is faster? A table variable or temporary table?

A table variable is faster in most cases since it is held in memory while a temporary table is stored on disk. However, when the table variable’s size exceeds memory size the two table types tend to perform similarly.

Q68) How big is a tinyint, smallint, int, and bigint?

1 byte, 2 bytes, 4 bytes, and 8 bytes.

Q69) What does @@trancount do?

It will give you the number of active transactions for the current user.

Q70) What are the drawbacks of CTEs?

It is query bound.

Q71) What is the transaction log?

It keeps a record of all activities that occur during a transaction and is used to roll back changes.

Q72) What are before images, after images, undo activities and redo activities in relation to transactions?

Before images refers to the changes that are rolled back on if a transaction is rolled back. After images are used to roll forward and enforce a transaction. Using the before images is called the undo activity. Using after images is called the redo activity.

Q73) What are shared, exclusive and update locks?

A shared lock, locks a row so that it can only be read. An exclusive lock locks a row so that only one operation can be performed on it at a time. An update lock basically has the ability to convert a shared lock into an exclusive lock.

Q74) What does WITH TIES do?

If you use TOP 3 WITH TIES *, it will return the rows, that have a similarity in each of their columns with any of the column values from the returned result set.

Q75) How can you get a deadlock in SQL?

By concurrently running the same resources that access the same information in a transaction.

Q76) What is LOCK_TIMEOUT used for?

It is used for determining the amount of time that the system will wait for a lock to be released.

Q77) What is the ANY predicate used for?

SELECT * FROM emp_table WHERE enter_date > ANY (SELECT enter_date FROM works_on)

Q78) What is the ALL predicate used for?

SELECT * FROM emp_table WHERE enter_date > ALL (SELECT enter_date FROM works_on)

Q79) What are some control flow statements in SQL?

while, if, case, for each etc..

Q80) What is the EXISTS function used for?

It is used to determine whether a query returns one or more rows. If it does, the EXIST function returns TRUE, otherwise, it will return FALSE.

List of Related Microsoft Certification Courses:

 SSIS  Power BI
 SSRS  SharePoint
 SCCM  BizTalk Server
 Team Foundation Server  BizTalk Server Administrator


Popular Courses in 2018

Get Updates on Tech posts, Interview & Certification questions and training schedules