How to deal with DB Size Limitations???

Retail Realm has an archiving utility that keeps old data without deleting. You may want to consider this as well as deleting journals. Craig

The 60% of the DB is the Journal. I delete the journal < "mydate" in the store and does not affect the data from HQ

Randall

"Asad" wrote:

aHello All,

what i know of RMS v2.0 and its embedded SQL Server 2005 Express Edition is that it can support a maximum of 4 GB DB size.

My question is that how can I maintain data at SO and HQ after it approaches this limit without losing any data?

If old data purging is the only solution, how can i keep it safely isolated yet readily accessible?

Secondly, does purging at SO also remove data in HQ? If yes, how to avoid such a situation?

Everyone is invited to suggest me appropriate answers to my questions, as well as add some extra dimension for benefit of all. Waiting for workable solutions. Thanks

Jeff I believe SQL 2005 workgroup looks like a viable option. But just a few concerns:

1. "What would happen to RMS SO user interface if the size of 'customer' table go beyond 1GB (catering to 2Mill customers records)." ? i.e.

- How much fetching time would RMS Customer lookup screen would take in order to find from such a huge sized table?

- Are there any options to optimize searching in RMS store databases in such cases? Any comments are welcome.

Regards, Mohs> Asad,

SQL 2005 Workgroup Edition or higher. All versions offer unlimited data growth. SQL2k5WE starts at ~$1000 USD