- software will used in many countries ..each country products differ from others and these products will be available in 2 languages: english, the native language .
- i start designing a DB for each country have its own pdts in english and its own language .
- is there better way to keep all data of products, countries, languages in one place but separated from eachothers?? .
- how can i link all these DBs together and modify them easily?
First, it appears that English may not be your first language so I am going to reword your question and then focus on it from there.
What structure should I use for designing my database? Should I use more than one database, and if not, how do I accomplish this with the software?
Software will be used in multiple countries. Each country will have products within the database that differ from the other countries, and the products will be available in two languages. The main language is English.
I have already started designing a database for each country that will have its own products in English and also the products in the native language.
How can I link these two different databases together and modify the content within them easily?
Is there a better way to keep track of all of the products, countries, languages, etc. within one database but maintain the organized format I am seeking?"
The answer is that you should likely use one database for all of this. If you simply change the table name for the country or language in your software, all of the other fields will be the same.
english_products table: id, name, price, description, qty native_products table: id, name, price, description, qty
In your software, I suggest simply providing an option to switch countries and use different table names based on the country. So, you would use
SELECT english_products for one country and
SELECT native_products for another.
Changes to either table could be accomplished by making a change in your software configuration to use a different table name instead. So, your code would be
SELECT [table_name] where the [table_name] is specified in the software.
I would suggest only using a single database regardless of your other design decisions.