Forum Discussion

ShanthanPaladi's avatar
ShanthanPaladi
Regular Visitor
7 months ago
Solved

Dynamic ODBC Connection.

Hi Community,

I have a On-prem ODBC for FireBird DB, for this we have created a Gateway that can connect to this ODBC on the on-prem system.
we have around 80 such ODBC's to connect with.
So, is there any way we can have the Connection Dynamic as we have a linked service in ADF.
all my connections to ODBC are same only change is Filename.

Could any help me on this please.

  • Hello ShanthanPaladi 

     

    You can't achive it using on-premise data gateway, the right way to go about is to use a self-hosted integration runtime SHIR, which should work for ADF pipelines, since you mention you're already using it. 

     

    You can create a Linked Service using a DSN with parameterised attributes and an appropriate driver.

     

    Driver={Firebird/InterBase(r) driver};
    Dbname=@{linkedService().fileName};
    Uid=@{linkedService().userName};
    Pwd=@{linkedService().password};
    Client=fbclient.dll;
    Role=;CharacterSet=UTF8;Dialect=3;

     

    "fileName" is the only value that would be different across your 80 connections. It is best to place the user credentials in a Key Vault. 

     

    Please note, parameterised linked service won't work on Fabric data pipelines, it is only relevant if you're using Azure Data Factory. 

     

3 Replies

  • Hello ShanthanPaladi 

     

    You can't achive it using on-premise data gateway, the right way to go about is to use a self-hosted integration runtime SHIR, which should work for ADF pipelines, since you mention you're already using it. 

     

    You can create a Linked Service using a DSN with parameterised attributes and an appropriate driver.

     

    Driver={Firebird/InterBase(r) driver};
    Dbname=@{linkedService().fileName};
    Uid=@{linkedService().userName};
    Pwd=@{linkedService().password};
    Client=fbclient.dll;
    Role=;CharacterSet=UTF8;Dialect=3;

     

    "fileName" is the only value that would be different across your 80 connections. It is best to place the user credentials in a Key Vault. 

     

    Please note, parameterised linked service won't work on Fabric data pipelines, it is only relevant if you're using Azure Data Factory. 

     

    • v-menakakota's avatar
      v-menakakota
      Community Support

      Hi ShanthanPaladi ,
      Thanks for reaching out to the Microsoft fabric community forum. 

       

      I would also take a moment to thank deborshi_nag   , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

      I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you .

       

      Best Regards, 
      Community Support Team 

      • v-menakakota's avatar
        v-menakakota
        Community Support

        Hi @ShanthanPaladi ,
        Thanks for reaching out to the Microsoft fabric community forum. 

         

        I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you .

         

        Best Regards, 
        Community Support Team