Skip to main content
  • EN

Hello,

 

Is there a way to 'fanout' when writing to an SQL Database? The image below shows a simplified example of what I want to achieve , I have a number of target SQL Server tables and their table names relate to the values in Col2 (I actually have dozens of target tables to write to).

 

I'm guessing I could achieve this by writing to a format that is 'fanoutable' (e.g. Excel), then re-importing and then writing to SQL Server, but I wondered if any one knew of a more eloquent way of achieving this?

 

Example

Thanks,

 

RB

Sure, in the output feature type parameters, set the table name to the attribute containing the table name, e.g.:

sql fanout

 As long as all the target tables have the same schema (as they do in your example), then that's all.

Thanks David, that is exactly what I needed.

Sure, in the output feature type parameters, set the table name to the attribute containing the table name, e.g.:

sql fanout

 As long as all the target tables have the same schema (as they do in your example), then that's all.

Hi @david_r​ , I got a similar problem where I am trying to reproject a number of SQL table and then write back to same database. The concept is like the attached image. Problem is when I am connecting all the reader tables to the projector transformer, attributes/columns from all tables are getting merged into one, from where I cannot fan out the tables to write back into the same SQL server. Is there any other interim process?sql_reproject_concept_draw

Hi @david_r​ , I got a similar problem where I am trying to reproject a number of SQL table and then write back to same database. The concept is like the attached image. Problem is when I am connecting all the reader tables to the projector transformer, attributes/columns from all tables are getting merged into one, from where I cannot fan out the tables to write back into the same SQL server. Is there any other interim process?sql_reproject_concept_draw

Did you look into using the feature attribute "fme_feature_type"? This should contain the table name from the MSSQL reader, which you can then either transform or use as-is on the writer.

Note that you may have to manually expose (make visible) this attribute on the reader first.

Hi @david_r​ , I got a similar problem where I am trying to reproject a number of SQL table and then write back to same database. The concept is like the attached image. Problem is when I am connecting all the reader tables to the projector transformer, attributes/columns from all tables are getting merged into one, from where I cannot fan out the tables to write back into the same SQL server. Is there any other interim process?sql_reproject_concept_draw

Hi @david_r​, thanks so much. Yes I have used fme_feature_type to expose and dynamic reader/writer. That worked. Also I needed to search and replace the schema that is in string otherwise a new prefix gets added and failed to read into the destination table. Do you have any suggestion if I would like to transform tables from different schemas? The string searcher/replacer allows only one string per transformation, right?

Reply


Community Stats

29,997
Posts
113,956
Replies
37,623
Members
Terms & ConditionsCookie settings