You will have to have a CONNECT statement in your load script to connect to a single database at a time. It is in effect until the next CONNECT statement in your load script. So at one single point in time you will have one database connection (basically) but you can connect to multiple databases in a sequential fashion and have a new current connection to add to your in-memory data model as long as you run the load script. At run-time you will be able to connect directly to databases if you employed DIRECT DISCOVERY in your load script.
The short answer: Use a CONNECT statement multiple times.
Access Point is the web portal which presents all the QlikView applications/documents that have been published for users from QlikView Server/Publisher through a web interface.
In short: the menu to start QlikView applications
You put the URL as a link on the intranet of the company/organisation or the users get the URL directly The standard URL is http: // <qlikview-host-name> / qlikview where <qlikview-host-name> is where the AccessPoint / QlikView Web Service Server / IIS is hosted.
Do a Google search - and try it out too - also have a look at this Qlik Community content - just memorizing this is probably at best very risky. But here goes:
Cross Join combines all rows from a source table with all the rows from another table and results in a cartesian product of rows if used without a where to filter out rows in some way.
Cartesian Join could be the same as a cross join and combines all rows from one table with all the other rows of the other table. You get a N x M number of rows. Very seldom something that you want - unless you need all combinations. Could lead to memory overflow and non-responsive load script.
Self Join is when you join a table with itself which is quite useful and necessary in certain data model development situations.
A delta load also often called a differential load is a load from a table/source that only loads new rows and depending on the source and your needs also updated and removes deleted rows. For this a delta load needs to keep a history of previous loaded data in for example QVD-files or some other persitent storage.
Well i am suggesting you to do one method which will make the Qlikview to work faster also. make a qvw to load all the data files and tables and save it as qvd files.
Make another qvw for loading the data files from the qvd and make the dashboard. by doing this, you dont have to connect to the database every time you reload and saves lot of time and processing. schedule updating of the qvd files so that the tables get updated.
You will have to have a CONNECT statement in your load script to connect to a single database at a time. It is in effect until the next CONNECT statement in your load script. So at one single point in time you will have one database connection (basically) but you can connect to multiple databases in a sequential fashion and have a new current connection to add to your in-memory data model as long as you run the load script. At run-time you will be able to connect directly to databases if you employed DIRECT DISCOVERY in your load script.
The short answer: Use a CONNECT statement multiple times.
Access Point is the web portal which presents all the QlikView applications/documents that have been published for users from QlikView Server/Publisher through a web interface.
In short: the menu to start QlikView applications
You put the URL as a link on the intranet of the company/organisation or the users get the URL directly The standard URL is http: // <qlikview-host-name> / qlikview where <qlikview-host-name> is where the AccessPoint / QlikView Web Service Server / IIS is hosted.
Do a Google search - and try it out too - also have a look at this Qlik Community content - just memorizing this is probably at best very risky. But here goes:
Cross Join combines all rows from a source table with all the rows from another table and results in a cartesian product of rows if used without a where to filter out rows in some way.
Cartesian Join could be the same as a cross join and combines all rows from one table with all the other rows of the other table. You get a N x M number of rows. Very seldom something that you want - unless you need all combinations. Could lead to memory overflow and non-responsive load script.
Self Join is when you join a table with itself which is quite useful and necessary in certain data model development situations.
A delta load also often called a differential load is a load from a table/source that only loads new rows and depending on the source and your needs also updated and removes deleted rows. For this a delta load needs to keep a history of previous loaded data in for example QVD-files or some other persitent storage.
