There are many reasons why organizations are implementing standardization, the most important thing is the saving of working time and savings of economic resources, as well as the competitive advantage, the improvement of efficiency, effectiveness and the prevention of human errors. Which is reflected in the image of the organization to its customers or Stakeholder.
A software project, regardless of how many people are involved in its life cycle, needs to establish standards, because each person handles different forms of work, acquired in other projects, organizations or learned in a study center. In this line, it is necessary to give importance to work in SQL database, because in this, all the information consumed by the software is manipulated.
This database guarantees that any change in the product is made at a lower cost and with greater security and speed, providing the desired quality. Ensuring that the development staff performs the activities identically when necessary.
For this, we have the ISO / IEC 9075, which was developed by different international, governmental and non-governmental organizations such as ISO, EIC, which covers the IT field and focused on the SQL language for RDBMS managers such as Oracle, MySql, SQL Server , DB2, among others. Currently, in its 2016 version, it defines the data structures and basic operations in SQL-data; providing fundamental features to create, access, maintain, control and protect SQL data. Among the most relevant elements about the syntax and semantics of a database language, we have:
To specify and modify the structure and restrictions of integrity of SQL data.
– For declaring database language procedures.
– To embed SQL statements in a compilation unit.
For this article to be more useful, we cite some examples:
- Columns: Use the Pascal Case format. Also, have only letters and a singular character because it represents a single characteristic of the subject of the table to which it belongs: CustomerId, CustomerName, PhoneNumber, CustomerPassword.
- Tables: the singular name when it represents an entity and plural when more than one entity (Snake Case) are joined: Distributors, Distributor_Notes, Distributor_Status.
- Stored procedure: The name must be related to the entity <Entity_Action_Sp> (Snake Case) leaving aside Sp_ as a prefix, because it slows the query: Distributors_GetALL_Sp, Distributors_GetByStatus_Sp.
- Functions: the name defined by the action or verb followed by “Fn” (Snake Case): GetOpenDate_Fn, ParseTableToString_Fn, CalculateAge_Fn.
It is important to define a standard, and this, depends on the vision and the rules that each organization manages, the definition of the standard for each object in the SQL database. Bearing in mind that it must be readable even for those people who are not involved in the IT technological environment.