DLM Dashboard is part of the SQL Toolbelt.

Skip to end of metadata
Go to start of metadata

This page applies to DLM Dashboard 1.4.7 and later. For earlier versions, see Getting started in v1.2.5 and earlier, or Getting started in v1.2.6 to v1.4.6.

1. Before you start

You can install DLM Dashboard on any machine that can talk to your SQL Servers over the network. Make sure that machine has .NET Framework 4.5 (download) installed.

To access DLM Dashboard, you need the latest version of either Chrome, Firefox, or Internet Explorer.

SQL Server 2008, 2008R2, and 2012 are fully supported. There's limited support for SQL Server 2014 and SQL Server 2016.

2. Install

Download the installer, run it, and follow the instructions. 

When installation finishes, make sure that Launch DLM Dashboard 1 on completion is selected, and click CloseDLM Dashboard opens in your default browser at http://localhost:19528/.

If you want to access DLM Dashboard from a different machine to the one it's installed on, use the URL http://<machine name>:19528

If you're prompted, enter your Windows username and password.

3. Add servers and databases 

You can use DLM Dashboard to monitor up to 40 databases - or 50 if you set up notifications.

When DLM Dashboard opens, the welcome page is displayed:

Contents

Click Set up DLM Dashboard. The Configuration page opens.

Add a server

For DLM Dashboard to track schema changes on a server, you need to run a setup script run a setup script on the server. The script creates a DDL trigger, a database, and some stored procedures. For information about these objects, see About the DLM Dashboard server objects.

To add a server:

  1. On the Configuration > Add a server page, under SQL Server name, enter the SQL Server's name:

    For a remote SQL Server, enter its details in the format: <machine name>\<SQL Server instance name>,<port number>
    For example: production-server\SQL2012,999
  2. Select either SQL Server authentication or Windows authentication
    If you choose Windows authentication, DLM Dashboard will connect to SQL Server using its Windows services account.
    To change this account, see Changing the DLM Dashboard user account.
  3. Enter credentials to connect to the server.
    If you're evaluating DLM Dashboard, it's easiest to use a login with the sysadmin role.
    Otherwise, we recommend creating a new login for DLM Dashboard. 
    For instructions, see Creating a login with the correct permissions.
  4. Click Add server.

    If you've already run the setup script on this server, you'll skip step 5.

  5. The Set up server page opens.

    You need to run a SQL script which sets up the server for monitoring. To find out more about the script, see About the DLM Dashboard server objects.
    You can either:
    • Select Let DLM Dashboard run the script and click Run setup script.  
      This will only work if the account you used in step 4 has CONTROL SERVER permissions. Click Back if you want to change the account.
    • Select I'll run the script myself.
      You need to download the setup script the setup script, then run it on the server. You need sysadmin permissions to run the script.
      When you've finished, click I've run the script.

The server you added is listed under Servers. 

Add databases

Once you've added a server, you can add a database.

If you've just added a server:

  1. The databases on the server are listed on the right:
  2. Next to each database you want to monitor, click Add

Otherwise:

  1. On the Configuration page, select the server that the database is on.
  2. On the right, click Add databases.
    The Connect to server page opens.
  3. If you're using SQL Server authentication, re-enter the credentials for the server.  
  4. Click Connect
    The databases on the server are listed on the right. 
  5. Next to each database you want to monitor, click Add

 If you want to add more than 40 databases, setting up notifications will add an extra 10 to your limit.

4. After configuration

When you've finished setting up, click Home in the banner. It now looks something like this:

What's next?

See Investigating schema changes.

  • No labels