Good afternoon.
I am currently developing an epos system, and have been thrown a curve ball.
The Story so far:
Each Epos terminal connects to the server over a standard Network.
The server is running SQL 2005 Express edition.
As each transaction is put through the epos systems, the transaction details are recorded to the database on the server.
Nothing unusual so far.
However, 9 time out of ten, the server will also be a touch-screen epos, just like the others.
What happens if the server (or 'Master Till') goes down?
In the current scenario, that means all of the epos systems will also go down, due to them not being able to talk to the server.
I need all remaining systems to keep running.
as I understand it, this would have been an ideal scenario for SQL Replication, however that is not possible with Sql 2005 Express edition.
This is a low cost high volume piece of software, so bundling sql server Workgroup ed. is out of the question.
Any Ideas?
I am currently developing an epos system, and have been thrown a curve ball.
The Story so far:
Each Epos terminal connects to the server over a standard Network.
The server is running SQL 2005 Express edition.
As each transaction is put through the epos systems, the transaction details are recorded to the database on the server.
Nothing unusual so far.
However, 9 time out of ten, the server will also be a touch-screen epos, just like the others.
What happens if the server (or 'Master Till') goes down?
In the current scenario, that means all of the epos systems will also go down, due to them not being able to talk to the server.
I need all remaining systems to keep running.
as I understand it, this would have been an ideal scenario for SQL Replication, however that is not possible with Sql 2005 Express edition.
This is a low cost high volume piece of software, so bundling sql server Workgroup ed. is out of the question.
Any Ideas?