Slow Query: Has 2 document type fields

lineamovil

Hello,

I have a really good application in Aware 5.3 and so far it´s looking better everyday.

After a time of use, I have noticed that a Query is showing slower and slower. The query its simple.

B.O. Invoice

FIND Factura WHERE (Factura.Creado>=?'Desde' AND Factura.Creado<=?'Hasta') OR Factura.CargoAFactura.RazonSocial CONTAINS ?'Cliente' OR Factura.Oficina.Serie=?'Serie' ORDER BY Factura.OficinaShort,Factura.Folio

BO Invoice has 2 "Document type" fields. And each record has 2 documents that are about 700Kb together.
I only have 250 records at the most for this table/BO

The other query very similar to this one (B.O. Sales), but the only diference is that it does not have "Document" type fields. And this one has no problem and loads very fast.

Im not calling the document field into the query, any suggestions?

Thank your for your help and support,

nlarson

there are several tools you can get to find out if the query is slow or if the slow down is in another part of the application. In a few recent examples a slow query turned out to be executing very quickly.

this might help:

lineamovil

thank you! I had run the Fiddler2 and I see a bunch of data, but the time to run a query is 29 sec. I have a saz file but dont know what to do.

I honestly think that the problem is the 2 document type fields in the BO. Because I have another "alike BO" that it is running smooth. No problem.

I just want to make sure that Im doing everything correct, before I remove the 2 fields in the BO. That would be a lot of work for the user to link to the file.

thank you!!

nlarson

fiddler is a client side tool, so can't tell you the time to execute a query, for that you need server side tools. If you are using MYSQL or other non-default DB's they can give you the execute time on the query. If it is low then you can look at the fiddler data for trouble spots.

aware_support

There was a similar issue that I think was fixed. Since you are using 5.2 there is a chance that your version still has that issue. Can you download teh evaluation version of 5.3, install it separately somewhere, import your BSV and try it there? If it works fine in 5.3 you need to upgrade.

I am not sure, however, that it is fixed in 5.3, so please try first before upgrading. If the behaviour is the same in 5.3 let us know and we'll investigate further.