Subscribe to this thread
Home - General / All posts - SQL4Arc - Can't see feature class exported from SQL Server
Fridtha4 post(s)
#24-Jul-24 12:55

Hello,

I took a feature class that was inside a SQL Server database and exported it into another gdb geodatabase. However when I open SQL4Arc, no matter what I do, it can't see the new feature class for me to run queries on. If I create a feature class from scratch in pro, SQL4Arc can see that no problem. What do I have to do to troubleshoot getting SQL4Arc to see the exported fc?

Dimitri


7,464 post(s)
#24-Jul-24 14:20

To run sql4arc you have to launch it from within Pro. Is the file geodatabase you want to see being used in Pro? If not, you can still manually open it from sql4arc.

Launch sql4arc from Pro and then choose File - Create - New Data Source - more... and then in the New Data Source dialog choose File:gdb for the Type. Choose the Source gdb and then Create Data Source.

There's an illustrated, step by step example in https://sql4arc.com/doc/sql/example__connect_to_an_esri_gdb_file_geodatabase.htm

Fridtha4 post(s)
#24-Jul-24 14:41

That's not the problem. I am opening it from within Pro, and the gdb is showing in sql4arc. However the feature class I exported from SQL Server into the gdb is not showing up in sql4arc. I've tried the refresh icon in the Add-In tab, I've tried refreshing the gdb in sql4arc, I've tried rebooting. The feature class (table) does not show in sql4arc. Any other feature class I create DOES show up, just not the one I exported from SQL server.

Dimitri


7,464 post(s)
#24-Jul-24 18:47

Interesting. Just to try something completely different, to bracket the issue, try this: run Pro with a different gdb, and then launch sql4arc from Pro. Next, within sql4arc, create a new data source by connecting to the gdb that had the missing feature class issue, using the procedure in my post. Does the table show up in that data source?

Fridtha4 post(s)
#24-Jul-24 19:07

Ok I tried your suggestion, to no avail. However, I just figured it out. Sql4arc apparently does not like Big Integer field types. Once I removed those and re-exported, it showed up in sql4arc.

*edit: Actually, when I ran a select *, no data showed up even though the table's schema did. I then removed the Timestamp Offset fields, and BAM, the rest of the data showed up.*

Thank you for trying to help! It was nice to know that help is out there.

F-

Fridtha4 post(s)
#09-Aug-24 17:44

Sigh, it's doing it again but this time, nothing I try is working. See the image, two of the tables in the gdb come through to SQL4Arc, but the rest do not. I can't figure out what it is.

Attachments:
Missing-Tables.jpg

Mike Pelletier


2,139 post(s)
#16-Aug-24 18:54

If memory serves, I could not get GDB layers that had topology "running" on them in ESRI to show up in Manifold. Perhaps explore that.

Manifold User Community Use Agreement Copyright (C) 2007-2021 Manifold Software Limited. All rights reserved.