Skip to main content

Whats up with identity_insert ?

Basics:
To insert explicit value in the identity column of a table we need to set identity_insert On. Syntax for this is
SET IDENTITY_INSERT tablename ON

Now execute all your insert / update queries

Make sure you set the identity_insert to Off. Syntax for this is
SET IDENTITY_INSERT tablename OFF

Did you know:
Identity insert is session sensitive. If you have an identity_insert On for another table in that session you will get the message " IDENTITY_INSERT is already ON for table 'xxx'. Cannot perform SET operation for table 'tablename'."

To test this you can open another session and try executing the same statement again. You will not get the error message this time.

Option 2:

Step 1: Go to the Table name in the Object Explorer and click on Design.
Step 2: In column Properties, go to 'Identity Specification' and select 'Is identity' as 'No'
Step 3: Click on Save.

Now try the insert/update command.

Still does not work?


Step 1: In Sql Server Management Studio ,  Go to Tools --> Option and click on Designer.
Step 2: Uncheck "Prevent Saving changes that require table re-creation"













Now you are all set. You can re-execute the queries, it should not give you any problem.

Since we are talking about Identity let me also mention how to reset the identity.

DBCC CHECKIDENT (tablename, reseed, x)
... tablename is the name of the table that needs to be reseeded.
... x is an integer value that is one less than the value you want the indexing to start

Let me know how your experience was. :)

Labels:

Comments

Post a Comment

Popular posts from this blog

Insufficient access rights to perform the operation. (Exception from HRESULT: 0x80072098)

While accessing the active directory (AD) and authorization manager (AZMAN) , If you get “   Insufficient access rights to perform the operation. (Exception from HRESULT: 0x80072098)  “ message check the    account that is being used to get the LDAP query from AD .  ERROR DETAILS Exception Details:  System.Runtime.InteropServices.COMException: Insufficient access rights to perform the operation. (Exception from HRESULT: 0x80072098) Source Error: Line 154:    'Session("FullName") = System.Security.Principal.WindowsIdentity.GetCurrent.Name.ToString() Line 155: Line 156:    If Not User.IsInRole("Role1") Then Line 157:          Response.Redirect("./Login.aspx") Line 158:    End If  Stack Trace : .... SOLVE IT Steps to do check the app pool rights: Click on the website name that you are having problem with in IIS  In the right panel you will se...
Post a Comment
Read more

Do's and Don't SQL

Do's: Writing comments whenever something is not very obvious, as it won’t impact the performance.  (--) for single line  (/*…*/) to mark a section Use proper indentation Use Upper Case for all SQL keywords. SELECT, UPDATE, INSERT, WHERE, INNER JOIN, AND, OR, LIKE. Use BEGIN... END block for multiple statements in conditional code  Use Declare and Set in beginning of Stored procedure Create objects in same database where its relevant table exists otherwise it will reduce network performance. Use PRIMARY key in WHERE condition of UPDATE or DELETE statements as this will avoid error possibilities. If User table references Employee table than the column name used in reference should be UserID where User is table name and ID primary column of User table and UserID is reference column of Employee table. Use select column name instead of select * Use CTE (Common Table Expression); its scope is limited to the next statement in SQL query, instead of...
Post a Comment
Read more

SQL Server 2008 - Inline Variable Assignment

Microsoft SQL Server 2008 brings in a new feature of 'Declaring and Assigning' a variable all in a single line. Earlier, while using SQL 2005 and earlier versions, we had to declare a variable before assigning it. This feature is explained in detail below. In SQL 2005 and earlier versions we had to write: Declare @age int Declare @name nvarchar(25) Declare @date date Set @age = 25 Set @name = "Garry" Set @date = GETDATE() With SQL 2008 we can combine both these statements to write Declare @age int = 25 Declare @name nvarchar(25) Declare @date @date = GETDATE() Advantage : This helps us to write less code, yet get the same functionality. Even though this feature has been available it is not being used in many projects because of backward compatibility issue. If the same code is being used on both 2005 and 2008 server we would prefer writing in a format compatible to both. Do share with us :  Would you like to use this new method? If not, why?
Post a Comment
Read more