hi guys,
some questions i would like to ask:
1. when i do a backup, will the user ids be backup as well?
2. another thing is, is it recommended to create a database with a lot of schemas? let's say around 20++. my scenario is like this. i will be handling a database that stores data for over 20 comp. the comps is handled by 1 HQ. that means, the HQ will be handling the database for the child comps.
the comps will share some data from some tables. i've do some checks, if i create schemas, i still can do referencing (foreign key) from a table from schema 1 to a table in schema 2. but i don't think i'm able to create a foreign key to reference a table to another database.
reason y i chose schema is not to duplicate the tables that is shared among the comps. that's y i've been wondering whether schema is the rite way to go? please advice coz i nd some opinions from u guys out there. thanks in advance.
some questions i would like to ask:
1. when i do a backup, will the user ids be backup as well?
2. another thing is, is it recommended to create a database with a lot of schemas? let's say around 20++. my scenario is like this. i will be handling a database that stores data for over 20 comp. the comps is handled by 1 HQ. that means, the HQ will be handling the database for the child comps.
the comps will share some data from some tables. i've do some checks, if i create schemas, i still can do referencing (foreign key) from a table from schema 1 to a table in schema 2. but i don't think i'm able to create a foreign key to reference a table to another database.
reason y i chose schema is not to duplicate the tables that is shared among the comps. that's y i've been wondering whether schema is the rite way to go? please advice coz i nd some opinions from u guys out there. thanks in advance.