Using Query Database Smart Service

RE: Using Query Database Smart Service

amans — Wed, 17 Oct 2018 06:07:35 GMT

thanks, I have deleted the suggestion

RE: Using Query Database Smart Service

Mike Cichy — Tue, 16 Oct 2018 13:40:01 GMT

amans This is a VERY dangerous design, please do not recommend or even suggest it to anyone. You are not only exploding the kdb cache with a series of gigantic unique strings, but you are also exploding the app server heap.
I can't think of a single use case where bringing 600K record into memory at once was a must.

RE: Using Query Database Smart Service

Shanmukha — Tue, 16 Oct 2018 04:26:22 GMT

Hi I would agree with Colton Beck and Mike Cichy . You can implement the looping concept but please note that, the more data that you are pulling in the memory is not of much use. Even if you want to do any validation on the huge records will lead you performance degrade. So I would suggest please redesign the scenario according to appian DB data best practices.

RE: Using Query Database Smart Service

amans — Tue, 16 Oct 2018 00:54:35 GMT

[deleted]

RE: Using Query Database Smart Service

Mike Cichy — Mon, 01 May 2017 15:33:44 GMT

I agree with Colton and I would HIGHLY recommend AGAINST pulling in this many records into process. The limit of 1000 is there in place for a good reason. I am not sure what you are trying to do with that data but there are better ways to transfer/process this amount of data.

RE: Using Query Database Smart Service

Vinay Kumar Rai — Mon, 01 May 2017 07:15:12 GMT

Hi,
Using of OFFSET in SQL query, which give you the functionality of BatchSize, SELECT ____________ FROM _______ OFFSET @StartIndex ROWS FETCH NEXT @BatchSize ROWS ONLY

Initially @StartIndex = 0 and @BatchSize = 1000 on the second loop Increase the StartIndex @StartIndex = @BatchSize + @StartIndex

RE: Using Query Database Smart Service

aloks0189 — Sat, 29 Apr 2017 06:27:16 GMT

BrendenH I think you should look into this URL

forum.appian.com/.../Configuring_Relational_Databases.html

RE: Using Query Database Smart Service

Colton Beck — Fri, 28 Apr 2017 13:51:30 GMT

The QD smart service caps results at 1,000. I'd recommend against pulling 600,000 records into process, but if you must, you could loop the node updating that startIndex value of the select statement until you've pulled them all.