Question

This one will take some explaining. What I’ve done is create a specific custom message queue in SQL Server 2005. I have a table with messages that contain timestamps for both acknowledgment and completion. The stored procedure that callers execute to obtain the next message in their queue also acknowledges the message. So far so good. Well, if the system is experiencing a massive amount of transactions (thousands per minute), isn’t it possible for a message to be acknowledged by another execution of the stored procedure while another is prepared to so itself? Let me help by showing my SQL code in the stored proc:

--Grab the next message id declare @MessageId uniqueidentifier set @MessageId = (select top(1) ActionMessageId from UnacknowledgedDemands);  --Acknowledge the message update ActionMessages set AcknowledgedTime = getdate() where ActionMessageId = @MessageId  --Select the entire message ... ... 

In the above code, couldn’t another stored procedure running at the same time obtain the same id and attempt to acknowledge it at the same time? Could I (or should I) implement some sort of locking to prevent another stored proc from acknowledging messages that another stored proc is querying?

Wow, did any of this even make sense? It’s a bit difficult to put to words…

Answer 1

Something like this

--Grab the next message id begin tran declare @MessageId uniqueidentifier select top 1 @MessageId =   ActionMessageId from UnacknowledgedDemands with(holdlock, updlock);  --Acknowledge the message update ActionMessages set AcknowledgedTime = getdate() where ActionMessageId = @MessageId  -- some error checking commit tran  --Select the entire message ... ...