2. Star schema is the typical one building fact/dimensions, where your dimensions are linked to the fact table (Mainly with surrogatekeys). When you have a SnowFlake schema multiple/one dimension is related to another dimension.
4. You could optimize your app in serveral ways. Try to eliminate complex expressions - Make sure you application only contains the data you need. - QVD files is loaded much faster - Make as much logic you can in the backend (i dont like Qlikview as both backend/frontend tool - I see it as a frontend tool)
6. Slowly changing dimensions. Typically you use SCD1 or 2. When you use 1 its typically when for example you have a product dimension. Let say ProductID 1 is called Cola, but next year productID 1 is called Coca Cola (but its the same product) Then you want to update your dimension with the newest name - Then you use SCD1. SCD2 is quite common if you want historical data. Lets say you have an employee.
EmployeeID 1, Name Thomas, Sales Denmark
Next year i switch department so my data is now:
EmployeeID 1, Name Thomas, Sales Germany
Here you maybe want to keep both because you might still wanna know where i was one year ago, because you still wanna see how i performed when i was in Sales Denmark or know where i was.
For example, create a calculated dimension in a straight table:
=ValueList('KPI1','KPI2')
Then, an expression like
=pick(match(
ValueList('KPI1','KPI2')
,'KPI1','KPI2')
,sum(FIELD)
,count(FIELD)
)
You'll get a dimension with two value, KPI1 and KPI2. To check in your expression, which is the current dimension value, you'll need to repeat the Valuelist() function as used in the dimension again in the expression. (Above can also be written as
The Server was the analytic part; the QlikView engine that gets requests from clients on selections in the data model inside a qvw file.
The Publisher was the administrative part: user management, file distribution, scheduled reloads etc.
However, both the server and the Publisher are nowadays merged together in the same software package, so you cannot always say that a specific module belongs to one and not the other.
But the two licenses are there: If you have a server license only, you do not have all the administrative tools, e.g. you cannot distribute files (chop one master file up into several user documents). But if you have both server and publisher licenses, then you have full administrative capability.
10: I havent had any problems but be sure the newest version supports your users browser/OS and so on.
see like we change dimensions alternatively on the axes of chart
4.drill down:dependent event.
see for example if we selected india in list box the states a.p,karnataka,madhyapradeh etc will appear in axes of the chart.i.e drilling to next level.
2) star schema looks like star it has 1 fact and multiple dimension tables.dimension tables are de normalised.
snow flake schema is having 1 fact and multiple dimension tables.dimension tables are normalised.
3) in groups we have multiple dimensions so it won't get.
4) do some logics in script level, and ui level also do some techniques to do optimized.
remove synthetic keys and circular ref and do some techniques in script.
5) you will get it from community there are so many answers.
6) SCD is a dimension which can be changing over by the time that is called SCD.here we have one concept that is intervalmatch() here we can achieve this.
7) For example, create a calculated dimension in a straight table:
=ValueList('KPI1','KPI2')
Then, an expression like
=pick(match(
ValueList('KPI1','KPI2')
,'KPI1','KPI2')
,sum(FIELD)
,count(FIELD)
)
You'll get a dimension with two value, KPI1 and KPI2. To check in your expression, which is the current dimension value, you'll need to repeat the Valuelist() function as used in the dimension again in the expression. (Above can also be written as
😎 Recno() is unique number it will assign a number when the record enters into QV.
rowno() it will change every time when you apllied any where conditions ETc.
9) Server will host the qv documents. publisher will use for sending the reports in the form of PDF or Any Format. using publisher we will send the reports to users who are in outside domain.
10) Macros and triggers will not work in AJAX mode
