Community

Exporting to a Database from Flexicapture 10 is too slow

Hi I'm using flexicapture 10 to export a batch of images to a database. it takes about 1 minute to export 1 image. 3 minutes to export 5. 17 minutes to export 30.
It should not be this slow, how can I speed it up?
For the identical project, flexilayout and images on flexicapture 9.0 it took around 30 seconds to export 30 images the same batch of images.

Other projects work fine from flexicapture 10, what is slowing it down?

Thanks
RIchard


0

Comments

4 comments

  • Avatar
    Sushi
    rhorsfield,

    Are you certain you are using the same setting? Try this. Copy the FC9 project and upgrade it to FC10. When you export does it take the same amount of time? If no, then it could be an issue with FC10 project. Talk to your local ABBYY support. If yes, then its an issue with your export setting in FC10

    Also am I correct when you say you are exporting images into the DB? So you are exporting blobs into the DB? This will slow the DB down in the long run.
    0
  • Avatar
    rhorsfield
    I upgraded the FC9 project into FC10, and all the export settings are correct, I also have 5 other projects that worked perfectly fine following an upgrade, just this one project becomes painfully slow to export. exporting from fc9 takes 30 secs, the same project to fc10 takes nearly 20 minutes. exporting field data, using "Export to Database" command, not "export to images". this is how we have always done it and for other projects.
    Richard
    0
  • Avatar
    Sushi


    So only this particular project has this problem correct? In that case, it could be project related. Without having your project, its tough to troubleshoot. I don't seem to have an issue with FC9 to FC10 exporting to SQL. I would contact your local ABBYY Support. Basically I would try the following:

    1) Try exporting to a new DB. Does that work?
    2) Map some field and export. If its quick, gradually add more fields to map and export. Maybe its one of the field causing the issue
    3) Try exporting to a different DB like instead of SQL, Access and so on

    This should help pinpoint the location of your issue.
    0
  • Avatar
    rhorsfield
    yep only this project. nothing seems to be fixing it so will contact abbyy support.
    Thanks for your advice
    Richard


    0

Please sign in to leave a comment.