1. Home
  2. Point-Of-Sale Software
  3. Recalling transactions to void/database size

Recalling transactions to void/database size

I am having this problem with voiding transactions: it takes around 2-3 minutes for the system to even recall the transactions for the day before it lets me browse them to void the transaction. I have a database that is around 1.5 Gb large. I am using MSDE and I DEFINITELY don't want to upgrade to SQL Server. I only have 1 lane so I don't really need a full blown SQL server for my application. I would imagine that part of the reason why my database is slowing down is the size. I am running a relatively slow server (one lane just doesn't justify the cost to run a faster one).

I want to shrink the database...and what I mean by shrink is remove and archive the transaction history and any other extraneous information. There are 3rd party applications for that, but once again, I can't justify paying for a 3rd party app when it should be something that is integrated in the current program. What are my options?

I was thinking of just backing up the main database and then using the offline database to build up a new database with only item information. Is this possible? I would imagine that the offline database doesn't store ANY transaction history, except what is used when the main is offline, then purges the transactions to the main database when it comes back online?

Does anyone have any ideas? Is my logic flawed? Please respond in plain english, I have very limited knowledge of MSDE/SQL server and neither am I a database programmer. Thank you very much :)

Reply to
mkim797
Loading thread data ...

mkim797,

How much RAM in the machine? We like at least a gigabyte.

Have you re-indexed and checked (in SO Administrator) the database recently? Backup before doing either.

Reply to
Jeff

Reply to
ozzie

you can run a shrink database command on the database to remove unnecessary empty space. Usually the impact is small, but noticable.

Do not recall transactions to void. It will not accomplish what you want and it will override the main purpose of a POS system. That data is gold.

The size limit for MSDE is 2 gig. The next version the limit will be 4 gig I think. The next version is SQL express and should be available in November sometime. Yes, it is still free.

Reply to
root

I recall transactions to void a transaction in the case where I have finished a transaction with a customer who changes his/her mind and decides not to purchase a product. Or sometimes I need to void the credit card transaction because they wanted the item rung up as a debit transaction.

Next, I am running only 128Mb of ram. Yes, I know this is a measly amount of ram. Once again, I wish to rectify this situation without purchasing more ram or purchasing 3rd party software.

Thank you all for the replies.

-Mark

Reply to
mkim797

Mark,

So what's your question? You've been told to try re-indexing, if that didn't fix it, add RAM. Not much RAM in your system is going to operate slowly, as you have found. Right now, RAM is extremely cheap, ~$100 for a gigabyte.

128mb of RAM is barely enough to run Win 98, let alone W2K or XP. Even Microsoft, which _always_ low-balls RAM and processor speed, says a _minimum_ of 256mb for RMS from;
formatting link
System Requirements Use any PC-compatible system running Microsoft Windows 98 SE, Windows ME, Windows 2000 Professional Edition, or Windows XP (all versions). It is recommended the system have a Pentium 500-MHz or faster processor, 8 GB of free hard disk space, and 256 MB or more of RAM.

Either buy the archive add-on, delete your information or add RAM.

Reply to
Jeff

Mark

Refer to Knowledge Base Article #903749. It speaks to this issue.

KN

Reply to
Ken Nelson

Mark, I have seen this problem with large databases. I would recommend using a utlity provided by Retail Realm that will archive your data into an archive database. This is the only real solution I have had success with. You could make a backup of your database then purge the data using some delete queries. Primarily you want to purge out the Journal table which is the table that usually grows the largest.

Casey Hanson New West Technologies

Check out amaz> Mark

Reply to
CaseyHanson

Ok here is the cheap way out of this. Back up the database. Then delete all sales history in the System Admin/ Database. You will have a new clean database with all your items and only loose sales history. You can then backup your "current" database and restore the old one if you want to look at past history. When your done just mount the "new" database again and your off to the races. mt

Reply to
Masta T

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.