Why does TPC-D model an environment with ad hoc queries as opposed to ones which are prewritten?
Decision support queries can come either in an ad hoc or prewritten form because the business questions they intend to solve could be posed either dynamically or repeatedly. Modeling strictly ad hoc queries presupposes end-users with no special knowledge of the database or of optimizer strengths and weaknesses in a particular vendor’s DBMS. TPC-D chooses to exclusively model ad hoc queries and enforces execution rules which are based upon this premise. Some examples are the restriction on how the queries may be phrased, the ban on optimizer hints, the requirement of a constant DBMS configuration throughout the performance tests, and the requirement of dynamic SQL as opposed to static SQL.
Related Questions
- How easy or difficult is it going to be to include short ad hoc courses and other elearning resources into the local catalogue?
- How does QD respond to ad hoc analytical read-only complex queries faster than a standard RDBMS on a PC?
- Why does TPC-D model an environment with ad hoc queries as opposed to ones which are prewritten?
