Share via:

Hello Readers,

This page will give you a composite summary of how Teradata DBAs use their time.

Let’s first have a look at the high-level summary that lists the main activity categories of the DBAs. As we scroll down further, we shall learn about these in depth:

High-level summary :

  • Performance monitoring and tuning
  • Space management
  • Statistics management
  • Workload management
  • System Health and support (viewpoint)
  • Evaluating new features
  • Upgrades
  • Training, consulting
  • Security
  • Application Team Support
  • Incident Initiation
  • Backup and restore management
  • Data refresh between different environments
  • System Administration functions
  • Password management
  • Roles and accessrights management

Performance monitoring and tuning

  • Look into long running queries
  • Evaluation of ResUsage and DBQL output
  • Detecting and responding to performance issues
  • Tune queries for optimal consumption of resources and time.
  • Analyse monthly reports of high-consuming queries
  • Daily review of performance score card (top 25 worst queries)
  • Run some handy queries to see any query performing badly and take appropriate action on it ( rewriting or collecting/dropping stats, creating indexes )
  • Code reviews, performance assurance

Space management

  • Maintain space accuracy in the system by:
  • Updatespace
  • Packdisk
  • dropping unnecessary objects
  • moving space across databases as needed


  • Collect/refresh necessary stats for optimal query performance
  • Take care of missing/stale stats
  • Refresh stats/collect necessary after the upgrade


  • Verify system health frequently and take immediate action when the system health is degraded
  • setup the alerts in viewpoint if anything exceeds threshold values like disk usage, spool usage, high IO, CPU usage, etc.
  • Look at SQL, indexes, statistic collection detail


  • Take daily backup for important objects
  • Take and maintain weekly/monthly backups
  • Do scripting to improve backup routines and implement UDFs from Developer Exchange to replace complex SQL functionality


  • Work with CSRs to apply patches, perform upgrades, projects such as TTU software distributions, manage change control
  • For major upgrades, plan for outages


  • Discuss all new things/learnings with colleagues
  • Make sure that all the tasks are done before leaving/give handover to the next person available
  • Gain knowledge on all new features adding to all the latest versions
  • Check with senior expertise/ SME as needed
  • Plan for and manage big new feature exploration, adoption, put together guidelines
  • Monthly/Quarterly formal training sessions for end users

Incident initiation

  • Open and track incidents with Teradata GSC
  • Manage Incident resolution
  • Regular meetings with Teradata Managed Care and CS associates


  • Help define overall security needs and guide its implementation that will be more important in the future
  • Security for all Teradata, including cross-team meetings, interfacing with vendors
  • Security, validating adherence to standards
  • Security only at a high level (a special team own security implementation)

Roles and accessrights

  • Create and grant roles for better security
  • Granting and revoking access rights appropriately when needed.


  • Maintain passwords in TDWallet for more security
  • Keep an eye on the accounts/password(s) expiry dates, change them when needed and communicate the same to respective application teams.

Other general tasks :

  • Support and work with Application DBAs
  • Writing scripts to automate complicated database tasks for the Application DBAs
  • Prepare appropriate cron jobs to schedule batch jobs
  • Work with application groups to resolve issues with queries or utilities
  • On-call to answer questions or resolve issues as they arise
  • Coordinating arriving data that needs to be loaded
  • Managing movement of data to Hadoop
  • Assist in development of new applications
  • Monitor blocking on the system and try to release locks if any left-over exists like HUT locks and locks at object level
  • Maintenance of indexes for objects ( PI for uniqueness )
  • Schedule the daily/weekly jobs to move the data from dbc to history tables.
  • Enable access logging and query logging for query performance comparison and objects logging details
  • Use appropriate utilities to load data in objects in better way.
  • .Create Teradata objects like Databases, Users, Profiles, Roles, Tables, etc. Modifying Databases, Users, Roles Profiles according to project requirement

Thanks for reading my article , I hope above content is useful and informative.

Follow us on : 

Website : https://www.ktexperts.com/
Facebook Page: https://www.facebook.com/ktexperts/
Facebook Group : https://www.facebook.com/groups/ktexperts/
Linkedin : https://www.linkedin.com/company/ktexperts/
Twitter : https://twitter.com/ktexpertsadmin
Youtube : https://www.youtube.com/channel/UCJ-gDTLfNXSY3QoV_fnKtOg

Share via:
Note: Please test scripts in Non Prod before trying in Production.
1 Star2 Stars3 Stars4 Stars5 Stars (2 votes, average: 5.00 out of 5)

Add Comment