I have a MSSQL (2008 R2) SQL view that is visible and displayable within QGIS (LTR ESSEN 2.14.15) itself. However if I attempt to style the results by classification the map display disappears. If I add any form of querying to the table it disappears.

Loading the Feature table for review MSSQL 2008 R2 view shows the inherent issue- all the fields are returning an error within QGIS.

The view behaves perfectly within SQL Management Studio and within QGIS itselfMSSQL 2008 R2 View rendering as you can see above, it is up to a point. So I'm discounting //most// connection issues.

But I can't apply any styling or additional queries to the table whilst it is returning a table full of Errors.

Sadly this doesn't appear to be specific to this one particular view, but any view I'm pushing through to QGIS.

Has anyone ever encountered this type of behaviour before? And any concept of how to fix?

  • please share a screen capture of where you're getting the features to disappear... – DPSSpatial Jun 12 '17 at 15:58
  • looks like qgis is have trouble reading the table attributes. is there a unique key or a duplicate id in there? – Mapperz Jun 12 '17 at 17:48
  • @DPSSpatial- it's like the one with dots but without them! – Richard Colwill Jun 13 '17 at 10:42
  • @Mapperz- it's a view so there is no primary Key but there are also no complete duplicates. It's patently able to read the table at some point as when styling is in simple mode (ie the default when first loading a point layer) it will render the points but when you attempt to load the feature table or apply any form of query or classification of point display it all goes <sad face> – Richard Colwill Jun 13 '17 at 10:46
  • @DPSSpatial- sorry re-read your comment- it's the whole layer that fails to render- it's not datum shift or location specific it's all 105k features – Richard Colwill Jun 13 '17 at 10:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.