Running Head: DATA WAREHOUSING 1

Tuning Data Warehouse

Student’s Name

Course Name

Institution

Date
DATA WAREHOUSING 2

In the future, the type of query users will use to post data is increasingly becoming

unpredictable as the data warehouse is evolving. Therefore, it is challenging to tune a data

warehouse system. The phrase “Tuning data warehouse” defines the processes of selecting

suitable optimization techniques while creating or updating queries. The phrase also defines the

processes of making queries run faster. Turning data warehouse maximizes the use of resources

when queries are being executed (Raza et., 2018). Complex queries usually access data

warehouse for significant business operations in seconds but not days. Physical designing and

tuning are necessary for continuous improvement of query performance. In the physical design,

the data warehouse administrator selects advanced index schemes, horizontal partitioning,

materialized views, vertical partitioning, denormalization, and parallel processing, among other

optimization techniques (Bellatreche, 2009). The process selection is based on typical updates

and the most frequently asked queries. The physical design creates a configuration with various

optimization techniques and can evolve as data warehouse changes dynamically through time.

Tuning data warehouse instances include performance assessment, data load tuning,

integrity chack, turning queries, fixing queries, and ad hoc queries. Performance assessment

measures memory usage per process scan rates, average query response time, time used per day

query, and input/output throughput rates. While performing performance assessment tunning, it

is essential to specify the Service Level Agreement (SLA). Also, tuning response time is of no

usage, especially when they are better than those required. Realistic expectations are also

encouraged while making performance assessment. Users must have a feasible expectation, write

a query one has not tuned for, and hide system complexities.

Data load tuning forms a critical part of overnight processing. Until it is complete,

nothing can run as it is the entry point of a system. In the process, if there is data delay in transfer
DATA WAREHOUSING 3

or arrival, the entire system is affected severely. The prevalent method of tuning data load is to

insert data using SQL Layer (Sharma & Nelson, 2017). The approach ensures that normal

constraints and checks are performed. When users insert data into a table, the process checks for

enough space to add new data, if there is inadequate space, then more space may be allocated to

the table. These checks are time-consuming and cost the CPU. Bypassing all these constraints

and checks is another approach. The process places the data directly to the preformatted blocks

that are later written to the database. The method is faster and works with whole blocks of fo

data. The last approach fro this process asserts that to load the data in a table that has data drops

and recreates the indexes when the loading process is complete.

Tuning, thus, can be a complicated process due to various reasons. For instance, the

turning process is affected by the dynamic nature of the data warehouse and the difficulty

predicting the query users will use to posy data in days to come. Also, business requirements are

constantly changing the same way users, and their profiles are changing. Furthermore, users can

move from one platform to another, causing the data load to change over time.
DATA WAREHOUSING 4

References

Bellatreche, L. (2009). Optimization and Tuning in Data Warehouses.

Raza, B., Sher, A., Afzal, S., Malik, A. K., Anjum, A., Kumar, Y. J., & Faheem, M. (2019).

Autonomic workload performance tuning in large-scale data repositories. Knowledge and

Information Systems, 1-37.

Sharma, H. K., & Nelson, S. (2017). Performance enhancement using SQL statement tuning

approach. Database Systems Journal, 8(1), 12-21.