Home/ Questions/Q 6150221
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T19:35:13+00:00

Greeting and Salutations! I work in an environment where I have a development server,

  • 0

Greeting and Salutations!
I work in an environment where I have a development server, QA server and a production server. I’ve recently ran into issues because I would like to work locally and have my local development connect to our development server. When I deploy to our development server I want the data connection to continue to connect to our development server but then when I deploy to our QA or production, I want it to connect to the database sitting on that current server.

I’ve come up with a solution that using an ODBC data source to connect to the SQL instead of using standard SQL data connections is the easiest way to manage this. This means changing my connection string, along with using odbc ado.net instead of SQL ado.net.

My question is, is there any downside, limitations or performance loss with using ODBC connections over standard SQL connections? Will this prevent me from using LINQ / Entity framework later on?

Thanks,
Paul

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Ok, I figured it out on my own. I did a benchmark of the code using the SQL driver against the same exact code using the ODBC driver.

    My results are below.

    • ODBC DRIVER: 100% connection success. Average duration 796
      Millisecond.
    • SQL DRIVER: 100% connection success! Average duration
      641 Millisecond.

    The ODBC driver performs slightly slower. I still might use because this benchmark was again 20 thousand records so the difference should be very minimal.

    Thanks you all for your help!

    Paul

    • 0