Best practices for Database Management Standards

 

 Best Practices for Appian developers

Appian best practices are like a check list, use these checklists at different stages of your development cycle as described to ensure application success and reduce technical risk. Each section provides guidance for when and how often you should use these.

16.Best practices for Database Management Standards :-

Whenever possible, tables should be created by Appian when publishing a data store vs. writing a SQL script to create them manually. If the application is referencing an existing table then this is not possible, otherwise, this is the preferred approach (less error-prone).

Tables and views should be prefixed with the short name or acronym of the application. For example, Sales Contract Management tables are all prefixed with “SCM_”. Views should have SCM_V_ to indicate the referenced table is actually a view.

The SQL to create or replace a database view should be contained in a DDL or SQL file and stored in folder within Appian. This will allow for version control and provide a single location for all of the application’s SQL.

Add an “active” bit column should be used to denote active vs. inactive data. To prevent data relationship and integrity issues, avoid the deletion of rows. Use an active flag to denote active vs. inactive data. Queries can then filter on that column to return the desired data.