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
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
help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!