It's hard to say without seeing the actual error, where it happens and what versions of Laserfiche are involved. But your query has the potential of returning the entire repository.

Is there a reason why you need Workflow to do this migration instead of using the Laserfiche Repository Oracle to Microsoft SQL Server Migration Utility or briefcases?

Hi Miruna,

Thanks for getting back to me. I am getting "Error encountered when receiving an HTTP response" only in the workflow. Also, in my workflow, I'm giving to fetch the first 2/10 results only. Do you think it still goes and search for the whole repository?

Version- Using workflow 10.4 to fetch repo from 9.2 to transfer to 10.4

Our repository size is too large more than 2 TB. Do you think Migration Utility/briefcases will still work for us?

After consultation from Laserfiche Engineering, we were advised that the standard Microsoft provided Oracle to SQL data transformation utility cannot successfully achieve a working SQL migrated repository database and that a ‘one-off’ workflow driven migration is required for both repositories.

Hi Mehak-

Not sure if you've figured out workarounds, but a couple of thoughts that might be helpful.

• Don't search for everything. Instead, do it by folder or template or some other way to logically keep track of breaking this down into smaller tasks.
• I've had some weird issues when trying to run things in parallel or migrating folders this way. I finally gave up and went with the slowest option of one document at-a-time. That may be something specific to my environment, but at least it gets everything successfully. For context: the error is that the document would store fine, but there would be a SQL error when trying to set metadata, so the entry would be migrated without its template/metadata. And it would only raise a warning, so it was very difficult to track down and fix problem documents.