SwapnilD, You should be able to handle this on the backend. You can write a DB trigger that copies the image "record" to the other database after it is committed. Considering that you did not describe the database software you are you using then we can't speak to this more specifically. I would have hoped that you would be using a 3 tier architecture, i.e., 2 servers to load balance web applications [1], another server that has the database [2] and the client software (browser,thin client, thick thick client, whatever) [3]. In this manner you only have to have one place a record has to be maintained. If you insist on having a DB on both servers then they should be mirrored. That is, the database software that is used will do this record copying function for you "automagically". MSSQL Server has mirroring capability; Oracle server has this functionality as well but this would be done either using Oracle's RAC technology or one of the 2 databases would be in a standby-read-only mode that is near-time, not real-time (it uses log shipping from the "hot" database to keep records up-to-date). Otherwise, as stated, the best way to handle this is by writing a database trigger on each database server that fires off a copy of the image record to the database on the other server after the image creation transaction is committed on whichever database server handles the inital transaction.

SwapnilD, You should be able to handle this on the backend. You can write a DB trigger that copies the image "record" to the other database after it is committed. Considering that you did not describe the database software you are you using then we can't speak to this more specifically. I would have hoped that you would be using a 3 tier architecture, i.e., 2 servers to load balance web applications [1], another server that has the database [2] and the client software (browser,thin client, thick thick client, whatever) [3]. In this manner you only have to have one place a record has to be maintained. If you insist on having a DB on both servers then they should be mirrored. That is, the database software that is used will do this record copying function for you "automagically". MSSQL Server has mirroring capability; Oracle server has this functionality as well but this would be done either using Oracle's RAC technology or one of the 2 databases would be in a standby-read-only mode that is near-time, not real-time (it uses log shipping from the "hot" database to keep records up-to-date). Otherwise, as stated, the best way to handle this is by writing a database trigger on each database server that fires off a copy of the image record to the database on the other server after the image creation transaction is committed on whichever database server handles the inital transaction.