and tied to that is another important advantage: security.
A server connection uses all security and availability restrictions that you can imposes on a document by way of the QlikView Server.
A local connection starts QV Desktop in the background, which opens the file straightaway using File->Open. Not many standard security measures involved.
Connect to a QlikView server instead of using a local connection benefits are:
- better performances and stability
- section access is supported on server connections
- data are refreshed after a .qvw reload without the need to do a metadata reload
lech_miszkiewicz I ping you in case you would to add some info.
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.
Well as Ruggero said i can add to it a lot:
Pros fro qvp connection are:
- qvw is already preloaded on the server - it can be accessed faster
- qvw is handled by QVS service (QlikView server) which means that it will manage memory consumption accordingly and drop some cached records if it runs out of the memory (as opposed to LOCAL connection which will drain all resources untill your server dies). This is extremly important in long term when you are running production environment.
- I am 100% sure that running local connection will result in lack of resources at some point (Unless you are running 5 MB qvw on the server with 128 GB of RAM)