Gents,
I have come into a system that uses a secondary table to generate (for
want of a better word) Identities.
eg
create table myidents
( name sysname not null, ident int not null)
create procedure getnextident @table sysname, @ident int output
as
begin
if not exists (select top 1 1 from myidents where name = @table)
insert into myidents values (@table, 0)
update myidents
set @ident = ident = ident + 1
where name = @table
end
now, (ignoring for now the use of reserved words) the problem is that
this is called frequently, from other procedures. Trouble is that the
calling procedures call it from within a transaction. We now have a
wickedly hot spot on this table, with frequent deadlocks.
Is there any relatively quick fix for this? Some locking hints or
whatever.
Or do we need to go and recode, moving this kind of thing outside the
transaction (which are all rather too long for my liking), and even
cosidering using identity columns as a replacement?
Thanks 4 2240
IMHO, IDENTITY would be the best approach with the current design. You
might also consider using natural keys instead of surrogate key values.
If your actual myident table has no primary key on name, this will
contribute to blocking/deadlocking. Unless your application always acquires
values in the same sequence, you will be vulnerable to deadlocks unless you
specify a TABLOCKX hint. This is obviously bad for concurrency (especially
for long-running transactions) and should be avoided if possible.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"WangKhar" <Wa******@yahoo.com> wrote in message
news:bb**************************@posting.google.c om... Gents,
I have come into a system that uses a secondary table to generate (for want of a better word) Identities.
eg
create table myidents ( name sysname not null, ident int not null)
create procedure getnextident @table sysname, @ident int output as begin if not exists (select top 1 1 from myidents where name = @table) insert into myidents values (@table, 0)
update myidents set @ident = ident = ident + 1 where name = @table end
now, (ignoring for now the use of reserved words) the problem is that this is called frequently, from other procedures. Trouble is that the calling procedures call it from within a transaction. We now have a wickedly hot spot on this table, with frequent deadlocks.
Is there any relatively quick fix for this? Some locking hints or whatever.
Or do we need to go and recode, moving this kind of thing outside the transaction (which are all rather too long for my liking), and even cosidering using identity columns as a replacement?
Thanks
You could try this:
if not exists (select top 1 1 from myidents ROWLOCK, UPDLOCK where name =
@table)
Hope it will help.
Igor
"WangKhar" <Wa******@yahoo.com> wrote in message
news:bb**************************@posting.google.c om... Gents,
I have come into a system that uses a secondary table to generate (for want of a better word) Identities.
eg
create table myidents ( name sysname not null, ident int not null)
create procedure getnextident @table sysname, @ident int output as begin if not exists (select top 1 1 from myidents where name = @table) insert into myidents values (@table, 0)
update myidents set @ident = ident = ident + 1 where name = @table end
now, (ignoring for now the use of reserved words) the problem is that this is called frequently, from other procedures. Trouble is that the calling procedures call it from within a transaction. We now have a wickedly hot spot on this table, with frequent deadlocks.
Is there any relatively quick fix for this? Some locking hints or whatever.
Or do we need to go and recode, moving this kind of thing outside the transaction (which are all rather too long for my liking), and even cosidering using identity columns as a replacement?
Thanks
WangKhar (Wa******@yahoo.com) writes: create procedure getnextident @table sysname, @ident int output as begin if not exists (select top 1 1 from myidents where name = @table) insert into myidents values (@table, 0)
update myidents set @ident = ident = ident + 1 where name = @table end
now, (ignoring for now the use of reserved words) the problem is that this is called frequently, from other procedures. Trouble is that the calling procedures call it from within a transaction. We now have a wickedly hot spot on this table, with frequent deadlocks.
Is there any relatively quick fix for this? Some locking hints or whatever.
Deadlocks can usually be avoided by:
BEGIN TRANSACTION
SELECT @ident = ident FROM tbl (UPDLOCK) WHERE name = @table
UPDATE tbl SET ident = @ident WHERE name = @table
COMMIT TRANSACTION
However, if you have more work in the transaction, you will have lot of
blocking and not much concurrency in the system. And if you in some
procedures perform work before you come here, they might be blocking
other processes that aleady have an ident, and now wil block the other
prcoess.
The above is only really meaningful if you have busienss rules that
require consecutive series. Else you should move out the ident-generation
out of the transaction or use IDENTITY instead.
--
Erland Sommarskog, SQL Server MVP, so****@algonet.se
Books Online for SQL Server SP3 at http://www.microsoft.com/sql/techinf...2000/books.asp
Thanks thats pretty much what I thought ...
See if I can convince people that we need to take this action :(
Erland Sommarskog <so****@algonet.se> wrote in message news:<Xn*********************@127.0.0.1>... WangKhar (Wa******@yahoo.com) writes: create procedure getnextident @table sysname, @ident int output as begin if not exists (select top 1 1 from myidents where name = @table) insert into myidents values (@table, 0)
update myidents set @ident = ident = ident + 1 where name = @table end
now, (ignoring for now the use of reserved words) the problem is that this is called frequently, from other procedures. Trouble is that the calling procedures call it from within a transaction. We now have a wickedly hot spot on this table, with frequent deadlocks.
Is there any relatively quick fix for this? Some locking hints or whatever.
Deadlocks can usually be avoided by:
BEGIN TRANSACTION
SELECT @ident = ident FROM tbl (UPDLOCK) WHERE name = @table UPDATE tbl SET ident = @ident WHERE name = @table
COMMIT TRANSACTION
However, if you have more work in the transaction, you will have lot of blocking and not much concurrency in the system. And if you in some procedures perform work before you come here, they might be blocking other processes that aleady have an ident, and now wil block the other prcoess.
The above is only really meaningful if you have busienss rules that require consecutive series. Else you should move out the ident-generation out of the transaction or use IDENTITY instead. This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics |
by: Fredrik M?ller |
last post by:
Hi All,
I have read about deadlocks here on Google and I was surprised to read
that an update and a select on the same table could get into a
deadlock because of the table's index. The update...
|
by: Tim McAuley |
last post by:
Hi,
I have a stored procedure that is causing deadlocks when called multiple
times synchronously. The odd issue is that the deadlock seems to be
happening on different threads waiting for locks...
|
by: Mike Carr |
last post by:
I am running into an issue. Recently I installed IBuySpy Portal and then converted the data source to odp.net. When debugging the app my machine would freeze or become really slow. I can reproduce...
|
by: Ben |
last post by:
I'm doing a bunch of data mining against a postgres database and have
run into an interesting problem with deadlocks. The problem is,
postgres is detecting them and then wacking the offending...
|
by: Carlos Moreno |
last post by:
Hello,
I'm using PostgreSQL 7.4.3 on a RedHat 9 Linux server
(a P4 HyperThreaded, using the SMP kernel, in case this
makes a difference).
I'm not 100% sure I understand exactly why I am...
| |
by: Greg Stark |
last post by:
There's another poster complaining about referential integrity checks causing
deadlocks. Unfortunately I've deleted the message so this response (and the
archives aren't responding) isn't going to...
|
by: Rahul Babbar |
last post by:
Hi,
Is there any way to find the SQL that is causing the Locks.
I am using SYSPROC.SNAPSHOT_LOCK to find out the locks on the table,
but i am unable to find out which SQL statement was...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing,...
| |
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and...
|
by: TSSRALBI |
last post by:
Hello
I'm a network technician in training and I need your help.
I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs.
The...
|
by: adsilva |
last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
|
by: 6302768590 |
last post by:
Hai team
i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated ...
|
by: bsmnconsultancy |
last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence...
| |