Shulou(Shulou.com)05/31 Report--

SQLServer in how to prevent concurrent insertion of duplicate data, many novices are not very clear about this, in order to help you solve this problem, the following editor will explain in detail for you, people with this need can come to learn, I hope you can gain something.

To prevent the concurrent insertion of duplicate data in SQLServer, there are roughly the following methods:

1. Use Primary Key,Unique Key and so on to make duplicate data impossible to insert at the database level.

two。 Use conditions when inserting

Insert into Table (*) select * where not exists (select 1 from Table where *)

3. Use the SERIALIZABLE isolation level and use updlock or xlock lock prompts (equivalent to using (updlock,holdlock) or (xlock,holdlock) under the default isolation level)

Set transaction isolation level SERIALIZABLEBegin Tran select 1 from Table with (UPDLOCK) where *-even with index support, a range lock RangeS-U is added. Although it can be locked, the concurrency performance is not good. If @ @ ROWCOUNT = 0 insert into Table (* *) values (*). Is it helpful for Commit Tran to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.