-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Project with SQL Server Layers opens much slower in 2.8 than 2.6 #21006
Comments
Author Name: Nathan Woodrow (@NathanW2) You have a spatial index on the layers? |
Author Name: Nathan Woodrow (@NathanW2)
|
Author Name: Jason Moore (Jason Moore) I do have a spatial index on the feature table that stores all of the geometry data for the various views that I have set up for the layers that make up the project. |
Author Name: Nathan Woodrow (@NathanW2) What do your views look like? Nothing special? Have a unique int column for a key? |
Author Name: Jason Moore (Jason Moore) Most are not very complex. Two or three joined tables, one always being the feature table which has a unique int column that is the primary key for that table and also contains the geometry. An example would be a view called QGIS_SAN_MHs, it contains three inner joined tables, SAN_MHs, DPW_DrainageStructures, and DAT_Features. All are linked on the fetID column which is primary int in DAT_Features. |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Nyall Dawson (@nyalldawson) Still an issue with 3.2?
Windows 7 64bit desktop Windows 7 64bit desktop
|
Author Name: Jürgen Fischer (@jef-n) Bulk closing 82 tickets in feedback state for more than 90 days affecting an old version. Feel free to reopen if it still applies to a current version and you have more information that clarify the issue.
|
Author Name: Jason Moore (Jason Moore)
Original Redmine Issue: 12923
Affected QGIS version: 2.8.2
Redmine category:data_provider/mssql
I have a project that contains many sql server layers. In version 2.6 it opened in about 20 seconds in version 2.8.1 it takes about 100. I note a difference with even one layer taking considerably longer in 2.8.
Windows 7 64bit desktop
SQL Server 12 on Windows Server 12
The text was updated successfully, but these errors were encountered: