Viewing 15 posts - 406 through 420 (of 5,394 total)
It must be the floats, because NULLs are treated as equal by EXCEPT:
SELECT NULL
EXCEPT
SELECT NULL
returns no results.
June 12, 2015 at 7:07 am
What's the problem? The sleeping tasks? Can you please clarify your issue?
June 12, 2015 at 6:59 am
Log shipping will break your existing backup plans.
Use the log shipping transaction log backups to protect your database.
Instead of relying on log shipping directly, you could roll your own using...
June 12, 2015 at 6:43 am
There's no need to use a cursor in that trigger:
ALTER TRIGGER [dbo].[trgInsUpdBookingBasket]
ON [dbo].[Booking_Basket]
AFTER INSERT,UPDATE
AS
BEGIN
SET NOCOUNT ON;
UPDATE BM
SET
DateBegin = MinCheckInDate,
DateEnd = MaxCheckOutDate
FROM Booking_Main AS BM
CROSS APPLY (
SELECT MIN(CheckInDate) AS...
June 12, 2015 at 6:40 am
GilaMonster (6/12/2015)
'it's enforced by the app' is followed by 'why is my data wrong' in just about every case I've seen.
If I had $0.01 for every time this...
June 12, 2015 at 5:11 am
Looks like you have no unique index on lockedby.
June 12, 2015 at 4:57 am
matthew.green 36969 (6/12/2015)
fyi deadlock graph attachedthe 2 conflicting statments in this instance are:
303: MarkAsCompleted 'C0239484'
192: MarkAsKO 'C0239494'
As such seems to be conflicting with another proc - im reviewing now
Thanks...
June 12, 2015 at 4:22 am
matthew.green 36969 (6/12/2015)
sorry for delay - my profilers not picking up the graphs - will ppost soon - the deadlock issue is worse with the new code
No need to capture...
June 12, 2015 at 4:09 am
spaghettidba (6/12/2015)
GilaMonster (6/12/2015)
spaghettidba (6/12/2015)
This is how I would do it:
That isn't identical. If there are multiple rows in tbl_main locked by the same user, the original will update one of...
June 12, 2015 at 3:41 am
GilaMonster (6/12/2015)
spaghettidba (6/12/2015)
This is how I would do it:
That isn't identical. If there are multiple rows in tbl_main locked by the same user, the original will update one of them...
June 12, 2015 at 3:38 am
BTW, your code assumes that only one row at a time can be locked by a particular user. The same assumption is applied in my rewrite, but you should probably...
June 12, 2015 at 3:37 am
Probably same as before: unneeded reads before you write.
This is how I would do it:
CREATE PROCEDURE [dbo].[MarkAsKO]
@Username varchar(25),
@Reason varchar(1024),
...
June 12, 2015 at 3:31 am
No, nothing particular, but I tend to avoid it when I can achieve the same with row locks.
June 12, 2015 at 3:08 am
Nothing happens? Please clarify the exact steps you took while trying to restore the backup.
June 12, 2015 at 2:47 am
Viewing 15 posts - 406 through 420 (of 5,394 total)