Dear Alex,
its a decision making time, to go with ClassTable approach or concreteable approach.i read few of your posts and got some queries,pls advise.
- i have maximum four level inheritence, ie. Entity -> BusinessEntity -> Workstate -> PersonalPermission.
- DO 3.x was using classtable approach, n hence it used to create table for "Workstate" and used to create view for "PersonalPermission-view".
3.Now the class table approach does not create any view, infact creates both "workstate" and "PesonalPermission" as tables...This mean that we have to create views manually so that we can use it for Reporting, for support engineers, so "join" are always an overhead.
- if i go with concretetable approach then my Reporting enginer and creating views problem will be solved but then whenever i need to access "Workstate" object, it will make Union of all derived tables , and as u explained that Indexing part in one of ur posts, then it will have negative effect on performance.
- plus the base table like "Workstate" will be created but it will be empty table with no rows.
- lastly, sometimes i need base object to be returned, instead of exact types.
Please advise, which approach should be better for above requirements. which one is better optimized "joins" or "Union" query. i have to make decision keeping in mind performance, Reporting, and support engineers. so please advise.
thanks
HAN
asked
Nov 03 '10 at 08:46
HannanKhanji
54●14●13●17
Dear alex, i am waiting for your valuable advice.
Hi,i am waiting for your support.