Monitor Consumption Usage Sample Clauses

Monitor Consumption Usage i. Teradata collects and stores usage data to monitor, evaluate, and report system status and performance. Teradata uses this data to determine how you use our software, access functions, and perform analytics. Teradata does not collect any sensitive or personally identifiable data, nor any data values you enter into your Vantage system. ii. You can enable log features during onboarding to monitor Teradata processing activities. iii. To monitor system consumption, Teradata requires continuous access to your system compute resources. If you do not grant this level of access or if you turn it off, you will owe the full amount of the deployed system at the maximum Vantage Unit capacity available to you for the entire month. If you do not reinstate access before the start of the next month, Teradata reserves the right to terminate the service. iv. Database Query Log (DBQL) and Performance Data Collection Reporting (PDCR) Log. 1. The customer must not move data from dbc.Dbqlogtbl, dbc.ResUsageSpma, or dbc.dbqlutilitytbl. 2. Configured Viewpoint jobs move data from dbc.Dbqlogtbl, dbc.ResUsageSpma, and dbc.dbqlutilitytbl to the PDCR log. 3. Teradata maintains a minimum of three months of data in the PDCR log. 4. If there is a shortage of space in the PDCR log, Teradata will increase the space to accommodate the new logs. 5. Teradata sets SQL, Utilityinfo, and FUL DBQL logging for all the users. The customer must not change it. 6. Teradata disables Summary and Threshold logging. v. VCMUSER requires access to several views, tables, macros, and stored procedures to perform Vantage Unit collection activities.