Two Pro4 Servers accessing One DB?
Posted 06 July 2006 - 05:58 AM
The reason I am asking this is that I can see benefit in load balancing our pro4 users across two servers with two independent code sets that have been mirrored.
Limiting the impact against a hardware failure
Better batch processing capabilities
Greater processing capabilities.
Posted 06 July 2006 - 06:27 AM
The only thing you have to consider is that @TERM will hold a unique value per pro-iv server, but the two servers might give you the same @TERM value. To overcome this problem, our logon screen adds a 1 or a 2 (depending on if started up from server 1 or server 2) to @TERM, to make it unique again. We use a lot of workfiles keyed on @TERM.
Posted 06 July 2006 - 04:52 PM
Have you run into this? If so, how do you handle it? Thanks. Mark Dexter
Posted 07 July 2006 - 06:27 AM
It does generate record locks. The mosty used workaround is that the start function of a transaction will update the counter, do a COMMIT(), and start with the data entry screen. If the user cancels, the counter is lost.
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users