November 2, 2009 at 8:33 am
hi,
when u tried to modify the procedure then it gives me error like this...
Procedure tr_ProcedureEvents, Line 6
Invalid object name 'DDLTriggerTest..EventTableData'.
please let me know what causes this error and how to resolve that.
November 2, 2009 at 8:37 am
Feebie (11/2/2009)
hi,when u tried to modify the procedure then it gives me error like this...
Procedure tr_ProcedureEvents, Line 6
Invalid object name 'DDLTriggerTest..EventTableData'.
please let me know what causes this error and how to resolve that.
someone has put a DDL trigger on your database, and it's trying to update a table 'EventTableData' in the database 'DDLTriggerTest'
I'd guess that both the database and thus the table are missing, so the trigger errors out.
in SSMS go to your Server and browse to ServerObjects>>Triggers.
you'll need to disable or drop the trigger in question.
If it's not there, it might be at the database level...Specific Database>>Programmability>>Database Triggers
Lowell
November 2, 2009 at 9:06 am
hi,
thank you for quick reply.
so that is not a system default trigger?
November 2, 2009 at 9:28 am
lol no, MS does not issue any default system triggers, that's for sure...also you can kind of tell by the name:'DDLTriggerTest'
definitely some trying out some code.
Lowell
November 2, 2009 at 9:33 am
🙂 thank you for your help.
i am new to SQL...
September 30, 2013 at 2:34 am
Can someone please help me with this in the objectname column I am getting this getting this "IFTSAutonested"
I have done a lot of searching and cannot find the meaning of it. I have a reason to believe it is causing my database to freeze.
September 30, 2013 at 4:35 am
Select from sys.triggers and sys.server_triggers. based on the brief description you gave plus the fact the.name contains "nested " you might have a trigger that blocks itself as well as other transactions, post the trigger in a new thread and we can offer suggestions to fix the design glitch that is locking things up
Lowell
October 2, 2013 at 4:39 am
can you give me the description on how to disable this? As its causing issues on the Master instance.
October 2, 2013 at 6:37 am
more details from you before we can help, i think.
you really need to analyze the trigger itself, and fix the issue;
for example, if there is a trigger on a table that is calling itself in a nested fasion, that trigger needs to be rewritten; simply dropping the trigger might have unintended side affects, like wher the trigger is inserting data the application expects to exist...if the data doesn't get added.
If it's a database or server level trigger, then you again need to analyze the trigger, and either modify or disable the trigger
ie
DISABLE TRIGGER [TR_DB_NO_DROPPING_OBJECTS] ON DATABASE
--or if it was a server trigger
DISABLE TRIGGER logon_trigger_not_from_SSMS ON ALL SERVER
Lowell
October 2, 2013 at 7:16 am
the example I have is that. when a simple copy command is been sent to the file server it gets blocked and the communication between SQL and file server gets fails causing a que on the rest of the nodes which then is forcing the software we are working on to freeze. From looking at the profiler on SQL this AutoNested was showing up in the time frame from which this the whole process froze. It was only happening in the Master database.
then it seems to unblock its self after about 10 minutes on the both occasions its happened.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply