Creating a Database for MySQL, Microsoft SQL Server, Oracle, or PostgreSQL

When you select mySQL, Microsoft SQLServer, Oracle, or PostgreSQL as your database engine used with LNDB, you will usually want to work with the Information Technology (IT) personnel at your organization or with external database hosting partners. Unless you have sufficient experience and expertise for administering these database servers, running them yourself is often very time consuming and distracting.

LNDB requires a "database" instance to be created on a mySQL, Microsoft SQLServer, Oracle, or PostgreSQL database server. This will (in most circumstances) only be used by LNDB. This database instance can also be referred to as a "catalog" or "service". You should work with your IT personnel or hosting partner to get this database/catalog/service created on the database server before you begin using LNDB.

When configuring LNDB to interact with mySQL, Microsoft SQLServer, Oracle, or PostgreSQL you will refer to the database/catalog/service by its name. This enables LNDB to know where to create its tables and populate (insert) the data into the database server. This database/catalog/service can be named anything you choose, but you may wish to choose a name like "LNDBDatabase" or "LoggerNetData" so that its purpose will be clear to all parties involved.

The database/catalog/service name is specified in the Select Database screen of the LNDB Manager. Selecting the wrong database name from the server (such as system databases or other databases that exist by default) can have highly unfavorable results. Please work carefully with the appropriate personnel to ensure this is configured properly.