frederico_fonseca wrote: Eric M Russell wrote:
For higher volume stores whose database can't fit within 10GB limit, we will deploy Standard Edition. Obviously Azure SQL would have advantages over on-sight deployments, but the issue is that we can't count on reliable internet connectivity many areas.
and then there are the "smart" companies - the limit of 10GB is per database - no limit in having 100 databases all with a single 10GB table on it. know of 2 software houses that did this to save clients costs.
So, how practical vertical partitioning across multiple databases would be depends on the application, and in this case it's a multi-user OLTP database. For a POS application that performs a lot concurrent reads and writes, it needs to have sub-second latency. Express Edition also a limit of 1 GB memory and 4 cores for which there is no work-around, so it would struggle scaling past 10 GB even if the per database storage cap were not there.
There is a historical data retention policy for the POS databases (payed off accounts, inactive customers, logging, etc.), so anything like reporting and dashboards point to the consolidated replica servers hosted in the corporate data center.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho