Elliott Database Naming Convention
Release Date: 06/30/20
Version: 7.x & Up
General speaking, Elliott's data is stored in <ElliottRoot>\DATA or DATA_99 folders. Where <ElliottRoot> is like "M:\Elliott8" and "99" can have the value of 02-99 that represent the Elliott company ID. The DATA folder represent company ID 01. To access these Elliott data through PSQL (Zen) engine, Netcellent provided DDF files which define the schema of the Elliott data in the DATA* folders.
There are also some database files in <ElliottRoot> folder. However, they are not significant before Elliott 8.5. After Elliott 8.5, especially Elliott 8.6, there are significant more data in the <ElliottRoot> folder. Therefore, Netcellent start to distribute DDF files for the <ElliottRoot> since Elliott 8.5 to allow relational database engine to access.
Listed below are examples of standard Elliott database naming conventions for current and future versions of Elliott. The naming convention implies (1) Elliott Database Version; (2) Whether the database is for DATA or ROOT; (3) Whether the database is for Elliott, SOAP Web Services, or Elliott Commerce Web Services:
- ELLIOTTDATA - V7.X DDF
- ELIDATA - V8.0-8.2 DDF
- ELI85DATA - V8.5 DDF
- EWS85DATA - V8.5 DDF for SOAP Web Services to operate on 24x7 basis which makes it difficult to update the DDF
- EEC85DATA - V8.5 DDF for Elliott Commerce (REST) Web Services to operate on 24x7 basis which makes it difficult to update the DDF
- ELI85ROOT - V8.5 DDF for <ElliottRoot> directory data
- EWS85ROOT - V8.5 DDF for <ElliottRoot> directory data for SOAP Web Services to operate on 24x7 basis which makes it difficult to update the DDF
- EEC85ROOT - V8.5 DDF for <ElliottRoot> directory data for Elliott Commerce (REST) Web Services to operate on 24x7 basis which makes it difficult to update the DDF
- ELI86DATA - V8.6 DDF
- EWS86DATA - V8.6 DDF for SOAP Web Services to operate on 24x7 basis which makes it difficult to update the DDF
- EEC86DATA - V8.6 DDF for Elliott Commerce (REST) Web Services to operate on 24x7 basis which makes it difficult to update the DDF
- ELI86ROOT - V8.6 DDF for <ElliottRoot> directory data
- EWS86ROOT - V8.6 DDF for <ElliottRoot> directory data for SOAP Web Services to operate on 24x7 basis which makes it difficult to update the DDF
- EEC86ROOT - V8.6 DDF for <ElliottRoot> directory data for Elliott Commerce (REST) Web Services to operate on 24x7 basis which makes it difficult to update the DDF
The DATA represent Elliott data in company 1. For other companies, we add two digits (a numeric number like 99) at the end. So ELI86DATA means this is Elliott 8.6 database for company 01 and ELI86DATA02 means this is for company 02.
Note: ELI85ROOT, EWS85ROOT & EEC85ROOT are based on DDF files in <ElliottRoot>\Bin85\DDFROOT folder and subfolders. On the other hand, ELI86ROOT, EWS86ROOT & EEC86ROOT are based on DDF files in <ElliottRoot>\Bin86\DDFROOT folder & subfolders. While the DDF folder paths are different, but in reality, they are the same DDF files.
For Elliott 7.x, we typically name the database as follows:
ELLIOTTDATAELLIOTTDATA02...ELLIOTTDATA99
Where 02 - 99 represents the company ID. ELLIOTTDATA represents company 01. The DDF is based on the folder <ElliottRoot>\DDF40.
For Elliott 8.0 - 8.2, we typically name the database as follows:
ELIDATAELIDATA02...ELIDATA99
Where 02 - 99 represents the company ID. ELIDATA represents company 01. The DDF is based on the folder <ElliottRoot>\Bin\DDF40.
For Elliott 8.5, our database use string for document field, vs. before 8.5, we use numeric for document field. All string fields are case insensitive to facility searching. We typically name the database as follows:
- ELI85DATA - based on DDF in <EllliottRoot>\Bin85\DDF40
- ELI85DATA02 - based on DDF in <EllliottRoot>\Bin85\DDF40
- ...
- ELI85DATA99 - based on DDF in <EllliottRoot>\Bin85\DDF40
or
- EWS85DATA - based on DDF in <EllliottRoot>\Bin85\DDF40\WSDDF. This for Elliott web services. The reason we have a separate folder for web services is because it will open Elliott's DDF on 24x7 basis and make it difficult to update. General speaking, the DDF used by web services is not required to update unless the web services is changed as well.
- EWS85DATA02 - based on DDF in <EllliottRoot>\Bin85\DDF40\WSDDF. Same as above.
- ...
- EWS85DATA99 - based on DDF in <EllliottRoot>\Bin85\DDF40\WSDDF. Same as above.
or
- EEC85DATA - based on DDF in <EllliottRoot>\Bin85\DDF40\ECDDF. This for Elliott Commerce (REST) web services. The reason we have a separate folder for Elliott Commerce (REST) web services is because it will open Elliott's DDF on 24x7 basis and make it difficult to update. General speaking, the DDF used by Elliott Commerce (REST) web services is not required to update unless the Elliott Commerce is changed as well.
- EEC85DATA02 - based on DDF in <EllliottRoot>\Bin85\DDF40\ECDDF. Same as above.
- ...
- ECS85DATA99 - based on DDF in <EllliottRoot>\Bin85\DDF40\ECDDF. Same as above.
Where 02 - 99 represents the company ID. ELI85DATA represents company 01. The main change in Elliott 8.5 DDFs from prior versions is that all Elliott document numbers are assumed to be in string format where alphabetic values can be stored. Additionally, we now have added various NSCTLFIL_9999 table definitions so you can access each NSCTLFIL record with proper column definitions. Even if you are using Elliott 8.5 but did not convert your database to alphabetic document format, then you should continue to use the Elliott 8.0 - 8.2 DDF databases (i.e., ELIDATA.)
For Elliott 8.6, it is mostly identical to 8.5 database, except the primary key string fields are case insensitive to correct an issue we have we 8.5 database. We typically name the database as follows:
- ELI86DATA - based on DDF in <EllliottRoot>\Bin86\DDF40\STDDDF
- ELI86DATA02 - based on DDF in <EllliottRoot>\Bin86\DDF40\STDDDF
- ...
- ELI86DATA99 - based on DDF in <EllliottRoot>\Bin86\DDF40\STDDDF
or
- EWS86DATA - based on DDF in <EllliottRoot>\Bin86\DDF40\WSDDF. This for Elliott web services. The reason we have a separate folder for web services is because it will open Elliott's DDF on 24x7 basis and make it difficult to update. General speaking, the DDF used by web services is not required to update unless the web services is changed as well.
- EWS86DATA02 - based on DDF in <EllliottRoot>\Bin86\DDF40\WSDDF. Same as above.
- ...
- EWS86DATA99 - based on DDF in <EllliottRoot>\Bin86\DDF40\WSDDF. Same as above.
or
- EEC86DATA - based on DDF in <EllliottRoot>\Bin86\DDF40\ECDDF. This for Elliott Commerce (REST) web services. The reason we have a separate folder for Elliott Commerce (REST) web services is because it will open Elliott's DDF on 24x7 basis and make it difficult to update. General speaking, the DDF used by Elliott Commerce (REST) web services is not required to update unless the Elliott Commerce is changed as well.
- EEC86DATA02 - based on DDF in <EllliottRoot>\Bin86\DDF40\ECDDF. Same as above.
- ...
- EEC86DATA99 - based on DDF in <EllliottRoot>\Bin86\DDF40\ECDDF. Same as above.
Where 02 - 99 represents the company ID. ELI86DATA represents company 01. Like Elliott 8.5, Elliott 8.6 DDF assumes all document numbers are stored in string format. Even if you are using Elliott 8.6 but did not convert your database to alphabetic document format, then you should continue to use the Elliott 8.0 - 8.2 DDF databases (i.e., ELIDATA.)
The following sample screen shows how ELI86DATA03 is defined in the database properties of PSQL Control Center:
Note that we use the local path on the PSQL server to define the location of <ElliottRoot>. For example, if your <ElliottRoot> normally refers to M:\Elliott7, then in our example above the corresponding local path is D:\Acct\Elliott7.
Elliott 8.6 also requires a special database name:
ELI86ROOT
Where the DDF is based on the folder <ElliottRoot>\Bin86\DDFROOT\STDDDF. This database contains the database layout for *.BTR file <ElliottRoot>. Typically, these are Report Desk data where the report definition applies to all companies. See the following sample screen for how ELI86ROOT is defined in database properties:
If you follow the above recommended default naming convention, it will make the setup of Report Desk easier, but you don't have to -- especially if you have a customized DDF.
Beginning with Elliott V8.6, it is necessary to associate the database names in PSQL Control Center to the company data directories in order to support the Report Desk feature.
Please note, we also support the following root folder database name:
EWS86ROOT
EEC86ROOT
Please see the following related article for Elliott 8.6 Database Convention:
Create Elliott Databases by Using EL850DB.EXE or EL860DB.EXE Utility
You can create Elliott 8.5 or 8.6 databases with the standard naming convention by using the EL850DB.EXE or EL860DB.EXE utility. Please refer to the following KB article for more detail:
JEG/EMK
Related Articles
Elliott 8.6 Database Convention & Report Desk/PowerSearch
Release Date: 08/27/2021 Revision Date: 4/11/2022 Version: 8.6 Elliott 8.6 Database Naming Convention Elliott 8.6 now supports Report Desk and PowerSearch, features based on the PSQL relational database engine. Databases must be created for Report ...Installation of ElliottService, NETcellent’s Web Services for Elliott
Installation to New Server 1. Server Location: Decide if you are going to install the web services on the same machine running Elliott, or a separate server on your network. The machine must reside on your network. 2. Set Up Server: If your ...A Support Case of Migrating to Different Version of DDF
Release Date: 4/24/19 Version: All Q - I've been asked to set up UPS Worldship to access customer shipping addresses in Elliott. I've run into a problem mapping City, State, and Zip fields to Elliott. Looks like Elliott concatenates these fields to ...An Example of DDF Files in DATA Folder that Can Confuse PSQL
Release Date: 04/11/2024 Version: All Q - I tried to access Elliott Item master column ITEM_CASE_SIZE in Report Desk. In one of the Report Desk reports, I wanted to drag ITEM_CASE_SIZE to the report body. But I can't find that column under the ...A Comparison of Elliott 7.5, 8.2, 8.5, 8.6 and 8.6 V2 DDF Files
Release Date: 11/15/2022 Last Updated: 06/25/2024 Version: 7.5 & Up DDF Files are used to define the PSQL database schema. Generally speaking, we distribute five different types of DDF files for different versions of Elliott releases: 7.5 DDF: These ...