New Store Database Size

I want to open a new store and copy the database from another store (as in
an HQ/Store setting).
The only store I have now has a 1GB database including transactions for two
years. When I used a backup to make a new database for the new store, then
delete the transactions, the database is still huge. How can I reduce the
database size?
Jason
Reply to
Jason
If you are simply trying to copy customers/items from one store to another, you ought to be able to copy the customer and item tables or at least export/import the customer & item data.
I could help the export/import method, but if someone else has a 'copy tables' method to offer, that would certainly be easier.
Tom
Reply to
Terrible Tom
I would want all of the other configuration data, like tax, register setups, file paths, etc... Not just customers and items. That would leave out all of the other linked tables anyway, like aliases.
I know storage is cheap, but network bandwidth is finite, and MSDE has a ridiculously low size limit...
On that note, who ships a POS software product that is only good for a couple of years in the average small business because the database gets too big. Microsoft conveniently forgot to mention in the sales literature that an expensive SQL Server upgrade will be required if you enjoy even an inkling of success (transactions).
Anyway, it seems like a bit of a hassle to export/import. There must be a way to do this (or shrink and existing database).
Jason
Reply to
Jason
There's quite a few ways to manage database size for either MSDE or SQLEXPRESS. I've found not to be a big problem even though we are a fairly busy store(average 90-100 transactions a day). At our current rate of database growth it will take 4 years before we even need SQLEXPRESS. Get with your partner to discuss the best options for your situation. Craig
Reply to
Craig
Get with my partner for the solution? The standard response is something like buy a full version of SQL for more than RMS costs. That doesn't make much sense...
With 250 transactions per day, I find that 1-2 years is all MSDE can handle, and that's what RMS ships with. Shame on MS for that... you can't dispute it.
Reply to
Jason
Technicaly sir if you want to reduce the DATABASE size you can delete the journal it takes 40% from the DB size the journal table at store DB (delete from journal where [time] < )
OR If you needn't the transaction history you can do delete transaction (from store operation admin-->connect --> database -->delete transaction) this will delete all transaction but will keep at master data (items, customers, quantity, prices, taxes, currency,?..)
Reply to
ENG RAMY
I want to open a new store and copy the database from another store (as in an HQ/Store setting).
The only store I have now has a 1GB database including transactions for two years. When I used a backup to make a new database for the new store, then delete the transactions, the database is still huge. How can I reduce the database size?
Jason
Reply to
Jeff
I would want all of the other configuration data, like tax, register setups, file paths, etc... Not just customers and items. That would leave out all of the other linked tables anyway, like aliases.
I know storage is cheap, but network bandwidth is finite, and MSDE has a ridiculously low size limit...
On that note, who ships a POS software product that is only good for a couple of years in the average small business because the database gets too big. Microsoft conveniently forgot to mention in the sales literature that an expensive SQL Server upgrade will be required if you enjoy even an inkling of success (transactions).
Anyway, it seems like a bit of a hassle to export/import. There must be a way to do this (or shrink and existing database).
Jason
Reply to
Jeff
Get with my partner for the solution? The standard response is something like buy a full version of SQL for more than RMS costs. That doesn't make much sense...
With 250 transactions per day, I find that 1-2 years is all MSDE can handle, and that's what RMS ships with. Shame on MS for that... you can't dispute it.
Reply to
Jeff

Site Timeline Threads

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.