Connect to a remote SQL Server

SQL Event Analyzer can be run on a different computer than the SQL Server. This tutorial will show you how to connect to a remote SQL Server.

To be able to use a remote SQL Server for event analysis or recording, a network share must be created where the SQL Server service account has write access. This tutorial will show, how to create this share on the SQL Server.

Note, if the SQL Server service account is a domain account, the share can also be created on the local machine running SQL Event Analyzer, giving the SQL Server service account (or Everyone depending on security) read/write access to the share.

If connecting to a remote SQL Server and trying to open a local trace file, the following will show:
TutorialConnect_1.png

or if connecting to a remote SQL Server and trying to record, the following will show:
TutorialConnect_2.png

First we need to find the name of the SQL Server service account:
TutorialConnect_3.png

The name of the SQL Server service account in this example is: NT Service\MSSQL$SQL2016

Create a directory on the SQL Server and choose to share the directory:
TutorialConnect_4.png

In this example, the name of the directory is: RemoteTraceDir

Give Read/Write access on the directory to the SQL Server service account:
TutorialConnect_5.png

In the Options for SQL Event Analyzer, enter the UNC path for the directory on the local machine:
TutorialConnect_6.png

You will now be able to use SQL Event Analyzer to record events on a remote SQL Server.

To be able to open trace files when connecting to a remote SQL Server, the trace files must be located in a directory, where the SQL Server can get access to them.

This can be done by setting the Import Path to a path, where the SQL Server can access the files. This path can be locally on the SQL Server or a network share:
TutorialConnect_7.png

You will now be able to open trace file while connected to a remote SQL Server.

Last edited Nov 16, 2016 at 4:55 PM by larshove, version 2