-
Notifications
You must be signed in to change notification settings - Fork 92
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
MS-SQL Error when connecting to named instance #86
Comments
Shouldn't you use a forward slash instead of a backslash after |
For the instance name a backslash is used, see the example connection string. If I use a forward slash sqlpage uses everything before the forward slash as hostname and the part after the slash as database name.
|
v0.10.3 now supports |
Thank you for the fast reply, but I get another error now
Seems something is missing |
Okay, thanks for testing. It might take a little longer, then... |
Okay, let's not be over-confident this time 😬 Can you try v0.10.4-beta1 https://github.com/lovasoa/SQLpage/releases/tag/v0.10.4-beta1 ? Sorry for the back and forth, but I don't have a windows instance myself. |
You don't have to apologize to me. No more error messages, but unfortunately the instance is ignored. Edit: It seems to work. I will take some more time to test and will share my results. |
That's strange... SQLPage is supposed to send the instance name in its login message now, so I don't know what more to add ... |
Ok, I'm learning much more about microsoft tech than I thought I ever would. After some reading, I'm realizing that non-default sql server instances run on dynamically allocated ports. SQLPage doesn't (yet) know how to lookup your instance's port automatically, and always connects to the default 1433 port. So you need to specify it in the connection string. For instance, if your instance is bound to the TCP Dynamic Port 2179, you would specify https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/connect/static-or-dynamic-port-config |
I think of lot of connection error comes from the Windows and MS-SQL Server The default Windows port is 1433 for incoming TCP connections. But if you have a "normal" instance and a named instance they cannot share the default port. On my work machine I could not activate TCP for 1433 and so it was unreachable since port 1433, the default, was not listening. As far as I can say by now, the error is fixed with your last beta. I can connect to a named instance. I will test the connection with different ports, but this is not topic of this issue |
Thanks for your investigation. Seems we where witing at the same time, but you were faster. I will try that. |
Sorry for the late reply. It works amazing. Instance and port are recognized. Thank you |
Great ! I'd like to keep that open to give it more visibility until SQLPage is able to find the dynamic port on its own. |
Hi there,
I am receiving an error when connecting to an names MS-SQL Server Instance
{ "database_url": "mssql://user:pass@localhost\\sqlexpress/Database" }
Connection string for named instance
Server=myServerName\myInstanceName;Database=myDataBase;User Id=myUsername;Password=myPassword;
Regards
Norbert
The text was updated successfully, but these errors were encountered: