Posted By: ZippyV | May 28th @ 11:26 AM
page 1 of 1
Comments: 5 | Views: 575
ZippyV
ZippyV
Soapbox = Fail

In the future I will have to write an application in .net that will be run on a lot of terminals in a warehouse all connected to a central Sql Server. The db contains a list of tasks that the people in the warehouse will have to do. Every terminal shows that list. Now if a person on a terminal selects a task he will execute, how can I notify the other terminals that that task should not be shown anymore?

Someone told me to use MSMQ. I have never used it before but are there any other maybe .net solutions or something in Sql Server to solve this?
Updating all the terminals every 5 seconds is surely going to kill the database server.

harumscarum
harumscarum
out of memory
What version of sql server?
SlackmasterK
SlackmasterK
I write my OWN blogging engines
ZippyV wrote:


In the future I will have to write an application in .net that will be run on a lot of terminals in a warehouse all connected to a central Sql Server. The db contains a list of tasks that the people in the warehouse will have to do. Every terminal shows that list. Now if a person on a terminal selects a task he will execute, how can I notify the other terminals that that task should not be shown anymore?

Someone told me to use MSMQ. I have never used it before but are there any other maybe .net solutions or something in Sql Server to solve this?
Updating all the terminals every 5 seconds is surely going to kill the database server.



I'd just add a status column and have the lists refresh on a timer. This also keeps them up to date when a job is added or modified. Alternatively, have them double-check the status of that job before assigning it; display a message if it's been taken.

How many terminals? How much data do they need to pull per select? 
ZippyV wrote:
SlackmasterK wrote: How many terminals? How much data do they need to pull per select? 

About 15 terminals.
A task contains multiple images (max 100KB) so the workers can see what they have to get and the images are stored in the db.

{delurk}
You might try SQL Server Notifications? or even a SqlDependency? If you already have a connection to the DB it might be that the dependency might be what you want, although you need to handle the fact that the update is unlikely to be atomic.{/delurk}
page 1 of 1
Comments: 5 | Views: 575