July 24, 2009 at 9:11 am
the trigger that’s firing is responding to fairly high volumes of data flowing through the system
Here is the Error Message:
Message: Warning: Fatal error 5243 occurred at xxx ## 2009 #:##PM. Note the error and time, and contact your system administrator.
Data: System.Collections.ListDictionaryInternal
TargetSite: NULL
HelpLink: NULL
Source: NULL
2) Exception Information
*********************************************
Exception Type: System.Data.SqlClient.SqlException
Errors: System.Data.SqlClient.SqlErrorCollection
Class: 22
LineNumber: 44
Number: 21
Procedure: foo_Update_Trigger
Server: (local)
State: 1
Source: .Net SqlClient Data Provider
ErrorCode: -2146232060
Message: Warning: Fatal error 5243 occurred at xxx ## 2009 #:##PM. Note the error and time, and contact your system administrator.
Data: System.Collections.ListDictionaryInternal
TargetSite: Void Save()
Curtis Smith
SQL Server DBA
Well in worked in Theory ...
July 24, 2009 at 9:20 am
Do you have the source code for that trigger?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 24, 2009 at 9:56 am
Sorry I cannot post the text of the trigger, but here is what it is doing, nothing complicated;
Insert into table( … )
Select inserted.ColumnA, deleted.ColumnA
From inserted inner join deleted
Where (deleted.ColumnA inserted.ColumnA)
OR (deleted.ColumnA IS NULL and inserted.ColumnA is not null)
OR (deleted.ColumnA IS NOT NULL and inserted.ColumnA IS NULL)
UNION
Select inserted.ColumnB, deleted.ColumnB
From inserted inner join deleted
Where (deleted.ColumnB inserted.ColumnB)
OR (deleted.ColumnB IS NULL and inserted.ColumnB is not null)
OR (deleted.ColumnB IS NOT NULL and inserted.ColumnB IS NULL)
...
not sure if this is causing problem in the tempdb because of high volume
Curtis Smith
SQL Server DBA
Well in worked in Theory ...
July 27, 2009 at 11:58 am
This problem has been resolved. Not sure of what was causing the problem exactly, but applying SP3 resolved the issue
Curtis Smith
SQL Server DBA
Well in worked in Theory ...
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply