Performance Database Changes Overview

bawltherapistSoftware and s/w Development

Dec 13, 2013 (3 years and 8 months ago)

103 views

Performance Database Changes
Overview
Jim Hale
Engineering
Open Database Advantages
 Better resiliency
 Better performance
 More flexibility in configuring storage
 Better scalability
 Access from TeamQuest Surveyor
 Access from 3
rd
party tools
MARCH 2013 RELEASE
Recent New Release
March 2013 Release
Performance Database Option
Advantages
 multi-version concurrency
control (improves
performance)
 point-in-time recovery
 table spaces
 hot backups
 query optimizer
 write ahead logging

March 2013 Release
More options:
 TeamQuest-provided PostgreSQL as install option
 PostgreSQL or Oracle for enterprise databases
 PostgreSQL or Oracle for virtualization agent
databases
• VMware
• Hyper-V
• libvirt
March 2013 Release
 Oracle instant client is included with Manager
 View and Alert do not work with open databases

SEPTEMBER 2013 RELEASE
Upcoming Release
September 2013 Release
 PostgreSQL or Oracle option for all agents
 Harvest and agents can store directly into the
same database
 Admin Console required for new open databases
September 2013 Release
 All control data now stored in the database
• Workload definitions
• Alarm definitions
• Harvest configuration
• Agent control information
• Summarization and retention specifications
 Open database interfaces provided
• Sqlite3
• SQL*Plus
• psql
Database List
 Open databases no longer identified by directories
• SQLite used to maintain a list of databases
 SQLite is a software library that implements a self-contained, serverless, zero-configuration,
transactional SQL database engine.
• SQLite records includes local database name and database
connection information
• SQLite data is stored in the TeamQuest data directory under
cf/manager
• Data directory database subdirectories are used only for logging
purposes

Simplified Database
Creation
 Can specify open database connection information via
tqdbu command line

tqdbu

-
i
-
d
production
-
a
postgresql

-
t pdb




enter your PG
administrator

login



enter your PG
administrator

password



enter the
db

owner




enter the
db

owner

password



enter the PG server system



enter the PG server port



enter the PG database name

FUTURE RELEASES
Longer term…
Future Releases
 Phase out TeamQuest proprietary database
 Provide tools to ease migration of existing
proprietary databases to an open database
 Integrate PostgreSQL database administration with
TeamQuest administration

Future Releases
 Leverage open database tools to provide
additional value in TeamQuest products
 Provide a package of database tools
 Provide a PostgreSQL agent to monitor the
PostgreSQL database server

Database Migration Paths
Gradual migration
 New data stored in the
open database
 Existing data remains in a
proprietary database
Complete migration
 New data stored in the open
database
 Proprietary database data
copied to open database
 Proprietary database removed
MORE ABOUT POSTGRESQL
Open Performance Database
Using a PostgreSQL
Database
 Install PostgreSQL
 Install Manager
 Create an open database using tqdbu
 Register the database with Admin Console
 Register the PostgreSQL database in IT Service
Analyzer
 Configure the PostgreSQL data source in Surveyor
PostgreSQL Architecture
PostgreSQL
Database
PostgreSQL
Server
TeamQuest
Agents
Data
Summarization
Data Harvest
Reporting Tools
Internal Tables
 Tables for structural metadata
• tq$aggservice – data used to control the aggregation service
• tq$aggtimes – information about the last aggregation of each table
• tq$clobs – control data that was in the file system before Sept 2013
• tq$dle – data location information used by ITSAR
• tq$field_cons_methods – how field values are consolidated
• tq$field_data_subtypes – list of valid field subtypes
• tq$field_data_types – list of valid data types

Internal Tables
 Tables for structural metadata
• tq$field_relationship_types – list of valid field relationships
• tq$field_types – list of valid field types
• tq$itr – IT Resource definitions
• tq$licenses – licensing information
• tq$nodes – list of database nodes linked to this database
• tq$properties – various simple properties such as database version
• tq$related_fields – relationships between fields in the same table
Internal Tables
 Tables for structural metadata
• tq$table_defs – used when data tables are initially created
• tq$table_fields – list of fields in each performance table
• tq$table_retentions – data retention information
• tq$table_time_types – list of valid field time types
• tq$table_types – list of valid table types
• tq$tables – list of performance tables in the database
• tq$time_unit_types – list of valid field time unit types
• tq$tokens – information used by Admin Console
PostgreSQL Summary
 Fast
 Reliable
 Flexible
 Open
Performance Database Option
QUESTIONS?
Thank you!