Skip to main content
Released

Schema Portal SQLExecutor

Related products:FME Form

Currently it is quite difficult to expose attributes using a SQLExecutor to read in data from a SQL Server DB. Its currently very difficult if not impossible to have a dynamic workspace using a SQLExecutor to aquire the data. The reason I would like to use SQLExecutor rather then a reader or feature reader is the ability to allow the SQL server to do most of the grunt work rather then FME server. The sql query can order by distance to a location, search just to the nearest data point etc.

A schema port similar to the port on the feature reader will allow for dynamic workspaces using largely SQL queries to grab data on the fly.

This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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.

5 replies

erik_jan
Contributor
Forum|alt.badge.img+17
  • Contributor
  • January 20, 2016

Could you use the SQLCreator to do this. It has a "Attributes to Expose" parameter that can be imported from the SQL query.


Forum|alt.badge.img+5
  • Author
  • January 22, 2016

Hi Erik, thanks for the reply.

That wouldn't work if you are doing dynamic workspaces. If you are only opening a few datasets at a time that's fine (or the same datasets over and over again). But if you want a flexible workspace that might have to open up hundreds of different datasets then you would have to pre- expose (sounds wrong!) all of those attributes. Also the query cant expose the correct attributes if you are opening up different data sets per workspace run.


erik_jan
Contributor
Forum|alt.badge.img+17
  • Contributor
  • January 22, 2016

OK, I see what you are trying to do.

And a schema port would make sense on any transformer that needs exposing attributes after use (SQLExecutor, SQLCreator, Joiner etc.).

You got my vote!


erik_jan
Contributor
Forum|alt.badge.img+17
  • Contributor
  • January 22, 2016

I would rename the topic to "Schema output port on SQLExecutor".


Forum|alt.badge.img
  • May 28, 2021

This would make it easier. Note if you want to dynamically write all attributes to a dynamic writer, you can use the Custom transformer SchemaSetter, then set the Schema Sources on the writer to "Schema From Schema Feature", the only issue (I have found) is the attributes will be sorted.


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