StatementType changes

Database
Scout

StatementType changes

Our site recently upgraded to TD 15.10. One change that we have found that has impacted on our TDWM throttle settings is that several statements are now classified as DDL. We have a throttle in place that limits DDL for a particular user to one concurrent query (deadlock avoidance).  We were everely impacted when the SET DATABASE statements statement started getting throttle because it is now classed as DDL. 

  My question is - What is the reason for reclassifying statement types? 

1 REPLY
Highlighted
Junior Contributor

Re: StatementType changes

The DATABASE command has always been DDL (in SQL, but maybe not for TASM).

 

But how can this short command cause severe impact?