I've been developing my DB system for a while and it has a sort of hierarchy to it. There's a parent entity with 15 columns, and there will be around 10 children inheriting therefrom. The children will then each have 15 columns of their own. This semed like a good idea to me, so that the parent and the children would all have their own tables. However, one of my users seemed nonplussed by my system and seemed to prefer a giant, 200-column DB over my system. My question is this: is it worth denormalizing my whole system for the sake of my users, or just tell him to get lost?
- Process Integration System Copy Guide Based on SAP NetWeaver 7.3 (ABAP+Java)
- System Copy for SAP Systems Based on SAP NetWeaver 7.3 ABAP
- How to create an ABAP Query based on a case scenario.
- SAP NetWeaver 7.3 System Copy Guide for SAP Systems Based ABAP
- System Copy for SAP Systems Based on SAP NetWeaver 7.0 SR3 ABAP
SAP S4 HANA Implementation Opportunity!!!
Exp :4 - 30 years | City : Chennai
SAP ABAP | Hyderabad |
Exp :1 - 3 years | City : Hyderabad
ABAP HANA Consultant Job | 5 - 8 yrs | Bengaluru | SAP India
Exp :3 - 5 years | City : Bangalore
SAP ABAP HR Certified Consultant
Exp :2 - 15 years | City : Delhi
SAP ISU EDM Consultant
Exp :5 - 15 years | City : Bangalore