Uploaded image for project: 'MariaDB Connector/ODBC'
  1. MariaDB Connector/ODBC
  2. ODBC-349

speed issues and IIS crashing

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 3.1.15
    • None
    • General
    • Windows 10 Pro with MariaDB 10.6, Apache 2.4 (Apache is mostly used as proxy), IIS 10, PHP 8.1, Code on IIS is ASP Classic (VBS). Hosted by VritualBox, dedicate 6 Cores and 5029 MB of memory.

    Description

      I have been struggling finding the right ODBC driver after this server meltdown. I ended up upgraded from MariaDB 10.1 to MariaDB 10.6.

      Before the upgrade IIS was fast and reliable. I used to connect ASP to MariaDB 10.1 in two ways: MySQL ODBC 5.1 Driver, and MariaDB ODBC 3.0 Driver. Connection string was:

      {{"PROVIDER=MSDASQL;DRIVER=

      {MySQL ODBC 5.1 Driver}

      ;port=3306;SERVER=localhost;UID=;PWD=;database=_;Option=3"}}

      {{"PROVIDER=MSDASQL;DRIVER=

      {MariaDB ODBC 3.0 Driver}

      ;port=3306;SERVER=localhost;UID=;PWD=;database=_;"}}

      –
      Now on MariaDB 10.6 I have tried myodbc8w.dll MySQL ODBC 8.00.27.00 Unicode Driver which is fast but it crashes IIS after 1 or 2 days (not just the Application Pool but IIS!)

      I also tried maodbc.dll MariaDB ODBC 3.1.15 but it is slow (it takes 4x longer) and it crashes the IIS Application Pool every 2 to 3 hours in.

      Link to my related post

      I am getting errors such as:
      MariaDB EventID 100: Aborted connection _ to db: '' user: '' host: 'localhost' (Got an error reading communication packets)

      Attachments

        Activity

          People

            Lawrin Lawrin Novitsky
            MeSo2 Nathaniel Courtens
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.