- Feb 20, 2009
- 2,272
- 182
- 265
Hi Guys,
Want to pick your brains a little, currently finalising the finishing touches to our epos system(till system) And we are now looking at affordability and scaleability(yes probably should of approached this first) However we are looking if anybody knows the best route to go down in terms of SQL. Things you need to know:
Every time a customer purchases our product they get a DB this db is scaleable dependent on each business however must be able to retrieve and hold data for 10 years, at the click of a finger. If its a nightclub it could have 10k worth of transactional data per day. But on the other hand a cafe could have 100.
Any advice as to costings or best route much appreciated.
Please keep in mind the DB also works locally and pushes at the next available network allocation.
Want to pick your brains a little, currently finalising the finishing touches to our epos system(till system) And we are now looking at affordability and scaleability(yes probably should of approached this first) However we are looking if anybody knows the best route to go down in terms of SQL. Things you need to know:
Every time a customer purchases our product they get a DB this db is scaleable dependent on each business however must be able to retrieve and hold data for 10 years, at the click of a finger. If its a nightclub it could have 10k worth of transactional data per day. But on the other hand a cafe could have 100.
Any advice as to costings or best route much appreciated.
Please keep in mind the DB also works locally and pushes at the next available network allocation.