My issue here is that I need the conversion to be generic such that the transformer can convert ALL feature classes and tables from the enterprise geodatabase (ArcSDE) to file geodatabase.
At the moment, the “Microsoft SQL server spatial” requires selecting the feature classes and table that will be transferred. Then what if new feature classes or tables are added to the enterprise geodatabase? Do I need to go back to the tool and select them so that these new feature classes and tables can be transfered?
I have tried also the ESRI ArcSDE but I got the error below.
Yes, if u use the reader you must choose the tables.
To read dynamically you could use a SQL-creator.
AS you can make your'e sql-script fully paramterised you can create user parameters, choice lists etc.
SQL-creator (and executor) allows for much more freedom.
Of course you then are required to create a sql-script.
If there are (materialised)views in the database for instance, you can copy the main sql body to your creator and adapt and parametrise whatever you want to.
You can even create a sql-creator to query and load the view and have a second creator execute it (witout writin the sql for it...) (there is a thread in this forum a couple months ago on this topic btw)
Does this mean that there is no generic “out of the box” tool in FME that can convert the ArcSDE geodatabase (SQL or Oracle) to file geodatabase? The available tool requires selecting feature classes\\tables. But my aim here is to have a workbench that convert the ArcSDE geodatabase to file geodatabase without selecting feature classes\\tables.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.