Home Information PDF Documents EULANDA Handbooks Training Book's corner Download Contact us Table of Contents About us

Glossary

Password needed Newsgroup

Remote Support system

Naming Convention for SQL Server Objects (SQL API)

Back | Level back

The naming convention of all SQL server objects, like tables, views, procedures, must follow regulate firm in order to guarantee an error free operational sequence of the EULANDA® business logic  and in order to ensure the compatibility with future updates. This page contains a summary of these regulates.

Trigger

TR [ < contraction creator> ] _ 
         []

    

The individual named components of the Trigger would be separated by underlines. Beside these special characters only the letters "A" to "Z" and numbers from "0" to "9" may be used. Used except the short description for all named-divide excluding capital letters.

The trigger name begins always with the two letters "TR" followed of the alias of the creator. That is either "USER" or if you are a EULANDA® solution partner your registered alias. Afterwards the table alias followed. You can take these from the Abkürzungsverzeichnis (abbreviation listing). Is no abbreviation for the table planed by EULANDA®,  the complete table name is used.

After that the abbreviation of the supervised table operations:

Operations Abbreviation
INSERT INS
UPDATE UPD
DELETE DEL
INSERT, UPDATE INSUPD
INSERT, DELETE INSDEL
UPDATE, DELETE UPDDEL
INSERT, UPDATE, DELETE ALL

Afterwards can still more concisely understood follow, which describes the trigger.

Examples:

TR_USER_AF_UPD_StatusUeberwachung
TR_USER_AD_INSUPD_Historie
TR_DDHANDEL_RE_DEL_WaehrungsKurs

Stored Procedure

Procedure names begin with „cn_“. User procedures begin with „cn_user_“. Beside there are no further conventions. A good practice is to be used next the abbreviation of the table, which is concerned primarily (see also abbreviation listing (Abkürzungsverzeichnis)).

User tables

The names of the user tables may only with prefix "user" without the following underlined begin. Excluded are the contraction registered solution partner.

Views

The names of the user view should begin with "USER_“.

Constraints

Constraint names must with the standard contraction for the type followed of one underlined begin (see also name conventions).

"USER" must follow after the user constraints.