Question

Currently we have embedded Derby DB installed on every developer computer. I have some problem according to this:

Derby supports only one connection simultaneously. I have to shut down WAS to examine DB structure and content with any Visual tool. Also I have no idea if it is even possible to use any profiler to watch what’s going on with DB when Commerce works. Do you use Derby? Does every developer in your team has his own database or DB is centralized and shared? Any possible disadvantages if I replace all developers Derby with local DB2?

Was it helpful?

Solution

There are 2 common ways to do this for the development environment. The most straightforward is to install DB2 as the developer database on the local machine. There are no glaring disadvantages to this approach except that you have to manage each database and push updates to it regularly. THe biggest advantage is that you end up with the same database in your developer environment as you would have for your production environment.

The second approach would be to install a centralized DB2 instance. This is easier to manage but you run the risk of one developer's changes poisoning the DB for the rest of the team.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top