we have web application which stores information in backend SQL 2014. currently the way is set up that central database stores all key information for the customers and then we have seperate database for each customers. Now tables structure for each customer's database is same for particular product. e.g. if one customer1 DB has tables almonds, oranges and Customer2 DB has tables lemon, citrus the structure is same just table is different depends on what kind of famrs they have. This tables belongs to Product 1 they purchased. This tables doenst have any reference to key since it will have redundant data. In future if they will buy second product, Table structure for the product will be different then product1 but it will be same along each customers database.Currently we are small in size but expecting to grow very very big with all kind of spatial data and Raw data with images , GIS data etc..Also with Different prodcuts offering like product1, product2, product3 etc..question is ..Is this good database design for future reference to hand heavy load? Should move forward to have one big database contains all information?Also keeping central Database on SQL and each customer DB keep on 'Not Only SQL' platfrom ( MongoDB, Cassendra) will be good approach?
Single Database Vs Multiple Database on SQL Server
database design;sql;sql server;multitenancy