docker-library / docker-library/redmine
SQL Server: Determine port of named instance using SQL Server Browser
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 237
- Forks
- 171
- PR merge metrics
- No merged PRs in 30d
Description
When using MS SQL Server with a named instance as database server, connecting via port 1433 does not work, because named instances run on different ports. By default, these run on random high ports that change everytime the database engine is restarted.
Using Redmine with SQL Server and named instances currently requires to set the port of a SQL Server instance to a fixed value via SQL Server configuration, because Redmine requires this port to connect to the database server.
The SQL Server provides the SQL Server Browser service that will return the actual port an instance is running on. Would it be possible to configure Redmine/Ruby in a way that it uses the Server Browser to determine the actual SQL Server port and use that for database connection attempts?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing how Redmine/Ruby makes SQL Server database connection attempts and review the SQL Server Browser service protocol for named instances. Done means a named SQL Server instance can be reached without manually configuring a fixed port, with connection behavior verified for the dynamically reported port.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby, sql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100