Replica of Rooms & Resources - for web app

I’m creating a workflow form so that people can request to have a new room or resources created in the Rooms & Resources database.

My problem is that that the application has to run on our 2 app servers, not the server where the R&R database currently resides. To use @dbcolumn to build the list of current Rooms, Resources, Sites, etc. I am considering creating replicas of the Rooms & Resources database on my 2 app servers (clustered) since the browser can only do lookups to the current server. (you can’t tell the browser to go look for data on a different server)

My admins say that this is a bad idea but don’t provide much detail beyond “it causes issues”.

Could someone shed some light on why this would be a bad idea? We’re not going to send people links to the replicas on the app servers - and they’re in a separate cluster from the main R&R database.

As far as I can tell, the only people who could end up using the replicas would be people who try to open the Main R&R database while that server is down. People scheduling meetings from their notes client mail file wouldn’t go there at all.

Am I missing something?

Thanks

Subject: replica of Rooms & Resources - for web app

You should not put a replica of the reservation db

Should the Resource Reservations database be replicated? Should it be clustered?

http://www-1.ibm.com/support/docview.wss?uid=swg21097149

You have your answer. You said:

As far as I can tell, the only people who could end up using the replicas would be people who try to open the Main R&R database while that server is down.

Peoples are suppose to open serverA but you will end up for whatever reasons to peoples accessing serverB. Then, you would end up with big problems (Duplictae reservations for the same rooms).