Skip to main content

Configuring WebReports SQL Server Using SSMS

Garrick Guillory
Updated

Use this article to configure a Microsoft SQL Server instance for WebReports using SQL Server Management Studio (SSMS).

This process includes enabling SQL Server authentication, creating the WebReports database, creating a dedicated SQL login, and assigning the required database permissions.

Before You Begin

Before configuring SQL Server:

  • Confirm that SQL Server Management Studio (SSMS) is installed.
  • Confirm that you can connect to the SQL Server instance that will host the WebReports database.
  • Have SQL Server administrator credentials available.
  • Make sure you have permission to restart the SQL Server instance.

You will need to save the SQL Server instance name, database name, login name, and password for use during WebReports configuration.

Connect to SQL Server

  1. Open SQL Server Management Studio.

SQL Server Management Studio

  1. Select the SQL Server instance that will host the WebReports database.
  2. Enable Trust Server Certificate.
  3. Select Connect.

Connecting to the SQL Server instance

Save the SQL Server instance name. You will need it when configuring WebReports.

Enable SQL Server and Windows Authentication

  1. In Object Explorer, right-click the SQL Server instance.
  2. Select Properties.

Opening SQL Server Properties

  1. Select Security from the left navigation panel.
  2. Under Server authentication, select SQL Server and Windows Authentication mode.
  3. Select OK.

Enabling SQL Server and Windows Authentication mode

Restart the SQL Server Instance

The SQL Server instance must be restarted for the authentication change to take effect.

  1. In Object Explorer, right-click the SQL Server instance.
  2. Select Restart.

Restarting the SQL Server instance

  1. Select Yes when prompted to confirm the restart.

Confirming the SQL Server restart

A restart is required before SQL Server Authentication can be used.

Create the WebReports Database

  1. Expand the SQL Server instance in Object Explorer.
  2. Right-click Databases.
  3. Select New Database.

Creating a new SQL Server database

  1. Enter a name for the WebReports database.

Example:

WebReports

  1. Select OK.

Creating the WebReports database

Save the database name. You will need it when configuring WebReports.

Create a SQL Login for WebReports

  1. Expand Security in Object Explorer.
  2. Right-click Logins.
  3. Select New Login.

Creating a new SQL Server login

  1. In Login name, enter the login that WebReports will use.

Example:

WRAdmin

Entering the WebReports SQL login

Save the login name. You will need it when configuring the WebReports database connection.

Configure SQL Server Authentication

  1. Select SQL Server authentication.

Selecting SQL Server Authentication

  1. Enter and confirm a strong password for the WebReports SQL login.

Configuring the SQL login password

Important: Do not use the following characters in the SQL login password:

/ \ { } ;

These characters can conflict with the WebReports appsettings.json configuration.

  1. Clear the following options:
  • Enforce password expiration
  • User must change password at next login

Configuring the SQL login password options

Save the password securely. You will need it when configuring WebReports.

Assign the WebReports Database

  1. In the Login - New window, select User Mapping.

Opening User Mapping for the WebReports login

  1. Under Users mapped to this login, select the WebReports database that you created earlier.

Mapping the WebReports login to the database

Assign Database Roles

With the WebReports database selected, enable the following database roles:

  • db_datareader
  • db_datawriter
  • db_owner
  • db_securityadmin
  • public

Assigning the required WebReports database roles

  1. Select OK to create the login and apply the database permissions.

Information Needed for WebReports

After completing the SQL Server configuration, keep the following information available:

  • SQL Server instance name
  • WebReports database name
  • SQL login name
  • SQL login password

These values are required when configuring WebReports to connect to the SQL Server database.

Troubleshooting

SQL Server Authentication Does Not Work

If the WebReports SQL login cannot connect:

  • Confirm that SQL Server and Windows Authentication mode is enabled.
  • Confirm that the SQL Server instance was restarted after changing the authentication mode.
  • Verify the SQL login name and password.
  • Confirm that the login is mapped to the correct WebReports database.

WebReports Cannot Access the Database

If WebReports connects to SQL Server but cannot access the database:

  • Confirm that the correct database is selected under User Mapping.
  • Verify that the login has the required database roles:
    • db_datareader
    • db_datawriter
    • db_owner
    • db_securityadmin
    • public
  • Confirm that the database name entered in the WebReports configuration matches the database created in SSMS.

Password or Configuration Errors

If WebReports reports an error after entering the SQL login credentials:

  • Verify that the password was entered correctly.
  • Confirm that the password does not contain /, \, {, }, or ;.
  • Confirm that the SQL Server instance name, database name, and login name match the values configured in SSMS.

If the issue continues, contact BridgeWorks Support.

Related Articles

Related articles

Comments

0 comments

Please sign in to leave a comment.