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 see 'Basic Settings'. Click It. Select the specific pool option and enter the name of the ac
Post a Comment
Read more

Sql Server database Read_Only / Read_Write

The ALTER DATABASE command allows a database administrator to modify SQL Server databases and their files and filegroups. This includes permitting the changing of database configuration options. Why Read Only ? When you need to ensure that the data is a database is not modified by any users or automated processes, it is useful to set the database into a read-only mode. Once read-only, the data can be read normally but any attempts to create, updated or delete table rows is disallowed. This makes the read-only mode ideal when preparing for data migration, performing data integrity checking or when the data is only required for historical reporting purposes. Make Database Read Only USE  [master] GO ALTER DATABASE  [TESTDB]  SET  READ_ONLY  WITH  NO_WAIT GO Make Database Read/Write USE  [master] GO ALTER DATABASE  [TESTDB]  SET  READ_WRITE  WITH  NO_WAIT GO In case you get the following error message make the database single user: Msg 5070, Level 16, Stat
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 temporary tables and der
Post a Comment
Read more