Question
Optimum settings for MS SQL Spatial Database writer.
Our workflows creates a MS SQL Spatial database. However we are getting a significant amount of Linestring type entities when we open the same database in Postgis. What are the optimum defaults in the sql spatial writer which could avoid the problem. Are there any other steps we could add to our shape file preparation workflow which could also assist with the issue?
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+21- Safer
Could you provide a few more details as to what the expected result is in MS SQL and what the overall workflow is? Sounds like you're going Shape->MSSQL and then as a parallel exercise Shape->PostGIS? And getting different results?