After Pro Server is installed, the Pro Server needs to be configured by using the DriveWorks Pro Server Configuration Tool before the service can be started.
Microsoft SQL Server Editions
This topic refers to Microsoft SQL Server, please refer to the DriveWorks Pro Server Prerequisites for information on which editions of SQL Server are supported.
There are three main steps to configuring Pro Server:
In addition, if you are running Pro Server in an environment where Microsoft SQL Server is locked down, then you may need to configure Microsoft SQL Server to enable DriveWorks Pro Server to access it.
The SQL Connection Details task allows the location and authentication information used to connect to Microsoft SQL Server to be configured.
Launch DriveWorks Pro Server and click the SQL Server task from the Task List on the left hand side, and follow the steps below:
Click the Browse button at the end of the Server field.
Select the Server from the list of available servers.
If the Server Address does not exist in the list click Refresh Server List to repopulate the list.
Select the Authentication method the SQL database has been set up to use.
If using SQL Server Authentication enter the Username and Password required to login to the server.
The username and password should have the correct permissions to access to the SQL Server.
Click Test Connection to determine if the connection is successful.
When you have browsed to the instance of SQL you wish to use you can then check your connections and any permissions that you maybe missing that you require to be able to use that SQL server as that user.
To do this click on the Test Connection button found below the browse button. This will run a check in SQL to make sure the user has the correct permissions in SQL.
It is important to make sure that you have the Service started before testing the connection otherwise Pro Server can't test the connection as it isn't running.
The Connection Tester will report back if you are missing any of the following permissions:
If you are missing any permissions speak to your IT administrator to be granted these permissions in SQL.