The thirty first feature they’ve announced is Named System Database.
In all versions of Microsoft Dynamics GP so far, the System database has been called DYNAMICS and could not be changed. This meant only a single instance (System and Company databases) of Microsoft Dynamics GP could be installed into an instance of SQL Server.
In Microsoft Dynamics GP 2013 this restriction has been removed in a new deployment. From this version onwards, the System database no longer needs to be called DYNAMICS but can be named during the installation/deployment process.
The diagram below shows the SQL Server requirements for both the current Single System Database Architecture and the forthcoming Named System Database Architecture;
This change has been facilitated on the SQL Server stage of the Microsoft Dynamics GP 2013 setup utility where there is now a radio button choice for the System Database Name. If Use default name is selected the System database will default to DYNAMICS, but if Enter custom name is selected a System database name can be entered;
The custom name must be a compliant SQL Server Name and can be up to 10 characters in length. This functionality allows for multiple system and associated company databases to be hosted within a single instance of Microsoft SQL Server.
Along with the ability to host multiple System databases, the Fabrikam, Inc. demo company deployment has also been changed to allow the database name to be changed which will allow each named System database to have the Fabrikam, Inc. demo database deployed;
This new feature is targeted at the following roles:
- System Implementer
- Business System Developer
Learning script available for download.