There are several scenarios where you do not want GeneXus to reorganize your application database but tell him that it is already reorganized (i.e. it already has the expected schema):

• You are converting your Knowledge Base to a new GeneXus version

You want the newly converted KB to point to the Database you already have. There is no need for reorganizations.

• A new developer is added to a team where all developers “point” to the same Database

Someone in the team is responsible for updating the Database. The new guy does not have to.

• All environments in a given Version point to the same Database

Your application must be implemented in different languages (one in each environment) but for the same DBMS. Why point to a new Database?

In most of the above situations you set the Reorganize server tables property to No to avoid the reorganization. But this is not exactly what you need.

As of GeneXus Evolution 1 Upgrade 1, there is a new option in the Tools/Advanced menu named “Mark database as reorganized” that was designed to solve the above scenarios faster and easier. Why? GeneXus does not scan the Database structure for changes or figures out how to move data between the old and new schemes.

Give it a try, it will save you time.
Take a look at the detailed information too.

Hoy resurgió el tema de mantener la historia de las reorganizaciones en GeneXus. Esta vez fue en el foro de GeneXus Rocha. Cuál es el enfoque más práctico?

(more…)