Forum Discussion

duvenhage's avatar
duvenhage
Occasional Contributor
7 years ago
Solved

MySQL DB Connection: Initial catalog does not change

I'm trying to do DDT using a db table but TC is using the wrong db (initial catalog).   My initial connection string (used for a db checkpoint) was  Provider=MSDASQL.1;Persist Security Info=False;...
  • duvenhage's avatar
    duvenhage
    7 years ago

    This seems to be an inconsistency between TC and the db driver, i.e. not a mistake per se.

     

    When I installed and configured the driver (in Windows), I specified a db and, irrespective of what the initial catalog parameter contains, the db specified during configuration is what is used. In fact, it seems that the initial catalog parameter is completely ignored - I created a configuration in Windows without a db and it validates just fine, but cannot be used in TC because TC apparently expects it to already be bound to a db. Specifying a db in the connection string makes no difference.

     

    The solution (such as it is...) is to create a config for every db needed.

tristaanogre's avatar
tristaanogre
Esteemed Contributor

So, in your configuration in TC, you're selecting a provider from Windows that is already configured?  

Can you post the screenshots, screen by screen, as you're setting up the DB connection?  It could be resolved by simply selecting a different SQL driver in TestComplete so it uses the connection string in TC rather than what is set up in Windows.

duvenhage's avatar
duvenhage
Occasional Contributor
7 years ago

Bird's eyeview:

 

1. I installed the Connector/ODBC from MySQL because I didn't have the necessary drivers installed on my machine.

2. I configured the drivers with ODBC DataSource Administrator. During this configuration, I specified a db

 

The screenshots of setting up the db in TC are attached.

 

The connection sring generated by the wizard is Provider=MSDASQL.1;Persist Security Info=False;User ID=usrname;Data Source=MySQL_ANSI;Initial Catalog=wsgtestsim_dev

 

 

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    7 years ago

    Yup, that's your problem... instead of selecting the ODBC driver as pictured in your second screenshot, select the one for SQL server and enter the appropriate information that way.  Because you're using the ODBC driver, it's going to get all it's connection information from the configured ODBC driver in Windows.

    • duvenhage's avatar
      duvenhage
      Occasional Contributor
      7 years ago

      I've previously tried to connect via SQL Server but no matter what configuration I try, it fails. That's why I installed the ODBC Connector from MySQL.

       

      Anyway, the connection with ODBC does work and if I need to access a different db, I can add another configuration.