SQL SERVER – Interview Questions and Answers – Frequently Asked Questions – Day 6 of 31

SQL Server Interview Questions and Answers
Print Book Available (207 Pages) | Sample Chapters

Please read the Introductory Post before continue reading interview question and answers.

List of all the Interview Questions and Answers Series blogs

2) Common Questions Asked

Which TCP/IP port does the SQL Server run on? How can it be Changed?

SQL Server runs on port 1433. It can be changed from the Network Utility TCP/IP properties –> Port number, both on client and the server.

What are the Difference between Clustered and a Non-clustered Index?

A clustered index is a special type of index that reorders the way records in the table are physically stored. Therefore, the table can have only one clustered index. The leaf nodes of a clustered index contain the data pages.

A non-clustered index is a special type of index in which the logical order of the index does not match the physical stored order of the rows on disk. The leaf node of a non-clustered index does not consist of the data pages. Instead, the leaf nodes contain index rows. (Read more here)

What are the Different Index Configurations a Table can have?

A table can have one of the following index configurations:

  • No indexes
  • A clustered index
  • A clustered index and many non-clustered indexes
  • A non-clustered index
  • Many non-clustered indexes

What are Different Types of Collation Sensitivity?

Case sensitivity – A and a, B and b, etc.

Accent sensitivity – a and á, o and ó, etc.

Kana Sensitivity – When Japanese Kana characters Hiragana and Katakana are treated differently, it is called Kana sensitive.

Width sensitivity – When a single-byte character (half-width) and the same character represented as a double-byte character (full-width) are treated differently, it is width sensitive. (Read more here)

What is OLTP (Online Transaction Processing)?

In OLTP –(online transaction processing) systems, relational database design uses the discipline of data modeling and generally follows the Codd rules of data normalization in order to ensure absolute data integrity. Using these rules, complex information is broken down into its most simple structures (a table) where all of the individual atomic level elements relate to each other and satisfy the normalization rules.

What’s the Difference between a Primary Key and a Unique Key?

Both primary key and unique key enforce uniqueness of the column on which they are defined. But by default, the primary key creates a clustered index on the column, whereas unique key creates a non-clustered index by default. Another major difference is that primary key doesn’t allow NULLs, but unique key allows one NULL only. (Read more here)

What is Difference between DELETE  and TRUNCATE Commands?

Delete command removes the rows from a table on the basis of the condition that we provide with a WHERE clause. Truncate will actually remove all the rows from a table, and there will be no data in the table after we run the truncate command.


  • TRUNCATE is faster and uses fewer system and transaction log resources than DELETE. (Read all the points below)
  • TRUNCATE removes the data by deallocating the data pages used to store the table’s data, and only the page deallocations are recorded in the transaction log.
  • TRUNCATE removes all the rows from a table, but the table structure, its columns, constraints, indexes and so on remains. The counter used by an identity for new rows is reset to the seed for the column.
  • You cannot use TRUNCATE TABLE on a table referenced by a FOREIGN KEY constraint.
  • Using T-SQL – TRUNCATE cannot be rolled back unless it is used in TRANSACTION. OR TRUNCATE can be rolled back when used with BEGIN … END TRANSACTION using T-SQL.
  • TRUNCATE is a DDL Command.
  • TRUNCATE resets the identity of the table.


  • DELETE removes rows one at a time and records an entry in the transaction log for each deleted row.
  • DELETE does not reset Identity property of the table.
  • DELETE can be used with or without a WHERE clause
  • DELETE activates Triggers if defined on table.
  • DELETE can be rolled back.
  • DELETE is DML Command.
  • DELETE does not reset the identity of the table.

(Read more here)

List of all the Interview Questions and Answers Series blogs

Reference: Pinal Dave (http://blog.SQLAuthority.com)

About these ads

20 thoughts on “SQL SERVER – Interview Questions and Answers – Frequently Asked Questions – Day 6 of 31

  1. Hi Pinal, 1st post, your blog is the greatest!
    How can you roll back a delete? (does it have to be inside a begin commit transaction?)

  2. Pingback: SQL SERVER – Interview Questions and Answers – Frequently Asked Questions – Complete Downloadable List – Day 0 of 31 Journey to SQLAuthority

  3. Hi Pinal,
    As mentioned by you for DELETE: It can be rolled back.

    It seems that TRUNCATE cannot be rolled back. But TRUNCATE just like DELETE can be rolled backed if used in transaction, otherwise not. This also stands true for DELETE.

    If DELETE is not in transaction then also it cannot be rolled back.

  4. Great job Mr Pinal,
    This is helpful for advanced and nivices users. It’s a good opportunity for checkup for those who are experienced and the news users. Keep go on spread the SQL tech.

  5. @SDDesh:
    1) Every time we use truncate statement it locks the whole table with “Schema modification (Sch-M)” lock, which is not good for a time sensitive OLTP system. So we have to carefully decide which statement to use (Delete or Truncate).
    2) Delete acquires an exclusive lock only on all the rows that satisfy the where condition.

  6. Love this series!

    “TRUNCATE resets the identity of the table.”
    “DELETE does not reset the identity of the table.”

    Can you explain this? In the context being described here, what is “the identity of the table” referring to?

    • This means if a table has an IDENTITY column, or a column defined as IDENTITY, like create table xyz (col_id IDENTITY(1,1) INT, col2….)

      Then if you ever truncate the table the initial IDENTITY or seed value of Col_id is reset, like here to 1.

      But this does not happens with DELETE. It retains the last IDENTITY value of that column.

      • Thanks. I *thought* that’s what it meant; however, I was confused because earlier in the list of points it says (for TRUNCATE) “The counter used by an identity for new rows is reset to the seed for the column.” and (for DELETE) it says “DELETE does not reset Identity property of the table.” In other words, there are *two* somewhat similar “identity” reference points for each command.

        I figured each command might do something *additional*, identity-wise, beyond the effect upon any IDENTITY columns.

  7. Hi Pinal,
    Im sorry Im not talkin about TRUNCATE and DELETE statements but I know u have a quick answer for me. The issue is: “Im using C# for .Net VStudio 2005 and MS SQL server2005, in the user interface in C#, Im using french to type data in a textbox of C# and then save them in the database; when I enter a text with apostrophe(like l ‘ endroit, l ‘ île, l ‘ enjeu), it refuses to save coz of the ‘ (the apostrophe). How can I capture text with apostrophe from a textbox and save them in the SQL Server database. Is the problem in C# or in SQL server ?

    • Dieudonné : No sure if you got the answer to your query which is more than 1 yr old. But ideally whenever you wanna enter data with ‘ (the apostrophe) you should use double ‘ (the apostrophe). So values should be entered like l ‘‘ endroit, l ‘‘ île, l ‘‘ enjeu.
      Hope it helps ;)

  8. i am making client-server application in vb.net 2005 first time. i have 3 User-Interfaces on client side and Ms sql-server on server side. How i will connect my client side forms with sql-server 2000. What will be the connection string
    in vb.net to connect the Ms SQLserver 2000.

    kindly helpe me

  9. Hi Pinal ,
    It is very help full for freshers who are visiting this sites you provide a very basic concepts of sql it would be great help from you if you suggest any practical queries

  10. Pingback: SQL SERVER – Weekly Series – Memory Lane – #036 | Journey to SQL Authority with Pinal Dave

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s