12-13-2013 05:22 AM
12-16-2013 10:26 AM
This could be due to the number of histories you are trying to merge, or if some of the histories are corrupted. You can try running maintenance on the database prior to the export. Additionally, to test and see if the histories are causing it, you can create another database and try the export to that database without exporting the histories and see if it goes through.
12-17-2013 05:13 AM
We have a service where we can merge 2 databases into one... and as this works on a copy feature we do not loose any History/Note/Activity/Group/Company/Contact/opportunity/Attachment/Secondary Contacts/private Contacts
if you are interested, this is the link to the service.
We do need the backup of both databases, and about 1h of your time to discuss the database changes, then the merge can run (i.e. on the weekend, so you can drop the database on Friday, and (depending on the amount of records) receive the backup of the merged Database on Sunday /Monday morning
12-21-2013 01:01 AM
Nice to get your answer here.
I can't accept your proposal because I have some security reasons. That's why I try to find right tool for the merging.
ACTDiag functionality doesn't help me, because ACTDiag or ACT! doesn't catch situation when fields property was modified directly (like fiel lenght was setting to 4000 characters). ACT! catchs it as soon as you open the property field window. ACTDiag doesn't track such "modifications" at all.
Now, I'm trying to merge two big databases by hand using ACT! merge procedure. It's funny to see the speed of merging (300 contact records per hour).
Do you have solution as a tool, not service?
12-21-2013 01:12 AM - edited 12-21-2013 01:18 AM
I was apply ALL maintenance procedures which are built-in ACTDiag (reindex, clear cache, repair database, refresh all kinds of index, rebuild metadata, rebuild security). The situation was not corrected and ACTDiag can't show me records with corrupted data. I have more then 90000 records in 2 databases in total. And if I'll starting analyze from records to records, I'll finishing under 10 years. It's not solution for me.
ACTDiag shows me that all are ok. But when I open the property some fields I find that some property was changed (like lenght of field was changed to 4000 characters). Why ACTDiag doesn't catch such corruption? I don't have an answer for this question.
My oppinion is ACT! functionality never was testing on big array of data (more then 50.000 records and more then 20 users). Otherwise, ACT! developers found solution many times ago.
It's not a claim. And I don't wait solution from Swiftpage. It's just fact which I see by my eyes.
Please don't answer me formal solution.. I'm already did it, because I'm not novice in ACT! I was trying localise ACT! 3.0 more then 10 years ago, I remember ACT! 6.0 for Windows. It was most stable version of ACT!
I was trying to create new database and only contact records was transfering to this database. But it was going with the same speed as transfering full database and I can't understand how I transfer history, notes, attachment after that.
Sorry for long comment to you.
12-21-2013 09:32 AM
I wonder why you are export 2 databases to 3rd one? Why not import into the largest existing database. With the report of a 4000 wide field is it a Char or Memo field? I have a client with 750,000 records and another with 500 users so ACT can perform at these levels.