Mark Flippin (me******@comcast.net) writes:
I'm just starting to use triggers in my databases and find the support
in Enterpise Manager lacking.
Using Enterprise Manager and Query Analyzer you can maintain the
triggers, but it's cumbersome.
Are there better tools for creating and managing triggers?
You don't specify what is cumbersome, but I can't see that trigger should
be any more cumbersome to use than stored procedure. That's true, that
maintaining anything from Enterprise Manager is cumbersome, and I usually
recommend people to stay awau from it...
In our shop we use a third-party text editor for all our SQL editing. This
editor, Textpad, has no special SQL capabilities, but is just a good editor.
As a devloper I load the SQL file through a command-line utility that
I fire off from within Textpad.
All our files are under source control. If we have a table widgets, the
definition for that table is in widgets.tbl. Indexes are in widgets.ix,
foreign keys are in widgets.fkey and triggers in widgets.tri. Normally
we have one object per file, with the name macthing the object, but
triggers are an exception. All triggers for one table is one file.
--
Erland Sommarskog, SQL Server MVP,
es****@sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp