Replacing load from BAT with QV server scheduling

[#1]

Hi,

I have an application which was executed on a personal edition.

There is a BAT to reload 2 QVWs: one QVW is for creating QVDs,

and the other QVW has the user DAR.

Now the application has to be run from a QV server.

Is it better to replace the BAT with two similar tasks?

Are there any Pros, Cons or things to be aware of?

Thanks in advance!

[sujeetsingh]

As till i think tasks will be more beneficial.

[Colin-Albert]

Running the reload as a task from QV Server will enabling logging of the task in the QlikView logs and will allow you to configure email alerts if the job fails.

You will also have an indicator on the QlikView Management Console (QMC) Status screen, for any failed jobs.

You can also set dependencies between the tasks, so the DAR reload can be set to run on completion of the QVD reload.

[#4]

Is there a way to control that the second task will be executed after the first one is completed?

[#5]

I found a thread for that one:

[Peter_Cammaert · Accepted solution]

Pros:

- you can power down your PC, no more wasting electricity. A qlikview server is up 24hrs anyway.

- great task management through the QMC, even remotely. You'll love the clean UI.

- easy task chaining. You found out about that yourself.

- greater flexibility, especially if you have a Publisher.

- multiple parallel reloads

- automatic publication of documents via the AccessPoint

Cons:

- a document reloaded by the server cannot be opened in PE anymore, as the server is a licensed user.

IMHO it's always better to let the QVS take care of tasks that should be automated anyway.

Good luck,

Peter

[#7]

Thanks a lot Peter!