different schemas with the same table's names in the one replication task

[KamilMaslanka]

I have this situation that I have few schemas with the same table names in every schemas and when I am adding these tables names are changed to table_name_1 and it is replicating with the same name with "_1" which is different name like in the source. I would like to handle it somehow. In old qlik every table was represanted like schema.table_name and it was not any issue when few schemas had the same table names.

[OritA]

Hi @KamilMaslanka , 

In general, by default Replicate replicates the source table to the target endpoint giving it same name as its name in the source endpoint.  It is possible to control the name of the schema through the task setting and also through transformation rule. 

I am not sure I understand what is your problem however I am suspecting that you have a transformation rule that adds the '_1' suffixs. In general, you can read more details about transformation rules in the Replicate documentation using the following link:
https://help.qlik.com/en-US/replicate/November2024/Content/Global_Common/Content/SharedEMReplicate/C...

If you still need help please open a case, explain the problem and attach to the case the task diagnostic package so we can get more details about the setting and help you to achieve what you want. 

Regards,

Orit

[john_wang]

Hello @KamilMaslanka ,

AS @OritA mentioned, you may use Global Transformation rule to rename the target table to make sure it's uniqueness, for example add schema name suffix as format:

sourceTableName_sourceSchemaName

In Qlik Replicate:

Hope this helps.

John.

[KamilMaslanka]

Hi John_wang,

It is not a problem to change datasets but problem is with how dataset is represents. 

Let me explain.

I made a test. I changed dataset names like schema_name.table_name and the problem is that it was replicated in snowflake in "schema_name/schema_name.table_name" but should be replicated in directory "schema_name/table_name".

In old qlik every datasets was represent like schema_name.table_name and in new qlik dataset is only table_name which is wrong planned. When we change dataset name exactly with the same name is treated like table name so it is replicated with dataset_name not with table_name.

I hope I describe this issue deeply and you will be able to understand.

Kamil

[john_wang]

Hello @KamilMaslanka ,

Thanks for the update. We need Replicate version and task configuration information. Please open a support ticket and provide the task Diagnostics Packages as well, Our support team will be more than happy to assist you.

Regards,

John.

[Heinvandenheuvel]

>>>> " In old qlik every table was represanted "

Please be specific about both the 'old' version and 'new' version. Do you still have access to the 'old' system to re-verify that the behavior indeed changed or was perhaps incorrectly remembered?

>>> "when I am adding these tables names are changed to table_name_1 "

Are you suggesting Replicate is doing that on its own, or did you setup a transformation to make that happen? Please clarify.

>>>> "In old qlik every table was represanted like schema.table_name and it was not any issue when few schemas had the same table names."

Well, Replicate utilizes this notion of 'default target schema'. If nothing else is indicated, then that's where the target tables will go and a name collusion may occur.

You can set up a per-table transformation:

Table Settings - ATT_USER.TEST

Source Table Details

Table Schema	ATT_USER
Table Name	TEST

:

Map to target table

Table Schema:

Table Name:

Of course that would be too tedious when numerous source tables are involved (unless json scripted)

The proper solution would seem to be multiple GLOBAL TRANSFORMATIONS, one for each target schema (corresponding to each source schema)

New Transformation Rule  ---> Rename schema --> Schema name is like: ---> Rename
schema to ---> 

Name  

Description: 

Repeat for each source schema

Makes sense?

Hein.

[KamilMaslanka]

I do not want to change schema name. When I am adding datasets from MySQL databas, every datasets should be represent with schema_name.table and in this representation I would like to replicate to snowflake. When I am adding new datasets display name is only table_name not schema_name.table_name. Please let me know how I can enable this option that every datasets will be represents like schema_name.table_name - not only table_name.

[KamilMaslanka]

I would like also to respond on your questions:

Old Qlik I mean Qlik Replicate from 2022 where every new adding tables (datasets) is represent with schema_name.table_name and I do not have any issue with schemas with the same table names.

New Qlik I mean Qlik Cloud.

[Heinvandenheuvel]

I had/have no clue what Qlik cloud is supposed to do, or why it exists. There are probably good reasons, and good documentatiom but when looking I could not find a simple description on the Qlik website.

I did find a video under https://help.qlik.com/en-US/videos filtering for 'Qlik cloud' and 'data integration' which seems to describe a product somewhat similar to Replicate (Formerly Attunity). If interested this linke may lead to what I watched, but I cannot tell from the name:https://help.qlik.com/en-US/video/NckjsfH6rimmtmYgCWuydK

@KamilMaslanka   Is this the 'new' Replicate you are referring to?

Well, You are asking a question in a Replicate forum but is it possible the you do NOT have a Replicate question at all, but a Qlik Cloud (formerly known as Talend?) issue. That appears to be a competing product brought under the same Qlik umbrella.

This  seems to be an exercise to replace one 'old' Replicate solution with a 'new' shiny object which is a completely different engine and possibly has completely different goals which may or might not match your needs better, but seem to fail this multi-source-schema requirement.

Qlik Replicate DOES show the source schema for a table, not just the name.

I suggest you re-post your question in a Qlik Cloud (Talend) forum.

Cheers,

Hein.

[KamilMaslanka]

Thank you for your response. When you selecting tables for replication every table is represent with schema_name.table_name but if you will go next in configuration you will see only table_name in datasets added to replicate.