When connecting to Microsoft SQL Server instances it is possible to login with Windows Authentication (called OS Authentication in dbWatch). The accout used is the same account as the dbWatch Control Center service runs as.

Per default the dbWatch Control Center Service running on Windows is configured using the system account. Running under this account will only make it possible to connect to SQL Server using SQL Server Authentication login.

In the dbWatch installer “Install Server” step you can specify what account to use.

To be able to use Windows Authentication login (which use credentials from Windows) the dbWatch Control Center Service must run under an account with sysadmin privileges on the SQL Server instances.
Click “Browse” and specify the correct Windows account with correct credentials.

You can also change this later by right clicking on the dbWatch Control Center service in the “Services” tool, selecting “Properties” and then navigating to the “Log On” tab.

This example shows the dbWatch Control Center Service running under a Windows account “SQLmonitor”.

The “SQLmonitor” account is mapped in to a login on the SQL Server instance

The “SQLmonitor” login needs the sysadmin server role to work properly.

After adding an MS SQL Server instanace to dbWatch Control Center you will be able to see a small connection pool (4 sessions) connected to the SQL Server.

You can also see all sessions from dbWatch Control Center Service (Server) in dbWatch Management GUI.

← Adding a SQLServer Instance / Adding SQLServer instances with kerberos →


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment