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?
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.
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?
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.