Microsoft Dynamics GP “12” Architecture Series

David Meego - Click for blog homepageThis is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.

Now that Microsoft Dynamics GP 2010 R2 has been released, the pundits and speculators are starting to focus on the next version of Microsoft Dynamics GP, codenamed GP “12”.

There have already been mention of some of the cool architecture changes coming with the mention of the GP “12” Web Client and with screenshots from the live demonstration of the early web client code.

My good friend, Mariano Gomez (MVP and The Dynamics GP Blogster) has been working with the Product Management team to bring together a summary of some of the architecture changes coming in this next release.

Starting with the GP “12” Web Client, which will allow existing Dexterity based windows to be displayed in a browser client using Silverlight. Mariano’s articles explains how the development team are separating the visual aspect of the windows from the rest of the runtime to allow the client to be rendered in a web client.  Please have a read of his posts to get a better understanding.

Mariano has also highlighted another one of the features coming with GP “12”. The removal of the hardcoded reliance on the DYNAMICS SQL database.  We will still have a system database, but it will not have to be called DYNAMICS.  This would then allow multiple Microsoft Dynamics GP installations on a single SQL Server instance. Currently, to install more than one installation on a single machine requires a new SQL instance for each installation.  Please read his post for more information on the Named System Database architecture.

This architecture change will make working with multiple installations much simpler. Companies can have test and live systems on one SQL Server, consultants can have multiple versions of Dynamics GP on their machines without needing multiple instances of SQL Server slowing their systems, hosting partners can run multiple customers on a single SQL Server instance.

Note: Support for the Named System Database Architecture will need some small changes to code for software developers, we will provide more information on these changes once the details are finalised.

Thanks to Mariano for publishing this great information.


17-Jun-2011: Changed references to Multi-tenant Architecture to Named System Database Architecture.

This article was originally posted on the Developing for Dynamics GP Blog and has been reposted on

5 thoughts on “Microsoft Dynamics GP “12” Architecture Series

  1. Hi David,
    Is there any plan for GP system to be independent of the SQL Server's server collation?  This means GP database do not have to use the same collation as the SQL Server's default collation.


  2. Hi Stanley
    I don't believe this is something that can be changed.  The issue is that the TempDB is in the SQL default collation and to perform joins from Dynamics GP databases with tables in the TempDB requires the collations to match.


Please post feedback or comments

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.