Table 'mysql.proc' doesn't exist

Question

Table 'mysql.proc' doesn't exist

Anargh V 1

MySql Client always throws the error "Table 'mysql.proc' doesn't exist", when a stored procedure is being executed. The weird thing is this error is thrown only in our Production server which is running on "General Purpose" pricing tier. Our staging server which runs on "Basic" pricing tier does not have this issue. Both production and staging is running under Single Server configuration.

There is a solution posted for this under https://learn.microsoft.com/en-us/answers/questions/25786/table-mysqlproc-doesnt-exist.html
however I want to understand why this issue exist in General Purpose tier and not Basic tier.

GeethaThatipatri-MSFT 29,542 Reputation points Microsoft Employee Moderator

2022-09-09T13:11:23.737+00:00

Hi, @Anargh V Welcome to the Microsoft Q&A forum, Thanks for posting your question.
Can you please confirm your MySQL version?

Regrds
Geetha
Anargh V 1 Reputation point

2022-09-09T13:25:47.523+00:00

Hi @GeethaThatipatri-MSFT ,
Thanks for the welcome.
To answer your question, both prod and staging servers are running 8.0 versions of MySQL

1 answer

Your answer

GeethaThatipatri-MSFT 29,542 Reputation points Microsoft Employee Moderator

2022-09-09T13:11:23.737+00:00

Hi, @Anargh V Welcome to the Microsoft Q&A forum, Thanks for posting your question.
Can you please confirm your MySQL version?

Regrds
Geetha
Anargh V 1 Reputation point

2022-09-09T13:25:47.523+00:00

Hi @GeethaThatipatri-MSFT ,
Thanks for the welcome.
To answer your question, both prod and staging servers are running 8.0 versions of MySQL

Answer 1

GeethaThatipatri-MSFT 29,542 Microsoft Employee Moderator

Thanks, @Anargh V for confirming the version

This error 'Table 'mysql.proc' doesn't exist' occurs when you migrate the database from version 5.6/5.7 to version 8.0.

In most cases, the Gateway returned version should not impact anything when using Azure MySQL server. However, in some cases when calling a stored procedure from an application, such as CommandType.StoredProcedure in .Net, version 5.6.42 will be detected and then will lookup mysql.proc to fetch relevant stored procedure information. But, MySQL 8.0, does not have the table mysql.proc anymore, which is why the above error is reported.

In MySQL Ver.8, stored procedure information will be stored in the mysql.routines and mysql.parameters tables, which are part of the data dictionary. You cannot access these tables directly. Instead, query the INFORMATION_SCHEMA ROUTINES and PARAMETERS tables

You can also try the following two workarounds from the application end to mitigate the issue:

Specifying CheckParameters=false in application connection string.
Specifying in the application connection string the port 3309 instead 3306. More information you can find here

Please let me know if you are looking for any additional information.
Regards
Geetha

Please don't forget to click on or upvote button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer.

Anargh V 1 Reputation point

2022-09-09T13:51:35.577+00:00

Thanks for the clarification, that makes sense, but this is for a completely new .NET 6 application and we had not performed any migrations.
And as mentioned previously, this error does not get thrown for our staging servers, and it is only in the production server this issue is observed. The only difference
between them I would say is the pricing tier. If you could provide any insights there, would be really appreciated.

The MySql.Data client version is 8.0.21
and MySql server is running version 8.0

Let me know if you require any additional information for this.
GeethaThatipatri-MSFT 29,542 Reputation points Microsoft Employee Moderator

2022-09-09T14:09:34.95+00:00

@Anargh V Thanks for the additional information let me check with the internal team and provide you with more details.

Regards
Geetha
GeethaThatipatri-MSFT 29,542 Reputation points Microsoft Employee Moderator

2022-09-13T11:53:46.76+00:00

@Anargh V Thanks for being patience
Can you please share the query you have executed when throwing the error
also, try connecting different client versions if it might help fix your issue,
https://stackoverflow.com/questions/55290077/mysqlexception-table-mysql-proc-doesnt-exist-when-executing-mysql-stored-p

Regrads
Geetha
Anargh V 1 Reputation point

2022-09-15T10:08:00.593+00:00

Apologies for the late reply, let me check this and get back @GeethaThatipatri-MSFT
GeethaThatipatri-MSFT 29,542 Reputation points Microsoft Employee Moderator

2022-09-20T14:41:30.243+00:00

Hi, @Anargh V We haven't heard back from you. Just wanted to check if you find the above reply useful. If yes, do click on the 'Mark as answer' link in the above reply. This will help other community members facing similar queries to refer to this solution.

Regards
Geetha

Share via

Table 'mysql.proc' doesn't exist

1 answer

Your answer