[BUG] dbForge Studio 2020 MySQL Enterprise - Importing Simple CSV file takes nearly 2 minutes

[Requnix]

Version: 9.0.391
Platform: Windows 10

When I try to import a CSV file with the below structure and 5,000 lines, it takes nearly two minutes for the IDE to go from the Source File>Destination process (hanging the entire IDE in the process). Once you get to the Destination process, everything is nearly instant. Something seems very wrong with the "file check" stage. Note this happens with all CSV files.

Below is a shot of the structure from Excel; nothing weird about it. 5,000 lines.

[alexa]

Unfortunately, we were not able to reproduce this issue.

We recommend you to check the system's performance in Task Manager.

[Requnix]

Version 9.0.435

Here's a video of the issue:
https://www.screencast.com/t/x42uyUQY0Twd

[alexa]

Are you also experiencing this issue with other formats?

Please also provide us the servers' versions.

[Requnix]

CSV is the only format we're using.

This is MySQL version 8.0.16.

[alexa]

Could you please also try any other file format? Are there any connection delays.

Please also check that you are using the latest version 9.0.435 https://www.devart.com/dbforge/mysql/studio/download.html

[Requnix]

My apologies; but these CSV files are the only formats I have, and I posted the version above (I am using the latest). I think it could be a connection issue, but haven't been able to verify.

[dzhanhira]

Could you please enable logging, reproduce it and send us that log file,
to enable logging in dbForge Studio for MySQL you need to:

1. Open in thetop menu "Tools" -> "Options"
2. Select "Environment -> Output Window".
3. Enable the options "Write queries sent by the program to the SQL log" and "Log application errors".
4. Disable the "Delete application log after closing" option ---> Click "OK"
5. Open that procedure.
6. Send us that log file with the current date from the directory:%SystemDrive%\Users\%UserName%\AppData\Roaming\Devart\dbForge Studio for MySQL\.

[Requnix]

Unfortunately (or fortunately! :) ), I cannot get the error to reproduce with the latest version. I'll let you know if I encounter it again.