Professional Plus - Project Workflow

Question

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

Kirk Johnson · Answer

Hi Paul, 
 
 I will just quickly summarize a couple of points. You do need to create the initial SQL DB by upsizing a gINT project (.gpj) . From there you can decide if you want to enter data directly into the SQL DB from the gINT SQL interface by opening the SQL DB directly in gINT or you can enter data in gpj files and then upsize them. The Idea would be to have a single standardized DB structure. I would encourage you to view the SIG seminar from February. It is very detailed and covers some overall concepts. 
 
 Best practices for Moving to gINT Professional Plus 
 
 SIG Learning Path 
 
 This will give you a real world example of a large organization with 1000's of projects that they migrated over time to a corporate Standardized SQL DB Structure. 
 
 If you need more info after looking at the SIG contact me and we can better assess what your company's background is with gINT. (IE how many projects, how many different structures, or you are brand new and have no or little existing gINT data.) 
 
 kirk.johnson@bentley.com send me your contact info and we can discuss your current usage of gINT.