Discussion Board for collaboration related to QlikView App Development.
I created my data model in 2nd layer.
So I don't want to call that as binary load in another qvw file rather on 2nd layer only I will create dashboard..
If any suggestions wts the advantage if I use it as binary and create only front end in different dashboard.
Please exprets can comment bcs, I felt why to unnecessarily increase one more layer in the name of 3teir architecture..
IF really needed whats the advantage (anything like dashboard on 2nd layer may b 200 mb and if used binary might become 100mb )..
Request you to comment with valid proofs why Binary wt it ll do?
why should I create 1more layer? which will increase my task running time by adding 1more application?
Why Qlik recommend 3layer..(nt looking fr docs as I have many but need justifications)
Else I think in 2nd layr we can build dashboard..Plss comment as its going to effect entire my organization??
"Or its just a statement to load 1 QVW file into other??"
It just loads the datamodel from the source QVW, producing the exact same physical data model in the target QVW. The resulting model is not smaller or optimized in any way by BINARY,
The key word here is BINARY -- meaning the datamodel is copied in it's physical internal storage format with no logical processing of the contents.
You can. We do, but... Now after a few years I wish we had used the 3 layer approach.
It might seem unnecessary when setting up apps first but after a while you see where the benefits would have come in.
From being able to reload/distribute a user facing app quickly and easily, to tidier variable maintenance, or more flexibility on reloads or concurrent maintenance on UI and datamodel. Its current 'best practice' because of peoples experience. Its not a regulation or requirement.
Thomas-Thanks fr ur reply..
reload/distribute----->I think in 2layr its cuts one more layer so 2layr saves time I guess..
And at the end in 3 layr what we say,when u call ur 2nd lyr data model as a binary its internally all data model will b residing inside 3rd layr..
Does any one has any idea on advantage of Binary load or is it a just a statement to call 1 qvw in other??
Its depends on your requirement and the complexity of the data sdmech81 . Why we go for 3 layer is if we have huge data ,transformation and business logic to implement then this is must needed . so that the architecture will be very clean .
1.Layer will be only the extract from the source
2.Layer all the business logic , transformation and Aggr of data (If required)
3. UI layer
you would merge the 2 & 3 but Imagine if you want to change business logic then you need to touch the UI layer also and what if you want to show only the Aggr data in the frontend UI then merging 2 and 3 doesn't make sense rite ?
binary load has lot of advantages
2.If you have the common transformation or what to show to different data in a single dashboard then no need to do the rework again just binary load that file
3.you don't need to share the DB details of the binary load file it will be completely secure
Thanks fr reply,
I have used 2layr and 3 layer based on need.But if I merge 2& 3 the ,1 layer is cut and then faster reload and also lesser complication and also easy handling as both datamodel and front end in same file.
So my question is will tht Binary statement has any advantage or its just works with same speed as loading the data fromQVD's.
Bcs many places i found simply in the name of 3-layr architecture saying nt useful..
And in case 2&3 are merged also back end is a different thing and front UI is different one.So i ll touch them as per the need.Like hw i do whn 2 & 3 are different.
sdmech81 as I said it depends on your requirement if you get a chance to see the Banking Domain apps then surely you will get to know the advantage of 3 layer .
So my question is will tht Binary statement has any advantage or its just works with same speed as loading the data fromQVD's
I belive It's more faster then the QVD's
I agree on few things.
Security plss alaborate..With respect to enterprise level implementation where all QVW files reside on server and all use through access point.Yess if dashboard.qvw can b stolen then 2nd layer.qvw can also be stolen.
Yess at the end it depends on situations I thinks.
And I don't thing any speed boost using binary load..I haven't seen them..infact by doing tht we r consuming more memory and loading same size twice.
SO I think its better to go binary,if same datamoel is used repeatatively I guess.
Is there any doc on Advantages of binary from QLiktech ?