It's the first time I see us zip codes of more than 5 numbers. Is this a common occurance?

If not maybe you could ship that in its own colum...

In sp_who2, scan the column BlkBy, anything different than "-" will mean that this process is blocked by the spid in that column.

You can see what that process is running...

To finish Ron's thaught :

CREATE TRIGGER LogOn_Delete

on ACCESS

For

DELETE

as

SET NOCOUNT ON

UPDATE L

SET LogoffDate = GETDATE()

FROM LogOn L inner join Deleted D on L.scrnnbr = D.scrnnbr and L.userid =...

Sorry for the confusion, I was talking of locks that could be holding back the whole process.

Can you try to recreate the situation and run the proc sp_locks and sp_who2...

Are you running that much out of space??

can you post the trigger code, table definition and the error messages you are getting?

Strange... have you see any deadlocks while it hung?

I got the same setup here, and the same problem.. I'll be anxiously waiting for an answer on this one.

if not exists (Select * from Deleted) and Exists (Select * from Inserted)

begin

Update...

end

You could create a task that would be run periodically by the sql server agent (open server in EM, thn gestion, sql server agent, tasks).

Just schedule it to run to...

Please do no cross-post.

Finish this thread here :

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=9&messageid=188352

exec sp_changeObjectOwner 'ObjectName', 'NewUser'

BTW, the point of logging the statement is to be able to rerun it and see if it's a compile or execution error and then fix the problem... fix is...

Sounds like an assumption of code execution to me (like the order by should be by the primary key if none is specified)... Nothing good can come out of...

Just rechecked to see which one was performing better, but they use the same execution plan so you may chose the one that you like best just by its looks...