====== Datastore Setup ======

You might have noticed that I make a distinction between //Database// and //Datastore//. The term //Database// is used when refering the physical middleware and the technical infrastructure, e.g. the PostgreSQL or Oracle software and servers. The term //Datastore// on the other hand is used for a BPS entity living in a database, often also refered to as //Schema//. There may be datastores (or schemas) from other applications living side by side with BPS in a certain database, or several BPS datastores in one database.

When you acquire licenses for BPS, they are valid for 3 instances:

    * A **production** datastore where the real business takes place.
    * A **quality** datastore where new releases of the application are checked before going live, and which is used for education and training.
    * A **testing** datastore for development and experiments.

You need not create them all depending on your needs. The naming of the instances and objects is basically free within the limits of the database software. Here is a suggestion for a company where one BPS installation covers all departments:

^                       ^ Production    ^ Quality       ^ Testing       ^
^ Database name (1)     | prod          | qual          | test          |
^ Data tablespace (1)   | prod_dat      | qual_dat      | test_dat      |
^ Index tablespace (1)  | prod_inx      | qual_inx      | test_inx      |
^ Owner user name (2)   | prod          | qual          | test          |
^ Guest role (3)        | prod_gst      | qual_gst      | test_gst      |
^ User role (3)         | prod_usr      | qual_usr      | test_usr      |
^ Normal user names(2)  | prod//nnnn//  | qual//nnnn//  | test//nnnn//  |

**Notes:**

(1) Need to be created beforehand with the tools of the database software (Command line, PgAdmin III, Oracle Enterprise Manager).

(2) Will be created in the [[createdb|Create datastore wizard]].

(3) Automatically by the [[createdb|Create datastore wizard]], as //owner//_gst and //owner//_usr.

(4) //nnnn// stands for a number with up to 8 digits which will be used within BPS as the User-ID for logging on. The full user name is only required if you need to do something directly in the database.