How to use the database deployment tool for Windows 2003

This week I'm posting an instructional video on how to use the database deployment tool.

Why would I use the database deployment tool?

The database deployment tool was created to support those that need to run the Management Reporter services from a Windows 2003 machine.

  • It is required to create a new Management Reporter or data mart database.
  • It is required to perform any incremental updates to the Management Reporter database when new rollups are released.  
  • It is not required if you are running Management Reporter on Windows 2008, Windows 2008 R2, or Windows Server 2012 machine . If you are on a newer version of Windows Server you can stop reading now as this information does not apply to you.

Do I have access to this tool now?

The database deployment tool was released with Management Reporter 2012 Rollup 2 and is included in any release with Rollup 2 or newer.

  • If you have installed Management Reporter 2012 Rollup 2 the database deployment tool is on your server.
  • If you are still on the RTM or Rollup 1 release of Management Reporter you do not yet have the tool. It will be required to update your Management Reporter database to Rollup 2 or newer.

Where can I get more information on the database deployment tool?

The full documentation is available in the Installation and Configuration guide (MRforDynERPInstGuide_ENUS.pdf) on the Microsoft Download center here. The steps are under "Install Management Reporter 2012 on Windows Server 2003". 

How can I get a list of the available parameters? 

Run the following to get a list of available parameters:

            MRDatabaseDeploy.exe /?

Can you provide an example of the syntax needed to deploy a new Management Reporter database?

Below is an example of the syntax to deploy a new ManagementReporter database to a remote machine named SQLServer

            MRDatabaseDeploy.exe /action:create /databasetype:ManagementReporter /servername:SQLServer

            /databasename:ManagementReporter /databasecollation:SQL_Latin1_General_CP1_CI_AS

            /databasemasterkey:pass@word1 /servicedomainuser:contoso\mr_svc /adminuser:contoso\ryan

Note: This should be a single line of text with just spaces with parameters between each switch. I broke this into three lines to avoid the text being cut off.


Comments (3)

  1. Paul says:

    One quick question for clarification.  Should SERVERNAME just be the name of the server, or the SQL instance on which you want to install?  I.e. SERVERINSTANCE or just SERVER.

  2. CharG says:

    If you want to put the database on a SQL Instance, then you will need to specify SERVERINSTANCE.

  3. Sheri says:

    I have MR2.0.1700.66 on a windows 2003 server.  I loaded the console from the MR012CU8 install. I followed your video exactly using the windows 2008 terminal server that hosts the GP2010 client.  These were the results: The database deployment failed: with the words "could not deploy package". I have tried to locate more information on this subject – but the link you provided did not have any documents that contained a section called "Install Management Reporter 2012 on Windows Server 2003"  At any rate, any advice on how to proceed with this initiative would be greatly appreciated.  

Skip to main content