- Notifications
You must be signed in to change notification settings - Fork 508
[microsoft_sqlserver] Establish Named instance connection by Instance Name #4501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🚀 Benchmarks reportTo see the full report comment with |
🌐 Coverage report
|
| /test benchmark fullreport |
| Microsoft SQL Server has a feature that allows running multiple databases on the same host (or clustered hosts) with separate settings. Edit the instance port and provide the named instance port to connect to the named instance and collect metrics. | ||
| See: [Instruction on how to configure server to listen Named Instance port](https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-a-server-to-listen-on-a-specific-tcp-port?view=sql-server-ver15) | ||
| Microsoft SQL Server has a feature that allows running multiple databases on the same host (or clustered hosts) with separate settings. Establish named instance connection by using the instance name along with the host name (Ex: `host/instance_name` or `host:named_instance_port`) to collect metrics. | ||
| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's provide detailed description here to avoid repeated user queries around this. There are couple of aspects that need to be clarified:
- As of now we support single host only. For multiple hosts, new integration need to be run. Need a section on it.
- What is the different syntax hosts can take with syntax description.
- Example of hosts with sample example values.
packages/microsoft_sqlserver/data_stream/performance/agent/stream/stream.yml.hbs Show resolved Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM mod the request for detailed description in the readme.
| | ||
| As of now the integration supports collecting metrics from single host. For multi host, each host needs to run a new integration. | ||
| | ||
| User has to provide the user name, password and the host name, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can add the following line:
+ The host configuration also contains both named instance or port details, as per the syntax below,
| ### Connecting to Named Instance (host) | ||
| | ||
| * `host/instance_name` ex: `localhost/namedinstance_01` | ||
| * `host:named_instance_port` ex: `localhost:60873` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
Minor edits
| LGTM |
What does this PR do?
Connection is established with and without port number and also with the Instance Name.
Checklist
changelog.ymlfile.How to test this PR locally