Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
jjordaan
Partner - Specialist
Partner - Specialist

reloading through QV Server way slower then manual QVDLoader

Hi everyone,

I have strange issue which I do not understand.

So I hope someone can help or can give some advise.

We have QVDloader which is fetching data from a SQL Server and stores the data in QVD's.

When I execute the QVDloader manually the reload duration is about 30 a 35 minutes.

So the performance given the amount of data to retrieve is good.

Here comes the strange part.

When I schedule this QVDLoader in the QlikView Server (SBE without publisher and version 11.20 SR6) the reload duration is about 3 hours!!

Does anyone knows what can be the reason of this?

Thanks in advance

1 Solution

Accepted Solutions
jjordaan
Partner - Specialist
Partner - Specialist
Author

Hi David,

Sorry for my late reply.

It had to with the user that was used in the Services.

I still don't know what was the actual reason but when I changed the user it worked as expected.

View solution in original post

8 Replies
Colin-Albert

There could be many causes...

When you run the QVD loader manually, is this on the server or another machine? If you run it manually on another machine does the network route to the SQL server differ?

How many cores are allocated to reload tasks in the QMC settings?

How much ram is on the server.

Is QV server running on a physical server or a virtual?

jjordaan
Partner - Specialist
Partner - Specialist
Author

Hi Colin,

First thanks for your reply.

I have 4 QVDLoaders scheduled (4 stores) the other 3 reacts the same (executing manually or through the QV Server) only 1 QVDLoader is like mentioned above.

When I run it manually it is on the same Windows QV Server machine.

Yes it is a virtual machine with 64 GB Internal memory.

8 cores are availabe for reload.

But like I said the other 3 QVDLoaders are working as expected and the have the same behaviour when I reload manually or through the QlikView Server.

Colin-Albert

Hi Jeroen,

Can you identify any differences between the 1 app that is slow compared to the other 3?

Have you enabled log files for the QV apps so you can identify where the time difference is occurring in he manual load compared to the server reload.

Are the 4 apps reloading consecutively when scheduled on the server or at the same time?

Could there be SQL locks that cause the loads to slow down?

Can you add nolock hints to the SQL queries?

jjordaan
Partner - Specialist
Partner - Specialist
Author

Colin,

There are no differences between the QVDLoaders (they are identical only the connection string, Server name and database name are different).

The 4 apps are loading at the same time.But my testing was also loading just that QVDLoader (first loading manually 30 minutes duration and then loading through Server duration 3 hours).

I don't think SQL locks would be the problem because I tried it several times a day and every time the manually load works fine but through QV Server it isn't.

I can always add the nolock statement to my queries but personally I dont think 'that's problem.

jjordaan
Partner - Specialist
Partner - Specialist
Author

Hi Colin,

I added the table hint No Lock to my queries.

Unfortunately with no lock.

This is still the only QVDLoader which is taking so long to reload.

I few minutes ago I als so tried to do a manual reload and that reload was still way faster then reloading through the Server.

I have really no idea

jjordaan
Partner - Specialist
Partner - Specialist
Author

Hi Everyone,

Does anyone has an idea to lead me in the wright direction so I solve this problem.

I appreciate your help.

Thanks in advance

Not applicable

Hi Jeroen,

Were you able to get this resolved?  If so, what did you change?

Thanks,

DJ

jjordaan
Partner - Specialist
Partner - Specialist
Author

Hi David,

Sorry for my late reply.

It had to with the user that was used in the Services.

I still don't know what was the actual reason but when I changed the user it worked as expected.