Archives of the TeradataForum
Message Posted: Sat, 17 Feb 2002 @ 01:49:44 GMT
I should point out that in v2r4.1 we have moved the DBQM functionality inside the Parser/Dispatcher. The new feature is called
Teradata Query Database Manager (TDQM)
You still use the DBQM Administartor to setup the rules however the rules are stored in a Database table and enforced by the SQL Parser.
Instead of being limited to just ODBC DBQM enabled clients, ALL SQL coming into the box from any source (Channel, ODBC, CLI, JDBC, Perl, whatever) are subject to the rules if enabled.
The Old ODBC Enabled DBQM feature sends the query to the database twice. Once as an explain to get the estimates and then again if after processing the rules the query is allowed.
The new feature uses the information already available inside the Parser to allow or deny the query based upon the rules in one pass.
Therefore for ODBC clients this save the EXPLAIN step traffic for queries which are allowed.
You don't have to have a separate version of the ODBC driver installed on workstation you want to filter via the rules which makes deployment of the rules easier.
This also means that you can also filter ALL SQL coming into the box regardless of it source. Therefore you must make sure the rules are specific enough to only filter what you want to filer.
Dennis isn't allowed to run queries before 6:00 pm.
means Dennis won't be able to submit a query before 6 pm from BTEQ, WINDDI, QUERYMAN, or C program or any other method he can come up with.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|