1, not sure what you looking for - a technical explanation?
2, During execution of the load script.
3a, During the execution of the load script b) automatically through naming the fields.
4a, Power off and you need to reload, yes. b) Server cluster (power off both servers and you still need to reload...)
Download a free demo and try it, you won't regret that.
"reload" is a QlikView term for when data is brought in to a qvw application using QV:s load script.
When you are reloading you can see memory consumption rise and fall, according to what you do in the load script
After a "reload" you can save the application, and when you close it all memory used by that application will be released.
The next time you open that application you will also load into memory all data exactly as it was when you saved the application. (no qlikview reload needed)
so I would like to add to Thomas answers:
2) ...or when opening a saved qvw application
4) You do not have to reload the data for an application if the application is saved before power off, you just have to open the application
The only place you use sql in QlikView load script is when you are fetching data from an sql database.
Otherwise you use QlikViews proprietary scripting language (I've never heard a name for it...)
It is defined and explained in the QlikView Reference Manual, and also in the help that's included in QlikView.
Then there is also a "Macro script" part which you can program either in VBscript or Jscript.
For basic applications you will not need macro scripting at all.
- The data is loaded from the source when you do a load. For users, the file is loaded into RAM when they open the file, just like any other file. In a client server environment, you can preload files into RAM as well. QlikView also caches data, I believe even for files you have closed.
- To clarify an earlier answer, the associations are made at the END of the load script. Until then, as best I can tell, QlikView makes no attempt to associate your tables. This seems logical, as until then, you cannot be certain of any associations.
- If you turn the computer off, you no longer have the document in memory. To put it back in memory, you need to boot the computer and open the document. There's nothing special about QlikView files in this regard. They're just files.
"what type of languages or scripts we can use in the script editor apart from sql like jscript or vb etc."
QlikView Script. It has its own scripting language. I agree with GandalfGray that you won't need to code macros for basic applications.
Hi shantheguy ,
Please see below for some information on the load process...
The data records are read into the memory, so that all the processing of data may be done through memory. I am sure you know this bit. QlikView treats all the data as Data Element Type (Columns / Fields) and Data Element Values (Values / Records). So each different data element value of each data element type is assigned a binary code and the data records are stored in binary-coded form and they are also sorted. By using the binary coding, very quick searches can be done on the tables. Also, QlikView removes the redundant information information and reduces the amount of data. However, the redundant information in stored as seperately with the frequencies for each unique data element value and across each data element type. When user makes a selection on data element values then the implied selection (possible values) are kept track seperately to present them to the user. By this process QlikView can perform rapid linear searches.
I understand this is not in detail but just a quick overview. I hope this helps!
Cheers - DV
The "associative logic" works like this:
Any fields that have exactly the same name (case sensitive also) are associated (connected) unless you specify otherwise by using a special command (Qualify)
The "associative query language" is essentially what you can do in QlikViews Load statement.
Startup QV and go in to the integrated help and read about the Load command!
Download a few sample applications and have a look at them.
Thank you i have one more query
for suppose I have some data like(example)
studentid name group
1 gendalf computers
2 shankar physics
3 gray chemistry
i have read the associative model stores the data as items and links
how this data will be stored in the associative database. where the columns will be stored and where the data will be stored?
please help me...
Consider you have table like this.
Student, Subject, Marks
A, XYZ, 10
A, PQR, 20
A, JKL, 30
B, XYZ, 30
B, PQR, 20
B, JKL, 10
The above table will be stores as
Student Subject Marks
A XYZ 10
B PQR 20
There will be 3 fields as shown above with distinct reocrd.
Now there will also be a reference values which will link this 3 fields.
The advantage of this kind of storage is it will reduce the data size.
Hope you understood.