Filter database table (with sql) before import

[TorstenFay]

When importing data from a sql-database via catalog pane, one has to load all data within the specified table. When using tables with data with complex shapes and several thousands of vertexes per entry, it takes minutes to even calculate the extent. After that one can exclude data that is not needed for the specific project.

It would be better if you could use sql-query to make a selection of entries that should be recognized and loaded in the first place. 

[AlfredBaldenweck]

If using an enterprise GDB, you may want to check out Query Layers. Query layers—ArcGIS Pro | Documentation

[Bud]

As a temporary workaround, could you use a model? Use a SQL expression in the Select tool and use that as a direct input to the Import tool.

Similar to this: Apply SQL filter to data used in Export XML Workspace Document

Related: Allow selection/SQL expression for all applicable geoprocessing tools

Also, I wonder if there are any GP tools similar to Import that have a SQL Expression parameter.

[KoryKramer]

@TorstenFay when you say importing data via catalog pane, are you using the Feature Class to Geodatabase tool?

XML Workspace Document?

[TorstenFay]

Hey, @KoryKramer, no, I just drag the database into my map.

Step 1:

1

Step 2:

2

Step 3:

3

This Step 3 can take a while. It would be nice if one could define a filter within Step 2.

[AlfredBaldenweck]

Wait.

Unless I'm missing something, why aren't you using a Where clause in that Query layer?

[TorstenFay]

Hi, @AlfredBaldenweck , you mean via Properties -> Source -> Query... but this is only possible after loading in the whole table. As far as I know...

[AlfredBaldenweck]

Nope, I think you have your order of operations wrong.

[TorstenFay]

Many thanks for the really good workaround. Obviously I was not aware of this way of importing.

So I really just need to change my workflow. Thanks!

[Bud]

@TorstenFay In the future, it might help to avoid using the word "import" in this context. Normally, importing would mean you are inserting data into a table or feature class using a geoprocessing tool. But when you add data to a map/create a query layer, you're simply viewing the data, not importing it into a table or feature class.