Application for grocery shop

Devendra Kumar

Client needs to create an application that will run in their 3 to 4 Grocery stores (just like Big Bazar)

Please guide me the best approach for storing their data. I shall use SQL Server.

Should I use same centralized database for all their grocery stores and fetch the data according to their machine name (an identical object) or shall I use seperate database for each store.

I thought:

If I use centralized database then it should be more difficult to take backup and restore the database and the database will also will bulky.

The most important thing that the admin should able to look all the data of all the stores.

Please suggest

Thank you

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Nitin Sontakke9y ago
Please be generally aware that you also have an option of creating a single db and spread tables across several secondary physical db files.
Nitin Sontakke9y ago
There is one more dimension to this. The master data and the transaction data. And for transaction data there is fear of growing.

My suggestion is, one database for master data and separate database for each store for each financial year.

You will need separate application for administration wherein you can dynamically connect to dbs and perform operations.

For analytics and MIS reports, you will need to do that anyway. Furthermore, from performance point of view, you can keep aggregated information in master db (of frozen past years) so that you don't calculate figures again and again.

Any questions / details required, please feel free to ping.