Comments
3 comments
-
Dirk,
Thankyou for your post about the trace flag. We are investigating this at the moment and will get back to you in due course.
Please accept our apologies if this has caused any inconvenience.
Chris -
Dirk.
Just thought I should get back to you with some info. The trace flag is currently used as part of the script decryption process. This allows you to see the contents of encrypted stored procedures if you have appropriate permissions. It seems that we failed to learn a lesson from SQL Compare that allowing people to turn this off is a must!
We'll make sure that this option is implemented for the next build we push out.
Simon -
Hi Simon,
that is great news for me !
I am eagerly awaiting your next build ;-)
Thanks,
Dirk
Add comment
Please sign in to leave a comment.
We have detected the use of a trace flag 3604 on one of our production servers.
At the same time a major job failed, which handles monetary transactions in the millions of euro.
It didn't take my fellow colleagues long to detect that the trace flag was coming from me (my connection to the database, that is).
Since I did not use this trace flag knowingly, and it appeared only very recently, I suspect it has to do with Sql Prompt 4 - I installed it yesterday...
Hence following questions:
Is it possible to provide an option to NOT use a trace flag to search for tables and stuff please ? (or not to use it altogether)
Our DBA doesn't like it (our sql server is hosted by another company) and this precludes us at the moment to use the product :-((
Additionally (but I haven't seen proof of this) he says that this trace flag can cause some transactions to fail. As I would use this product on our production database for maintenance purposes as well, this is a major factor to not use this product at the moment.
Thanks,
Dirk