https://community.qlik.com/t5/Talend-Studio/Cross-Schema-Database-Name-Field-in-Postgres-SQL/m-p/2534765#M148138 <P>Hello&nbsp;</P> <P><SPAN>You must specify the schema name in the Schema field. If multiple schemas exist, you can use context variables to dynamically modify the schema name within a single subjob.</SPAN></P> <P><SPAN>Regards</SPAN></P> <P><SPAN>Shicong</SPAN></P> Thu, 30 Oct 2025 07:12:09 GMT Shicong_Hong 2025-10-30T07:12:09Z https://community.qlik.com/t5/Talend-Studio/Cross-Schema-Database-Name-Field-in-Postgres-SQL/m-p/2534736#M148137 <P>Planning the layout of databases for Postgres SQL.</P><P>Right now - using MSSQL - have a DB for STAGE and one for FACT.</P><P>Converting to Postgres SQL, having single connection to EDW db in MS SQL can reference multiple schema (dbo, etc).</P><P>How do you specify a table in different schema in the tDBOutput component for a Postgres SQL connected db?</P> Wed, 29 Oct 2025 18:51:42 GMT https://community.qlik.com/t5/Talend-Studio/Cross-Schema-Database-Name-Field-in-Postgres-SQL/m-p/2534736#M148137 Tim_Ouimet 2025-10-29T18:51:42Z https://community.qlik.com/t5/Talend-Studio/Cross-Schema-Database-Name-Field-in-Postgres-SQL/m-p/2534765#M148138 <P>Hello&nbsp;</P> <P><SPAN>You must specify the schema name in the Schema field. If multiple schemas exist, you can use context variables to dynamically modify the schema name within a single subjob.</SPAN></P> <P><SPAN>Regards</SPAN></P> <P><SPAN>Shicong</SPAN></P> Thu, 30 Oct 2025 07:12:09 GMT https://community.qlik.com/t5/Talend-Studio/Cross-Schema-Database-Name-Field-in-Postgres-SQL/m-p/2534765#M148138 Shicong_Hong 2025-10-30T07:12:09Z