Dual running application using same database
-
I have an application that looks for the next job to process by querying a que table. If it finds a record it does some processing for the corresponding job and then removes that record from the que table. I want to have this application running on more then one server but I'm not sure the best way to keep each instance of the application from trying to process the same record in the que table. Somehow when one instance of the application begins processing a record in the que table it needs to flag that record so that another instance of the application will not process it. What is the best way to do this?
-
I have an application that looks for the next job to process by querying a que table. If it finds a record it does some processing for the corresponding job and then removes that record from the que table. I want to have this application running on more then one server but I'm not sure the best way to keep each instance of the application from trying to process the same record in the que table. Somehow when one instance of the application begins processing a record in the que table it needs to flag that record so that another instance of the application will not process it. What is the best way to do this?
-
I have an application that looks for the next job to process by querying a que table. If it finds a record it does some processing for the corresponding job and then removes that record from the que table. I want to have this application running on more then one server but I'm not sure the best way to keep each instance of the application from trying to process the same record in the que table. Somehow when one instance of the application begins processing a record in the que table it needs to flag that record so that another instance of the application will not process it. What is the best way to do this?
I've used something like this in the past to synch applications Using SqlDependency for data change events[^]
only two letters away from being an asset