Q: 5
You are given the following information:
1.
The data source "spfli" on line #2 is an SAP HANA
database table
2.
"spfli" will be a large table with over one million rows.
3.
This program is the only one in the system that accesses
the table.
4.
This program will run rarely.
Based on this information, which of the following general
settings should you set for the spfli database table? Note:
There are 2 correct answers to this question.
1.
The data source "spfli" on line #2 is an SAP HANA
database table
2.
"spfli" will be a large table with over one million rows.
3.
This program is the only one in the system that accesses
the table.
4.
This program will run rarely.
Based on this information, which of the following general
settings should you set for the spfli database table? Note:
There are 2 correct answers to this question.Options
Discussion
C/D tbh. Row Store is best for full row reads, and "Page Loadable" makes sense since the program runs rarely and you don't want to waste memory. If this was about analytics or more frequent access maybe I'd pick A/B, but not here. Let me know if anyone's seen different.
C or D. I figured Row Store (C) is right since every row gets read, but part of me thinks Column Store (A) could help with speed due to the huge table. Not 100% sure, open to corrections.
C/D? Row Store is better for this access pattern since you're loading full rows, not just a couple columns. Page Loadable matches Row Store for rare, on-demand reads so you don't waste memory. Not 100% but that's what most SAP training recommends for these scenarios. Disagree?
C/D make sense-Row Store is best when you're reading whole rows, and "Page Loadable" avoids loading the full table into memory for something that barely runs. That's straight from SAP best practices as far as I know. If it were constant analytics, then I'd maybe rethink it. Anyone seen a different setup work better for rare batch jobs?
C/D? Full row reads on big tables are faster with Row Store, and "Page Loadable" fits rare access patterns so the table isn't always sitting in memory. If it hardly ever runs, you wouldn't want resources tied up for nothing. That's what I've seen recommended in SAP ABAP training docs. Anyone got a real-world case where A/B was actually better here?
Makes sense to pick C and D here. Since the table's mostly accessed in full-row reads and it runs rarely, Row Store plus Page Loadable avoids keeping the whole thing in memory all the time. Wouldn't really see performance gains from Column Store if there's no column-specific stuff happening. Pretty sure that's SAP's preferred approach for such use cases, but open to other takes.
Why not A? If the table grows much larger and column-specific operations come up, wouldn't column store make more sense then?
Probably C and D, B is tempting but Page Loadable works with Row Store for full row reads like this. Seen similar in practice exams.
To be sure, what method does the program use to access data, and does it ever select only a few columns or always all columns? If it filtered specific columns frequently, Column Store (A/B) could actually fit better.
Be respectful. No spam.
