Without knowing what column EventDate is (we can guess, but that's dangerous!) we can't tell you.
However, if EventDate is a DATETIME type, how about
CAST(EventDate ASDATE) = CAST('NOW'ASDATE)
(Disclaimer - I don't know Firebird so using 'NOW' to get current date/time seems a bit weird - converting a string literal NOW to date time? I'd be more used to CAST(NOW() AS DATE) or CAST(NOW AS DATE) ... )
createtable PendingQueue (
cnstraint pk_pending_id nonclusteredprimarykey(id));
createclusteredindex cdxPendingQueue on PendingQueue (DueTime);
insertinto PendingQueue (DueTime, Payload)
values (@dueTime, @payload);
@batchsizeint = 100,
@retrysecondsint = 600assetnocounton;
set@now = getutcdate();
with cte as (
from PendingQueue with (rowlock, readpast)
where DueTime < @noworderby DueTime)
set DueTime = dateadd(seconds, @retryseconds, DueTime)
output deleted.Payload, deleted.id;
Specially see this line set DueTime = dateadd(seconds, @retryseconds, DueTime)
How this line instruct sql server to retry the update data again after 10 minute if fail to update data first time. this is not clear to me. please some one explain if you understand properly. thanks
I have some confusion about lock (ROWLOCK ,UPDLock AND xlock). i want to know the difference among these locks. where to use UPDLock, when to use RowLock and when Xlock with a example for better clarification.
BEGINTRANSACTIONSELECT @ID=RowID FROM MyTable WITH (ROWLOCK, XLOCK, HOLDLOCK) WHERE ID=6822
In the above sql rowlock and XLOCK both use as a result from other session records 6822 could not be read or modify. XLOCK alone is capable to lock the rows....so why one should use ROWLOCK & XLOCK together ?
if i use only xlock & HOLDLOCK then it will not serve the purpose ?
2) Tell me with example what is the difference between ROWLOCK & UPDLOCK ?
ROWLOCK prevent other session to modify data and UPDLOCK does the same thing. so what is the difference
between ROWLOCK & UPDLOCK ?
Please anyone explain these difference with example as a result at my end i can run the example code and understand.
I was looking for an efficient way to store "States" of entities in the DB. For example I had OrderStatus and that can be mapped to a table called Status and have the ID and the status Name be present in a join. If however I wanted to add more statuses for other Entity tables I don't want to have to create a new table for every Entity, is there a way to store all these statuses in one table? Thanks
I , the last project I was asked to advise on was managed by a PM who was adamant that this was the "modern" way to go (I was accused of being an old fart who was stuck in the 90's). Started off as a 2 column table and the last I saw of it was a 5 column, 2 table structure.
Luckily I walked away from anything to do with the project.
Never underestimate the power of human stupidity -
I'm old. I know stuff - JSOP