1. Home
  2. Point-Of-Sale Software
  3. SO Database 4G limit

SO Database 4G limit

Hello everyone I need help! I am using Store Operation and my database is at

4.1G The limitations is 4G. Everynight I am shrinking the database to keep things going. Is there anything I can do the lower the size. I remeber once I had a database that was corrupt. And it was sent off to Microsoft to be fixed. The RMS/SQL person at microsoft told me I had a 1G eventlog file that after he repaired the database he was able to remove the 1G evenlog. Do any one know how to do this? I would appreciate all the help. I will get the newest version of SQL but not right now. I am try to buy a few months.
Reply to
Jameer
Loading thread data ...

We reduce the database size very often for customers. Contact me via e-mail.

Marc Cott> Hello everyone I need help! I am using Store Operation and my database is at > 4.1G

Reply to
Marc Cotton

Hi Jameer,

I don't know about the eventlog file but in our database we removing records from fallowing tables on monthly bases:

- Journals no need to store journals more that 3 months old (unless you really need it), all transaction info will still stay in database but digital "picture" of the receipt will be deleted.

- TimeCard every time when cashier log in \ log out to register that is recorded in this table.

- RecordDeletedLog every deleted line in RMS is recorded in this table.

DELETE Journal WHERE Time The limitations is 4G. Everynight I am shrinking the database to keep things

Reply to
Arthur Hanusek

We have an Archive Utility that may be useful for you.

Reply to
Afshin

hi Jameer, If the databse is grow I would recommend you to stop the using MSDE edition of SQL server instead use the sql server personal or standard edition. Regarding the log file, I am writing below some commands apply this but make the backup first.

go to query pane and run this: select * from sysfiles (then get the files name)

ALTER DATABASE SET RECOVERY SIMPLE; GO -- Shrink the truncated log file to 1 MB. DBCC SHRINKFILE (QSDB_Log, 1); GO -- Reset the database recovery model. ALTER DATABASE SET RECOVERY FULL; GO

"Jameer" wrote:

Reply to
Akber Alwani

We faced this problem ourselves over a year ago. What we did was make a backup, we shrank the database by eliminating transaction data. I recall all the inventory, products, prices were left intact. We simply kept the old version of the database for archive purposes.

The only other factor we needed to keep an eye on was the gift cards. We resold these gift cards/certificates in into the new database using a dummy account.

With this > hi Jameer,

Reply to
reng

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.