SQL 2000 Server advice
Hi Experts,
I am currenly upgrading my product database from a local copy to be run on a MS SQL Server.
This is fine but I still need to beable to have a table called "Mutisavers"
this table is what the PoS terminals use to control the mutisavers during each sale and seelcted coloums have to be wiped clean each time a sale starts.
What I would like to know is
A. Can I have Each PoS terminal "create" it's own copy of the mutisaver table
B. Can I use a Master table and when ever it changes the PoS tables would update
C. is this possiable with a SQL server ? or do I need to have a local copy of the mutisaver table? if so how can I keep it upto date with the SQL Server table.
Thanks fo the advice in advance
Drew
[789 byte] By [
Drew_gable] at [2007-11-11 8:45:12]
# 2 Re: SQL 2000 Server advice
The reason why each terminal need a copy is so it can do the caculations.
example
mutisaver code = 105
Mutisaver name = buy 4 for $5.00
Min Scan level = 4
PoS Scan level = 3
PoS Price = $5.00
The mutisaver will not kick in untill another item with the same mutisaver code is scanned.
I mean if you can recommed another way to do the mutisavers then I am all for it.
I am also assuming once I upgrade top the SQL server I will see speed inmprovments on ALL my PoS Terminals. ( number ranges from 5 - 100 terminals)
# 3 Re: SQL 2000 Server advice
As I said, I would use a single multisaver table with a column to indicate which records are associated with each terminal. Instead of doing SELECT * FROM multisaver, you can do SELECT * FROM multisaver WHERE terminal_id = x.
# 4 Re: SQL 2000 Server advice
That is fine BUT the mutisaver table holds all the mutisavers for Each product
So if Till 1 scans example eggs with mutsaver code 1
it would look like
TerminalID MutisaverCode MitiName MinScan PoSScan Value
001 03 Eggs saver 2 1 0.50
and then when PoS 2 scan it again will it then create a entry like
002 03 Eggs Saver 2 1 0.50
or will it not work?
# 5 Re: SQL 2000 Server advice
I don't understand why that is a problem. If it will work with a local copy of the table on each terminal, it can work with a centralized table. Perhaps it would help if you describe in detail what you're trying to accomplish with the multisaver table?
# 6 Re: SQL 2000 Server advice
ok.
basicly the muitsaver table holds all the information the the store has for each mutisaver
eg
Mutisaver Code = 101
Mutisaver Name = Eggs offer
PoS name = ** EGGS OFFER **
PoS Value = 0.50
Min Scan lebel = 3
PoS Scan level = 0
when ever the PoS scans a item's barcode eg 10001051 Small EGGS if the mutisaver tab has the mutisaver code in (101) it will add 1 to the PoS Scan level.
When the scan level and Min level match the mutisaver kicks in
Example
EGGS (small)
3 @ 0.50 1.50
**EGGS OFFER ** -0.50
and then the PoS Scan level resets to 0.
the only differance with the local copy is if any new mutisavers are added then they are not aware of it untill the PoS runs a update command.
that is why I want to have them in a central location (via the SQL Server)
