What is current recommended method for migrating from IDimager V5?

[mjbiggs]

Hello

Having recently purchased Photo Supreme V3 64bits, I am attempting to migrate my IDimager V5 catalog/database over to Photo Supreme.
(I am running it on Windows 7 Professional 64bit laptop)

I am a little unsure of the best method/combinations of methods to use:

The first method I found was as per the forum post "Migrating from IDimager V5 to Photo Supreme", posted by Hertz, 18 Sep 12 14:10.

Then, in the IDimager Resource Repository, I found the entry "After IDImager V5 conversion to Photo Supreme", released 2016-01-17, script 'After IDimager Convert.psc', with the note that this is "MANDATORY FOR CONVERTED DATABASES".

Then, I noticed in Photo Supreme itself there is the option Tools->Restore from an IDimager Backup Catalog File

Please can someone verify which is the current recommended method.

Mike

[Mike Buckley]

The post and script that you mention are authored by the same person, the developer of the two products.

Notice Step 15b in the post that you mentioned. I believe that script is the script in the Resource Repository that you mentioned. You can easily verify that by downloading the script and loading it into the scripter.

The Restore function that you mentioned has nothing to do with migrating from IDimager V5 to Supreme. You would use that function when something has gone so awry with your catalog that you want to restore a backup catalog. You may also want to use the Restore function if you are using the software on a second computer such as a laptop in Travel mode.

Depending on the size of your catalog, keep in mind that Steps 11, 14 and possibly 15 (I don't remember) could take a long time.

I used the migration method and it worked very well for me. Hope the same is true for you!

[mjbiggs]

That's great, thank you. Can now proceed with confidence.

Thanks too for your incredibly quick reply.

Mike

[fbungarz]

Hi at the two Mikes...

Well, now I AM confused!

Hert's instructions at http://forum.idimager.com/viewtopic.php?f=65&t=18225 do not mention a script called "After IDImager V5 conversion to Photo Supreme" (= After IDimager Convert.psc) AT ALL.
All these instructions say is that it is recommended to rebuild the search data via

Code: Select all

After IDimager Convert.psc

However, on the Resource Repository site (http://scripts.idimager.com/cgi-bin/idi ... 05490134ef) it says:
IMPORTANT; RUNNING THIS SCRIPT IS MANDATORY FOR CONVERTED DATABASES. RUNNING PSU WITH A CONVERTED DATABASE WILL GIVE INACCURATE RESULTS

If running this script is so important for converted databases, why is it not mentioned in the instructions? I have been working with my converted catalog three weeks now, compacted it several times, re-built the search data a few times. I have not noticed any odd behavior apart from that my catalog database has been growing substantially in size (http://forum.idimager.com/viewtopic.php?f=57&t=24089) and, presumably as a result (!?), has become a lot slower, i.e., performance seems to be affected quite strongly by a much larger catalog...

Well, now I start wondering, if the performance decrease is not so much related to the enormous size increase, but perhaps because I have not run the 'After IDimager Convert.psc' script...

Hert - can you please clarify if running the script is still necessary OR if following your instructions (where the script is NOT mentioned) is sufficient...

Thanks!
Frank

[vlad]

in Photo Supreme itself there is the option Tools->Restore from an IDimager Backup Catalog File

For what it's worth, I think the wording could be improved, to avoid ambiguity (especially for users migrating from the old IDimager product). Something like "Restore from a Photo Supreme catalog backup" (or, simply, "Restore from a catalog backup") better conveys the function, imho.

[Mike Buckley]

This situation about the two scripts is indeed very confusing. The two scripts are not the same, as I assumed in my earlier post. The script in the repository includes the script in Step 15 as well as other stuff.

I don't have the script stored in the repository on my system, so I assume I never ran it. However, I migrated so long ago that I really don't remember. Edit: I just now remembered that I migrated to Supreme V2. The script in the repository is intended for migrating to V3, so I'm very sure I didn't use it.

[Mike Buckley]

For what it's worth, I think the wording could be improved, to avoid ambiguity (especially for users migrating from the old IDimager product). Something like "Restore from a Photo Supreme catalog backup" (or, simply, "Restore from a catalog backup") better conveys the function, imho.

The Restore function can also be used when using Supreme on a second computer in Travel mode. My point is that using that function is not limited to using a backup catalog.

[fbungarz]

The script in the repository is intended for migrating to V3, so I'm very sure I didn't use it.

Well, in that case I would really like to know if I should actually still run it. Because I migrated from IDI v5 to PSU v3...
Hert - could you please confirm if users migrating to PSU v3 should run this scriot or not?
Thanks,
Frank

[Hert]

IDimager users should run the script once. But you already did run it, just not from the repository.

[Mike Buckley]

The two scripts do not appear to be the same, Hert.

[fbungarz]

I still am confused. PSU3 opens IDI5 databases and converts them on the fly. Does the script in the repository do the same?
The only script I ever ran was the re-build search data...

[Hert]

All that's really important is to build the search data.

[Mike Buckley]

All that's really important is to build the search data.

To clarify that comment for others, the search data is built by the script stored at the repository and the script stored at the sticky thread that explains how to migrate from IDimager to Supreme.

[fbungarz]

I think a note should be added to the instructions on database migration and also in the IDI repository: in my experience running the script after having successfully migrated to PSu blows up the database size enormously, slowing down how the program works. I am not sure, if that would be the case running the script immediately after database conversion, but running the script aver having used a converted database for several days is, in my experience, certainly counterproductive!