Forum Discussion

noorudeen100's avatar
noorudeen100
Frequent Visitor
1 year ago
Solved

Fabric Datflow Gen 2 Creating multiple staging datawarehouse and Tables on every run

Hi Team,   I am using dataflow gen 2 to load on premise data to fabric datawarehouse upon using it for every new dataflow gen 2 it creating new staging datawarehouse and it inside it creating multi...
admin
  • v-prasare's avatar
    v-prasare
    1 year ago

    Hi noorudeen100,

     

    Meanwhile you can submit your detailed feedback and ideas via Microsoft's official feedback channels, such as the Microsoft Fabric Ideas.  Feedback submitted here is often reviewed by the product teams and can lead to meaningful improvement, your inputs will truely help grow our community.

     

     

    Thanks,

    Prashanth Are

    MS Fabric community support

     

burakkaragoz's avatar
burakkaragoz
Icon for Super User rankSuper User
1 year ago

Hi noorudeen100 ,

Use a Custom Connector Configuration

Sometimes the default PostgreSQL connector used by the On-Premises Data Gateway can be finicky. You can try the following:

  • Manually configure the connection string in the gateway using advanced settings. For example:
Host=your_host;Port=5432;Database=your_db;Username=your_user;Password=your_password;SSL Mode=Prefer;
  • Make sure the SSL mode matches what your PostgreSQL server expects (Require, Prefer, or Disable).

Check for 32-bit vs 64-bit Driver Mismatch

Ensure that the bit version of the PostgreSQL ODBC driver matches the bit version of the gateway. A mismatch can cause silent failures.

Try Using a Different Connector (ODBC vs Native)

If you're using the native PostgreSQL connector, try switching to the ODBC connector in the gateway setup and configure it using a DSN that you’ve already tested successfully.

Let us know if this helps—or if you can share the exact connector type and version you're using, we can dig deeper.