Our production environment demonstrates that these plugins work with SQL Servers with tcp-ip connectivity and both Windows and Mixed (SQL) Authentication.
Named pipes (Instance) connectivity is supported as well.
Incase the PRTG probe and target servers are not in the same domain structure using SQL based authentication is the only viable solution:
In many cases you need to allow Mixed authentication and a create a SQL user:
The following instructs the needed actions:
Start Admin Command Line:
cd "C:\Program Files\Microsoft SQL Server\MSSQL11.VEEAMSQL2016\MSSQL\Binn"
SQLCMD -S localhost\VEEAMSQL2016
Enter or Copy & Paste:
EXEC xp_instance_regwrite N'HKEY_LOCAL_MACHINE', N'Software\Microsoft\MSSQLServer\MSSQLServer', N'LoginMode', REG_DWORD, 2
CREATE LOGIN PRTGMonitor WITH PASSWORD='@PassW0rd1', DEFAULT_DATABASE=[master], DEFAULT_LANGUAGE=[us_english], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF
EXEC sys.sp_addsrvrolemember 'PRTGMonitor','sysadmin'
Then Restart SQL Server Services....
You can check the connectivity on the probe with the following lines in command line on your PRTG Probe computer:
cd "C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML"
VeeamBMon.exe -t:opavea1901\veeamsql2016 -u:prtgmonitor -p:@PassW0rd1 -i:jobperf
You should receive a response starting with <prtg>...