DB Trigger item - Does it exist?

[Paolo F Cantoni]

We are investigating extending the standard data(base) modelling to overlay the shapescripts with additional functionality.

Specifically, we are looking at SQL Server.  When we create a pattern structure from the available patterns (in this case "Basic SQL Server 2012 Model") we get the following structure:

Database A
Functions
Procedures
Queries
Sequences
Triggers
Tables
Views
Connections

When we reverse engineer using DB Builder, the appropriate folder is populated with the appropriate component type.
The Data Modelling Toolbox shows items for all the above EXCEPT for "Triggers".  None of our DBs (that we have reverse engineered) so far have used triggers so we can't see what EA uses after the reverse engineer.  Does anybody know if there is a separate stereotype for the Trigger?

TIA,
Paolo

[Richard Freggi]

Yes, the stereotype is right there in Configure - UML types menu.

[Paolo F Cantoni]

Yes, the stereotype is right there in Configure - UML types menu.

Thanks, Richard,
But the one I'm after is the EAUML::xxxxx version as the Data Modelling stuff is now held in the EAUML profile.  It doesn't seem to be there.

Paolo

[KP]

Yes, there is a stereotype EAUML::trigger that extends UML::Operation. I don't know why it isn't in the toolbox - maybe there's a "correct" way to create them and dropping from the toolbox isn't it? A quick support request should get you an answer.

[Paolo F Cantoni]

Yes, there is a stereotype EAUML::trigger that extends UML::Operation. I don't know why it isn't in the toolbox - maybe there's a "correct" way to create them and dropping from the toolbox isn't it? A quick support request should get you an answer.

Thanks, Neil,

I'll pop in a request.  Now that you say it's based on Operation, that would explain why I couldn't see it in the dropdowns.

Paolo

[Paolo F Cantoni]

I tried to create a Database trigger (as opposed to a table related trigger).  DB builder didn't see it.  Does anyone know if it is supported?

TIA,
Paolo

Trivial example (in case you've never seen a Database trigger):

Code: [Select]

CREATE TRIGGER MyDBTrigger ON DATABASE
FOR ALTER_TABLE
AS
IF IS_MEMBER ('db_owner') = 0
BEGIN
   PRINT 'You must ask your DBA to drop or alter tables!'
   ROLLBACK TRANSACTION
END
GO

[Paolo F Cantoni]

I tried to create a Database trigger (as opposed to a table related trigger).  DB builder didn't see it.  Does anyone know if it is supported?

[SNIP]

As I mentioned in the original post, there is a folder for Triggers.  As KP mentioned, table level triggers are specialized operations which are located within the table item.  Consequently, they can't appear in their own folder.

I surmise that the Triggers folder is for database-level triggers which are first-class DB objects in their own right.  Accordingly, since (currently - b1554) DBBuilder doesn't see them, should the folder be retained (to allow for the defect to the rectified) or should we delete it from the "pattern"?

I'm asking because we are finalising our new strategy for Database modelling within the organisation and I'd welcome input before we "lock the door".

TIA,
Paolo

[Paolo F Cantoni]

Reported,
Paolo