Short answer (imho of course) is No.
It's not appropriate to circumvent triggers by disabling / enabling them.
Having said that, I'm sure that there may be some circumstance that would warrant it, but I don't believe that it would be especially often.
Question is, is this such a case?. Have you thought of why the triggers are there in the first place?
Will anything break if you randomly switches them off and on?
What consequences will this bring for the consistency of the databases involved?
I wouldn't mess with this unless I knew the answers to all these questions...
Now, in order to aid you in your search, try to set up a profiler trace on your queries to see what's happening when you do your stuff.
After that's done, you should be able to decide if triggers are to blame, or if it's something else..