Bug report #10571
SQL Server Layers using DSN doesn't work
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Severe/Regression | ||
| Assignee: |  Nathan Woodrow | ||
| Category: | Data Provider/MSSQL | ||
| Affected QGIS version: | master | Regression?: | No |
| Operating System: | Windows | Easy fix?: | No |
| Pull Request or Patch supplied: | No | Resolution: | fixed/implemented |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 18978 |
Description
Configured connections to MSSQL no longer work. They did work in 2.0 and 2.2.
Steps to reproduce:
- set up a MSSQL ODBC entry
- open the Add MSSQL Table dialog, create a connection using just the provider/dsn field
- test connection works
- listing tables works
- loading the table as a layer in the map fails.
If you configure the connection with Host and Database and no provider/dsn, it works as expected.
History
#1
Updated by Nathan Woodrow about 10 years ago
- Assignee set to Nathan Woodrow
- Status changed from Open to Feedback
What is the version of your QGIS install. Have a look in the about box.
There was some work done in that last night and I have fixed some stuff today. It's working for me at the moment and I'm using a DSN.
#2
Updated by Alex Leith about 10 years ago
Nathan Woodrow wrote:
What is the version of your QGIS install. Have a look in the about box.
There was some work done in that last night and I have fixed some stuff today. It's working for me at the moment and I'm using a DSN.
2.3 master, installed using osgeo4w yesterday. I'll update now and check.
#3
Updated by Nathan Woodrow about 10 years ago
- Resolution set to fixed/implemented
- Status changed from Feedback to Closed
This was fixed this morning.