Once you have profiled the set of queries that will access the database, the behaviour patterns of end users, and the hardware resources, apply what you estimate to be the proper parameter configuration. In this initial phase, monitor the data warehouse during peak hours to determine if the data warehouse is being under utilized or is performing poorly in an attempt to process more queries that it can manage. If DB2 Query Patroller is configured too conservatively, the queries may not be submitted to the data warehouse even though resources are available. On the other hand, if DB2 Query Patroller configuration is too liberal, too many queries may be running against the data warehouse, causing the system to waste valuable resources paging or switching contexts.