Skip to main content
Question

Issue with writing lines to 10.4 Geo-database on SQL server using MS SQL Server Spatial writer

  • September 19, 2018
  • 4 replies
  • 98 views
J

Hi There, I am reading data from a 10.4 Geodatabase (on SQL server) using Microsoft SQL Server Spatial writer. I am also writing this data to 10.4 Geodatabase (on SQL server) using MS SQL Server spatial writer. The update process runs fine but when I open the features in ESRI ArcGIS, I get this error. I noticed that it happens only with lines, point datasets work fine.

Underlying DBMS error [[Microsoft][ODBC Driver 13 for SQL Server][SQL Server]A .NET Framework error occurred during execution of user-defined routine or aggregate "geometry":

System.ArgumentException: 24144: This operation cannot be completed because the instance is not valid. Use MakeValid to convert the instance to a valid instance. Note that MakeValid may cause the points of a geometry instance to shift slightly.

System.ArgumentException:

4 replies

andreaatsafe
Safer
Forum|alt.badge.img+12
Hi @jayd3vl,

 

Could you try using the ArcSDE Geodb writer instead of the Microsoft SQL Server Spatial Writer?

 

stalknecht
Contributor
Forum|alt.badge.img+19
  • stalknechtContributor
  • Contributor
  • September 23, 2018

Please try the ArcSDE reader and writer. An Arcgis Geodatabase is better handled by the SDE. If you use the backdoor using a SQL Server reader/writer you will get funny results. These readers and writers are not aware of by example versioning that the SDE does.

J
  • jayd3vl
  • Author
  • September 25, 2018
stalknecht wrote:

Please try the ArcSDE reader and writer. An Arcgis Geodatabase is better handled by the SDE. If you use the backdoor using a SQL Server reader/writer you will get funny results. These readers and writers are not aware of by example versioning that the SDE does.

Thanks stalknecht, Andrea for your feedback. The reason for using SQL Server Spatial wrier was the support for bulk Insert. Our business requirement is that in case of failed process, the original data remains intact. ESRI Geodatabase writer has this property “Features to write per transaction” and I set it to a very high value. I came across a scenario where there was an error with the workspace and rollback didn’t happen. I noticed that this writer writes record by record.

 

 

I would prefer to use ESRI geodatabase writer if I can get the rollback functionality to work. I am curious if anyone else had success with rollback using ESRI geodatabase writer. Thanks jay

 

 

 

 

 

stalknecht
Contributor
Forum|alt.badge.img+19
  • stalknechtContributor
  • Contributor
  • September 26, 2018
jayd3vl wrote:
Thanks stalknecht, Andrea for your feedback. The reason for using SQL Server Spatial wrier was the support for bulk Insert. Our business requirement is that in case of failed process, the original data remains intact. ESRI Geodatabase writer has this property “Features to write per transaction” and I set it to a very high value. I came across a scenario where there was an error with the workspace and rollback didn’t happen. I noticed that this writer writes record by record.

 

 

I would prefer to use ESRI geodatabase writer if I can get the rollback functionality to work. I am curious if anyone else had success with rollback using ESRI geodatabase writer. Thanks jay

 

 

 

 

 

What transaction-type do you use? I think it should be Transactions. See a screenshot from the help:

 

 

Reply


Helpful Members This Week

Community Stats

31,378
Posts
119,008
Replies
39,008
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.