[GH-ISSUE #91] SQL Server: can't connect to named instance with RiaB #53

New issue

Closed

opened 2026-03-23 20:28:44 +00:00 by mirror · 3 comments

mirror commented

2026-03-23 20:28:44 +00:00

Owner

Originally created by @rgoesseye on GitHub (Jul 29, 2024).
Original GitHub issue: https://github.com/RADar-AZDelta/Rabbit-in-a-Blender/issues/91

When using a named instance I can't connect to the database server in RiaB, this could be due to using a python module in RiaB which doesn't support named instances connections.

In the image above you can see the error that RiaB gives about being unable to connect. I tried different ways to write the server and the named instance -> (server//named_instance, server/named_instance, server\named_instance, ...) but it didn't work.

Originally created by @rgoesseye on GitHub (Jul 29, 2024). Original GitHub issue: https://github.com/RADar-AZDelta/Rabbit-in-a-Blender/issues/91 When using a named instance I can't connect to the database server in RiaB, this could be due to using a python module in RiaB which doesn't support named instances connections. <img width="722" alt="riab_instance_sql_no_conn" src="https://github.com/user-attachments/assets/a779a957-db41-4053-bdac-0ecfd956dd94"> In the image above you can see the error that RiaB gives about being unable to connect. I tried different ways to write the server and the named instance -> (server//named_instance, server/named_instance, server\named_instance, ...) but it didn't work.

mirror closed this issue

2026-03-23 20:28:44 +00:00

mirror commented

2026-03-23 20:28:45 +00:00

Author

Owner

@JensCardon commented on GitHub (Jul 29, 2024):

Riab connects to the database server using a sql authentication connection string, I don't think named instances are supported.

@JensCardon commented on GitHub (Jul 29, 2024): Riab connects to the database server using a sql authentication connection string, I don't think named instances are supported.

mirror commented

2026-03-23 20:28:45 +00:00

Author

Owner

@pjlammertyn commented on GitHub (Aug 22, 2024):

This seems to be an issue with the pymssql package.

My tests confirm this:

@pjlammertyn commented on GitHub (Aug 22, 2024): This seems to be an [issue with the pymssql](https://github.com/sqlalchemy/sqlalchemy/issues/4726) package. My tests confirm this: ![image](https://github.com/user-attachments/assets/a697c633-9025-4893-8ffa-882e4981e2fe)

mirror commented

2026-03-23 20:28:45 +00:00

Author

Owner

@pjlammertyn commented on GitHub (Aug 22, 2024):

A possible solution could be not setting the port, when it is a named instance.
The downside for this, is that named instances can only sit on port 1433.

@pjlammertyn commented on GitHub (Aug 22, 2024): A possible solution could be not setting the port, when it is a named instance. The downside for this, is that named instances can only sit on port 1433.