Release Management Console times out when launched

When the Release Management Console application is loaded, it defaults to the Traffic Overview page. If the database is not optimized, the query used to load such statistics may take a long time to execute. This may be due to recent updates such as an upgrade of your Release Management Server where existing statistics may now be staled.

By default, SQL Server already handles updating such statistics as needed. However, you can force this update manually in order to expedite the process.

If you are experiencing such delays, consider updating the Release Management database query optimization statistics as follow:

NOTE: To update the statistics on the database you should either be DBO of that database or SysAdmin on SQL instance.

Using SQL Server Management Studio

  1. Launch SQL Server Management Studio.
  2. Open a New Query window.
  3. Paste the following script snippet in the query window.
    USE [ReleaseManagement]
    EXEC sp_updatestats
    GO
  4. Press F5 to execute the command.

Using SQLCMD from the command line

  1. Save the following script snippet to a file called rm_updatestats.sql.
    USE [ReleaseManagement]
    EXEC sp_updatestats
    GO
  2. Locate the SQLCMD.EXE executable. It should be located in a path similar to C:\Program Files\Microsoft SQL Server\110\Tools\Binn, depending on the version of and location where your SQL Server is installed.
  3. Run the script file.
    1. Open a command prompt window.
    2. In the Command Prompt window, type: sqlcmd –S <myServer\instanceName> –i [Path]rm_updatestats.sql
      Where, <myserver\instanceName> is your specific server name instance; and [Path] is the location of the rm_updatestats.sql file.
    3. Press ENTER.

Verify the results by loading the Release Management Console again and observing the improvements.

Update – Feb. 6, 2015

NOTE: For customers with Update 4, we have added a scheduled job at the time of RM server configuration. If this has to run successfully, customers have to make sure SQL Server Agent is enabled on the DB
server hosting RM.