Hi Wesley,

At present command time-out cannot be overridden, any query that legitimately takes 2 minutes to run would likely bump up against a memory limitation in the engine regardless.

Are you able to chunk the queries into multiple runs of the same job?

Part of the issue is that we are running over a vLAN to another office location.  We had tried installing IMAN close to the data, but had to re-locate it so it was in the same office as our Accpac installation, as we ran into different timing problems with that configuration.

The volume of data itself is not terribly large (currently under 5000 records), but due to the latency of the network, and the processing SQL server must do to prep the data in the query (the application it is pulling from is not terribly billing friendly), it is simply time consuming.

Are there any workarounds to this time limit?

Thanks again,

Wesley

Wesley, I understand.

We made a patch for one client, but we didn't role this into the core product as it doesn't work well with the design portion of IMan....you end up getting UI/Threading/Locking issues...and this is the reason the timeout is set to 30 seconds as the UI times out after 30 seconds.

The size of the records isn't an issue here.

Would it be possible for you to run a command to first stage the records into SQL, then use IMan to process the staged records?

Hello again,

In your opinion what would be the best way to structure a staging process?  I would like to have it configured so in the event of a failure we can make this user-runnable with the least amount of steps for them to perform, but I don't know what IMAN would work best with to know if that's a good goal or not.

Would we be better off to make a stage table (I would assume the user would have to then generate that stage table somehow, and then go into IMAN to run the job), or have our staging process instead build a file that IMAN could watch for (which then they would probably just have to generate the file and wait)?  Would we run into issues if the writing to the file takes a while over the vLAN or does the IMAN file watcher know the file is still being written to?

Or is there another staging option that may work even better than these two options that i'm not thinking of?

Cheers,

Wesley

Wesley, from which type of database are you querying the data? Is it SQL or something else?

Just trying to figure the best solution.

Yes it is SQL Server 2008 R2.

Cheers,

Wesley

Hi Support,

Can you provide me with the patch to increase the SQL timeout please. Client is on SQL2008 SP2 and we have some hideous views pulling data from Goldmine. Query consistently runs in around 40 seconds, so if you could provide a 60 second timeout that should work nicely. Urgent, as usual!

Thanks,

Martin

Hello again,

Have you had any luck determining what would be the best route for us to stage the data with our setup?

Thanks in advance,

Wesley

Closed due to inactivity.