I've got a solution designed as a separation model where data is split among 6 files and I am working on an upgrade.

I'm planning to consolidate those 6 files under three with the following criteria:

• One file with messages because it gets quite big in size
• Another file with all of the value list tables I use because there are quite many and they require relationships only for value lists
• A file with the rest of the data

Is this a good way to distribute the data? would be better a single big file, even if it grows up to 800MB? which design criteria would you apply with this scenario?

Thanks,

The Separation Model refers to having the UI in one file and data in another file or files. I can't speak for your proposed setup.

6 hours ago, naio said:

Is this a good way to distribute the data? would be better a single big file, even if it grows up to 800MB? which design criteria would you apply with this scenario?

 

800MB is not big.

But consider backup efficiency too in your equation.  Split out the static tables from those whose data changes often and you'll make backups faster and lighter on the disk space consumption.

On 3/7/2016 at 0:06 AM, Wim Decorte said:

800MB is not big.

But consider backup efficiency too in your equation.  Split out the static tables from those whose data changes often and you'll make backups faster and lighter on the disk space consumption.

Thanks Wim, your advice sounds smart, I'll follow it.