70-450 · Question #42
You are designing the storage scheme for a new SQL Server 2008 database application The application will primarily be used to query data. The database will be initially populated with 4 terabytes of…
The correct answer is B. Use row-level data compression on the 4 tables that are loaded every night. ---Small Peter---(best answer logics) I will go with answer b. As the 4 tables get loaded every night will soon become the major factor of the storage capacity problem and page level compression will use a lot of CPU time. Thus row level compression every night for the 4…
Question
You are designing the storage scheme for a new SQL Server 2008 database application The application will primarily be used to query data. The database will be initially populated with 4 terabytes of data stored in 20 tables. The data is distributed evenly throughout all 20 tables. Every night, between 100 GB and 300 GB of new data will be loaded into 4 database tables. The remaining 16 tables will remain static. The average CPU utilization of the server where the application will reside is between 30 and 50 percent. You need to ensure that the amount of disk space used is reduced. You need to achieve this goal by ensuring minimum impact of performance on the server. What should you do? (More than one answer choice may achieve the goal. Select the BEST answer.)
Options
- AUse page-level data compression on the 4 tables that are loaded every night.
- BUse row-level data compression on the 4 tables that are loaded every night.
- CUse page-level data compression on the 16 tables that remain static.
- DUse row-level data compression on the 16 tables that remain static.
How the community answered
(37 responses)- A16% (6)
- B73% (27)
- C8% (3)
- D3% (1)
Explanation
---Small Peter---(best answer logics) I will go with answer b. As the 4 tables get loaded every night will soon become the major factor of the storage capacity problem and page level compression will use a lot of CPU time. Thus row level compression every night for the 4 non-static tables would be a good compromise. We should use row-level compression only on the 16 tables that remain static. Row-level because it is the compression type that consumes less CPU (page-level compression consumes more CPU). Full-recovery Model - Requires log backups. - No work is lost due to a lost or damaged data file. - Can recover to an arbitrary point in time (for example, prior to application or user error). Work loss exposure - Normally none. - If the tail of the log is damaged, changes since the most recent log backup must be redone. Recover to point in time - Can recover to a specific point in time, assuming that your backups are complete up to that
Topics
Community Discussion
No community discussion yet for this question.