greetings from Colombia, south america.
I have an app built with MySQL 5.0.88 in a Windows 2003 Server (DB1).
The server is on site A, and the company has another location (site B).
In site B the internet (we have a VPN) is pretty bad, so, it's often to see the site B without access so the app.
Somebody says that if it's possible to have an offline/local DB2 at site B, so it can be used when the conn goes down. In this case, both DB1 and DB2 would be running, executing queryes separately.
When the conn goes up, somehow it would be nice to sync DB1 and DB2, even knowing that they could've been working in the same tables, tables with autoincrement PK's.
is there a solution for this scenario ?
thanks
I have an app built with MySQL 5.0.88 in a Windows 2003 Server (DB1).
The server is on site A, and the company has another location (site B).
In site B the internet (we have a VPN) is pretty bad, so, it's often to see the site B without access so the app.
Somebody says that if it's possible to have an offline/local DB2 at site B, so it can be used when the conn goes down. In this case, both DB1 and DB2 would be running, executing queryes separately.
When the conn goes up, somehow it would be nice to sync DB1 and DB2, even knowing that they could've been working in the same tables, tables with autoincrement PK's.
is there a solution for this scenario ?
thanks