Ramco ERP on Cloud Enterprise Edition Database Architecture Design - Overview Introduction

This write-up furnishes at a macro level, the database architecture design and principles adopted during the development of Ramco ERP on Cloud Enterprise Edition business components. This content dwells around the primary data storage structures that comprise the system. And the database deliverables are targeted for SQL Server as the RDBMS.

Core Database Components

Ramco solution is multi tiered and has the Web layer, Application layer and Database Layer deliverables. Data exchanged between the Application layer and the Database layer is governed by the Application layer and specifically the Transaction scope is managed by the Application layer. The Database Infrastructure has the following database components:

Database Name
DEPDB

Description
This database contains the metadata related to the business components that get deployed for a customer and how they get configured for the business need. Importantly it would also hold the user security related information. This is the primary application database. This contains the data structures to hold the application data. And all the business rules are implemented as Stored Procedures / Functions and Views and are present in this database. The Audit trail related data structures are part of this database. This database contains the metadata related to Workflow configuration of various business functions. Also the configuration information is maintained here. This database contains the work tables / temporary data processing tables that would be used by the Stored Procedures and other objects of SCMDB. This database contains the temporary data structures that would be used in the collaboration integration sequences.

SCMDB

ENT_AUDIT WFM40

SCMTEMPDB

COLLAB

Page | 1

Ramco Systems. All rights reserved. All trademarks acknowledged.

Ramco

Systems

Limited

www.ramco.com

Design Principles
A few important design principles that are followed during the development of the database objects are listed below: (The detailed Design and Coding guidelines are part of separate guidelines documents) 1) All the OLTP tables would be normalized appropriately. 2) Native data types would not be used. User Defined Data types repository would be created and they would be used in the Data Tables design and all the objects that are referring to them. 3) Unicode compliant Data types would be used always. 4) All Tables would identify proper Primary Keys and have appropriate indexes defined as per the business function needs. 5) Timestamp column should be used wherever required to manage the user concurrency. 6) SQL Functions should not be used in where clause of a query. If needed, can be used on variables but strictly not on columns in the table.

Data Dictionary
There would be a separate Data Dictionary document for every Business function and that would consist of a wide array of metadata information, ranging from classic entity-level data definition, to detailed attribute-level descriptions of data structures.

Page | 2

Ramco Systems. All rights reserved. All trademarks acknowledged.

Ramco

Systems

Limited

www.ramco.com