Skip to main content
Question

Convert SqlLite to SQL Server

  • August 19, 2019
  • 3 replies
  • 31 views
C
Forum|alt.badge.img

Greetings.

I am trying to export a Sqllite (geopackage) to SQL Server.

Keep getting an error despite changing the options.

Reader:

 

Writer:

 

Error:

Transactions are being used by the Geodatabase Writer

An error occurred while attempting to open the table, feature class or relationship class 'main.airports'. The error number from ArcObjects is: '-2147467263'. The error message from ArcObjects is: {}

An error occurred while attempting to open the table, feature class or relationship class 'main.airports'. The error number from ArcObjects is: '-2147467263'. The error message from ArcObjects is: {}

A fatal error has occurred. Check the logfile above for details

A fatal error has occurred. Check the logfile above for details

Stored 1 feature(s) to FME feature store file `C:\\Users\\User\\AppData\\Local\\Temp\\wb-cache-geopackage2mssql_spatial-NJVZFF\\Main_airports -1 10 -1 0 89fdbd78da335154a0ddf39d89823152eee47e98.ffsupdating'

 

Any suggestions??

 

Thanks,

Clive

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.

3 replies

david_r
Celebrity
  • david_rCelebrity
  • August 20, 2019

Does the "main" table qualifier (usually it refers to a schema or a user) already exist in the geodatabase?

C
Forum|alt.badge.img

Does the "main" table qualifier (usually it refers to a schema or a user) already exist in the geodatabase?

In SQLLite it is main.

In SQL Server it is dbo.

 

I get an error whatever I choose.

chrisatsafe
Contributor
Forum|alt.badge.img+2
  • chrisatsafeContributor
  • Contributor
  • August 23, 2019

Hi @clives_online,

By any chance have you seen the answer on this post? It looks like they were getting the same error message and the issue was that it was not an SDE enabled database. Not sure if this is a new database or an existing one but it might be worthwhile to verify.

Hope this helps.

Community Stats

32,207
Posts
122,305
Replies
39,891
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.