Developer forum

Forum » Development » shared database on local and live server?

shared database on local and live server?

E-mail notifications
Rasmus Thirslund
Reply
Posted on 24/01/2012 10:26:38
Hi everyone

We want to have two solutions, one on local, one on .net, both on the same machine.

We are considering letting them share the DW tables, so we only have to update the files, when we want to present changes on the public accesible solution to the client...

Does anyone know if there are any problems related to a setup like this - any pitfalls or anything we have to beware of???

Best regards

Rasmus Thirslund

Replies

 
Jeppe Eriksson Agger Dynamicweb Employee
Jeppe Eriksson Agger
Posted on 24/01/2012 10:51:04
Reply

Hi Rasmus

I would not do this if one of the solutions is a live one. Especially if you change any data other than templates and such. That said, it's definitely possible to have two solutions use the same DB but you need to make sure that both solutions are the same version, otherwise you run the risk of updating the DB to a state that the oldest version can't use. Also remember that Dynamicweb caches a lot of objects to reduce the number of DB connections and these objects are cached on a per-application basis, so if you change some value in Dynamicweb then this change is reflected on the solution that made it, but not on the other -- until that solution is forced to reload the cache.

Those are the biggest issues I can think of off the top of my head, but there are probably other issues.

- Jeppe

 

You must be logged in to post in the forum