Workload Management and Service Classes

service classes define limits on groups in the {{ocient}} system you can design service classes using these limits use these parameters to control the limits 257,233,155,171,171,100,100,100,100,100 true unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type service class setting applicability when a user is present in multiple groups with different service class limits, the system applies the least restrictive limit for each parameter for example, if user a is in groups g1 and g2, which have service class time limits of 10 seconds and 20 seconds, when user a runs a query, the query has a time limit of 20 seconds this behavior is slightly different for concurrency if the service class concurrency limits for the groups the user belongs to are 1 and 2, a query can use a concurrency slot from either service class a user with multiple service classes can experience a query executing with a slot from one service class but using a time limit or other limits from a different service class additionally, the system does not apply service class concurrency limits when a query affects only system tables choose parameter values if you set a service class at the session or query level, the system uses the value set by that service class, with the query level service class taking precedence otherwise, if you set a value for this parameter at the session or query level, the system uses the most restrictive of the two if the ocient system chooses the value from multiple service classes, the system takes the least restrictive value from all service classes then, the system takes the most restrictive of that value and the query or session level value, if it exists this selection does not hold true for parameters related to result set caching cache max time and cache max bytes for details about the behavior, see https //app archbee com/docs/hoqbljqchkoc8dvhbf0dz/gnw qhg041w51u3vscwa4 if you choose a service class using statement text matching, the system compares its value to the query or session level value, and the system does not review any other service classes next steps a tutorial for designing a set of service classes for workload management is available in the docid\ sf8ojgyg8bqcetvtpj87c see docid\ jygpvmqcl3xgpbvftt4qp for service class related ddl statement references, such as creating, altering, and applying a service class related links docid\ jf l ie2lupbjgrjw4lqx