Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

SQL Server db Instance Port

I have searched Thwack, but haven't seen a solution for pointing some of the SAM monitoring items to a sql server not using the default 1433 port.

I am a sysadmin, and not a sql server dba. If I can not monitor our sql server farm, the dba has not much choice but to shop elsewhere.

Is there anywhere within SAM that a novice can add the port field that Solarwinds has seemed to have forgotten about?

Dave

Find more posts tagged with

sql_port

Accepted answers

tomb

The easiest workaround is using ODBC User Experience Monitor. Just edit the monitor and modify the default Connection String to

Driver={SQL Server};Server=${IP},1433;DataBase={Northwind};Uid=${USER};Pwd=${PASSWORD};

Replace 1433 with your actual SQL Server port number.

All comments

Bronx

This first link explains the SQL Server User Experience Monitor. Note this section: This monitor uses SQL Server port 1433. Instructions are given to help you overcome this issue,

This is the SQL template. Here you can change the SQL Server Port.

You can find a list of free templates here. Hope this helps!

aLTeReGo

There is currently no ability to specify a non-standard SQL port in the SQL User Experience Monitor. The SQL User Experience Monitor can be used to monitor Microsoft SQL Servers on non-standard ports provided the SQL Browse Service is enabled and working. This behavior should be no different than other MSSQL tools when connecting to a SQL Server on a non-standard port.

There are some environments where the SQL Browse service is not adequate on its own, such as where there are layer 3 boundaries, so allowing customers the ability to specify a non-standard SQL port in the SQL User Experience Monitor is something we're currently tracking internally as a feature request under FB87988.

tomb

The easiest workaround is using ODBC User Experience Monitor. Just edit the monitor and modify the default Connection String to

Driver={SQL Server};Server=${IP},1433;DataBase={Northwind};Uid=${USER};Pwd=${PASSWORD};

Replace 1433 with your actual SQL Server port number.

aLTeReGo

The latest SAM 5.2 beta will now allow you to define a custom port for the SQL User Experience Monitor . If you're an existing APM/SAM customer under active maintenance you can sign-up here to participate in the beta. We'd love to get your feedback on this feature.

To learn more about what's new in the SAM 5.2 beta please read my blog postings below.

SAM 5.2 Beta 2 - Soup's On

SAM 5.2 Beta is Now Available

sajiimi

Hi, I have created my own template to monitor SQL server, and where it allow either default or dynamic either of one only due to this limitation I can't able able add node's those can i have either default or dynamic ports, I have to stick with one number of port only.

But AppInsight SQL you can define the port number each time while adding node, can we have same feature for 'User defined template's'

Thanks

saji