Professional Plus - Project Workflow

Just trying to ascertain the benefits of moving over the the Professional Plus version to manage projects in an SQL Database.  Was wondering what the workflow is as it doesn't appear to be very clear in the Enterprise User Guide.

The User Guide goes through:

• Setting up gINT Enterprise
• Moving Projects to gINT Enterprise
• Viewing an Enterprise Database
• Reporting with gINT Enterprise
• Exporting Data from gINT Enterprise

At no point does it mention 'Editing in gINT Enterprise'.  In fact it only refers to being able to "use Microsoft SQL Server for storing and reporting your gINT Data. Data is entered and edited in single project (.gpj) files and then moved to the SQL Server Database".

My understanding of this is:

• Upsize .gpj file to gINT Enterprise Database (will only work correctly if the Library file is the same and the database has to have the same structure - the only allowable differences are Additional Tables and Additional Fields - and the user upsizing the projects has to have CREATE rights in SQL Server)
• The Enterprise Database structure is determined by the first project upsized.
• Upsizing is done in two ways - retaining the original project association (eg job number) or appending them (but the hole ID's have to be unique)
• Editing is done in the .gpj version of any given project.  When the changes are made and approved the project is then upsized to the SQL Database.  All data currently in the SQL Database will be deleted and replaced with the contents of the .gpj
• All reporting can be done from the SQL Database - ie what was previously three separate projects can be stored in one SQL Database and reported on together
• If a Project has been upsized to the SQL Database and the original subsequently deleted / moved / archived this can be retrieved by downsizing the SQL Database version.

Is my take on this correct?

Thanks in advance