MySQL Data Compare - Problem saving comparison files with very long auto-generated filename

[plindgren]

I am using dbForge MySQL Data Compare. I really like this product and I want to buy it, but I need to be able to save files.

I need to do data comparisons between two different Amazon Web Service RDS database instances. I am able to run the data comparison and generate a SQL change script. The problem is I can not save the .dcomp file. Because the AWS RDS instance names are very long, dbForge is auto generating a file name like this (not real server names):

dev_env vs test_env (development_aeaw90ala0asdtgjkasltg_us-east-1_rds_amazonaws_com through 127_0_0_1 (SSH)-3306 vs djaklsgudiatg091t_us-east1_rds_amazonaws_com through 127_152_51_1 (SSH)-3306).dcomp

And this results in this error message

The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

which would not be a problem if it let me change the file name to something shorter. But I never get that option. Can I either change how the default .dcomp file name is generated or try changing the default directory?

If I can not save a .dcomp comparison, then I need to re-create the comparison every time and I can not pay for that.

Thanks in advance

[alexa]

You can go to the main menu, select 'File -> Save *.dcomp As...' and change the file name in the 'Save File As' dialog.

[plindgren]

Hi alexa,

I tried both available options to save a dcomp file.
I tried...
"File -> Save"
"File -> Save *.dcomp As..."
"File -> Save All"
All of these options gave me a pop-up window saying:
"The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters."

I am running this on Windows 10

[plindgren]

I found a solution to my problem with long default filename generated by dbForge Data Compare for MySQL.

Solution
You need to use AWS Route 53 to create a CNAME record that is shorter than the long random alphanumeric RDS DB domain name.
http://docs.aws.amazon.com/Route53/late ... ds-db.html

Then you can use this shorter hostname in the Host field of the Database Connection Properties window. This results in a default filename that is short enough to get around the currently unavoidable Save File failure when MySQL Data Compare auto generates a filename that is too long.

By the way, this short auto-generated filename was still 147 characters long.

[alexa]

Could you please let us know if the 'Save As...' dialog opens when invoking it from the main menu? If it opens, please check that you manually specify a shorter file name along with a shorter path to the file (for example "c:\file_name.dcomp").

[plindgren]

Hi Alexa,

The "Save As" diaglog does not open when invoking it from the Main Menu.

I took some screen captures with all confidential info hidden and posted them to this shared google drive.
I will leave this public for at least one week before deleting it.
https://drive.google.com/drive/folders/ ... sp=sharing

These screen shots show in order...
1. A newly completed Data Comparison,
2. Trying to save it
3. The pop-up window with an error
I also included screen shots of the General Tab and Security Tab in the Connection Manager Window where I'm tunnelling through a Bastion server to a database server in the private subnet.

This is leading dbForge to create a default filename that is very long. I think it is similar to this default filename for when I try to Synchronize Data to Target Database and save it as a SQL file. :
dev_lift vs test_lift (fakedevdbname_rand0mAlphaNum_us-east-1_rds_amazonaws_com through 99_9_999_999 (SSH)-3306 vs faketestdbname_rand0mAlphaNum_us-east-1_rds_amazonaws_com through 98_987_987_98 (SSH)-3306)_20160920-1023

Hope this helps

[alexa]

We replied to you by e-mail on this.

[.jp]

Hello.

The problem has been fixed in 5.0.22 version of dbForge Data Compare for MySQL.

Best Regards.