Database analysts design, develop and administer data management solutions using database management software. Data administrators develop and implement data administration policy, standards and models. They are employed in information technology consulting firms and in information technology units throughout the private and public sectors.

Database analysts design, develop and administer data management solutions using database management software. Data administrators develop and implement data administration policy, standards and models. They are employed in information technology consulting firms and in information technology units throughout the private and public sectors.

Click on any of the Essential Skills to view sample workplace tasks for this occupation.

Skill levels are assigned to tasks: Level 1 tasks are the least complex and level 4 or 5 tasks (depending upon the specific skill) are the most complex. Skill levels are associated with workplace tasks and not the workers performing these tasks.

Scroll down the page to get information on career planning, education and training, and employment and volunteer opportunities.

The skill levels represented in the above chart illustrate the full range of sample tasks performed by experienced workers and not individuals preparing for or entering this occupation for the first time.

Note that some occupational profiles do not include all Numeracy and Thinking Essential Skills.

If you would like to print a copy of the chart and sample tasks, click on the "Print Occupational Profile" button at the top of the page.

This information has been adapted from the Government of Canada's Essential Skills Profile for
2172-
Database Analysts and Data Administrators

Read lengthy email and memos on technical matters from co-workers, customers and colleagues. For example, read developers' notes which document changes made to databases. Read several pages of email correspondence between co-workers and customers to learn about database malfunctions, analyses and solutions. Read colleagues' explanations of obscure error messages from database software. (3)

Read handbooks and guides for new software and programming languages to increase knowledge in the field of database management systems. For example, read books on new releases of database software to become familiar with the architecture, attributes and capabilities. (4)

Read software and hardware help files. For example, read numerous help files on software support websites to check command syntax and learn unfamiliar procedures such as changing database names. Typically, these texts integrate sections of programming code and sometimes screen shots to enhance their explanations. (4)

Read online newsletters and trade publications such as Slashdot, Oracle Magazine and FileMaker Magazine to learn about new database management products, tools, designs and configurations. For example, database analysts may read in-depth reviews written by developers and consultants on new software releases and libraries. Database architects may read articles on current trends in database modelling and administration such as clustering technologies to permit the pooling of several smaller servers and storage devices. Data administrators may read lengthy security alerts. (4)

Read 'requests for proposals', design specifications and other documents relevant to the design and development of database management systems. For example, database analysts read 'requests for proposals' to learn about the tasks, requirements, evaluation criteria and selection processes and to determine the resources needed to undertake projects. They may also read project charters and requirement reports to learn background information about customers' systems. They may also read 'requests for proposals' to ensure the scope and project deliverables are adequately defined and developed to achieve the desired objectives. (Database Analysts) (4)

Write reminders, short email and notes to co-workers, managers and customers. For example, database administrators may write email to advise co-workers of downtimes planned on large databases. They may write notes to database users within their organizations during the investigation of duplicate records. (2)

Write short descriptions of functions and features of database software for slide presentations, promotional brochures and websites. Adapt these descriptions to the interests and capacities of the audience providing concise overviews for generalists and technical details for specialists. (3)

Write memos and longer email to document work and collaborate on problem solving and design with co-workers, customers and colleagues. For example, database administrators may write memos to describe changes to databases, give reasons for the changes, outline expected effects and specify backup plans. They write email to co-workers to collaborate on the development of methods to improve database performance. Database analysts may write email to customers to clarify database specifications. (3)

Write proposals, specifications and reports for co-workers and customers. For example, database analysts may write project proposals in which they present analyses of customers' current systems and recommend database models. Database designers may draft design specifications for projects to circulate among co-workers for comment. Data administrators may write reports for managers to describe disaster recovery plans for databases, including the types of jobs to be run and locations of backup file libraries. (4)

Write user guides and standards for customers For example, database architects write user guides to detail system configurations, database architectures and procedures for customers unfamiliar with specialized terminology. They write standards to specify system elements such as programming languages, software program versions and correct data types, formats and values. (Database Analysts) (4)

Locate data on labels. For example, scan labels on computer equipment to identify ports and power connectors. (1)

Enter data into lists. For example, during audits, enter record numbers into lists of duplicate records. (2)

Locate data in schematic drawings of system configurations and data management processes. For example, review schematics of server and database configurations when evaluating system efficiencies and data loads. Database analysts may study schematic representations of data models illustrating data flows and relationships among various entities. They may also locate development tasks, teams and project milestones in Gantt charts. (3)

Locate data in graphs and identify trends in plots of quantitative data. For example, database administrators may monitor data on memory usage, numbers of concurrent sessions, event waits and calls per second on line graphs and bar charts. (3)

Complete forms such as database query forms, timesheets and change management process forms. For example, enter criteria such as dates and key words into database query forms to specify data to be extracted. Enter project names and numbers, customer names and job tasks and times into timesheets. (3)

Locate data in lists and tables. For example, scan long lists of software codes to identify errors. Data analysts scan database transaction logs for unusual activity when auditing data security. Database administrators may scan lists of database performance variables such as run times and disk growth rates to locate data on the performance of data management systems. They may also locate data on variables such as processing power and disk space usage in detailed tables of application production data. (4)

Use graphics software. For example, use programs such as Visio to create diagrams and flowcharts representing database models, data flows and management processes. Use software such as Photoshop, Illustrator and Fireworks to create graphic elements in database packages for customers. Use programs such as Power Point to create slide presentations for co-workers and customers. (Database Analysts) (2)

Use spreadsheets. For example, create lists, tables and graphs in spreadsheets such as Excel to migrate data, manage file and disk sizes and project schedules, and track database performance variables. (3)

Use Internet browsers and access vendors' websites and on-line trade publications to search for information on database errors, malfunctions and various tools. Participate in exchanges on user group forums and bulletin boards. Download shareware and program code to repair database errors and improve performance. Access Intranet websites to complete timesheets and answer computer assistance requests. (3)

Use word processing programs such as Word to create, edit and format documents such as program notes, memos, reports, user guides, standards and procedures. In some cases, integrate schematics, tables, screen shots and pictures to supplement the text. (3)

Use communications software. For example, use email software such as Outlook to exchange email and computer files with co-workers, colleagues, customers and software vendors. Create address books, manage personal agendas and maintain distribution lists to improve project management. Use instant messaging applications such as Messenger to correspond rapidly with co-workers while working at the computer. (3)

Do programming and systems design. For example, use programming languages to code batch jobs for mainframe computers to process very large volumes of data. (4)

Use computer and software applications. For example, use operating systems such as Unix and Linux to run applications. Use bug tracking software such as Bugzilla to help identify errors in databases and scripts. Use project and issue management software such as JIRA to centralize and record communication with co-workers and customers about specific tasks. (4)

Use databases. For example, database analysts design, develop, program, install and test data models and database management systems. They also design and program query forms and create interfaces for various applications using database development tools such as Oracle, IDMS, SQL Server and TOAD. Data administrators install, maintain and upgrade databases in Oracle, Access, FileMaker and other database management systems. They plan and manage data security, set usage standards, write script, run batch jobs, back up data, fine tune performance, troubleshoot errors and install upgrades. They also manage the configuration of servers and physical storage devices, expand files and move data, as necessary. (5)

Discuss technical matters concerning the development and management of database systems with co-workers, customers and colleagues. For example, data managers may discuss the adequacy of database scripts and the resolution of challenging system errors with co-workers. Database analysts may discuss acceptable levels of data loss with customers. Database analysts may speak with colleagues about the compatibility of new versions of database software. (2)

Negotiate project timelines and prices and discuss database requirements and constraints with customers and subcontractors. For example, probe to learn about information flows in customers' systems. Translate customers' objectives into specifications for database models and double check understanding. Negotiate hourly rates and deliverables with subcontractors who provide services such as translation, website development and programming for database development projects. (Database Analysts) (3)

Train, instruct and advise junior team members and database users. For example, advise junior members of the team to use good change management practices such as clear audit trails for all changes implemented to database systems. Train users of database systems in procedures to structure queries and format reports. (3)

Make presentations on software releases and database designs to groups of co-workers, managers and customers. For example, database architects present proposals for database models to customers, explaining the relationships and flows of data through the customers' systems. They match the complexity of information they present to the needs of their audiences. (3)

Prepare, monitor and adjust work schedules for database development projects. For example, data administrators may create schedules for teams of co-workers carrying out projects such as the migration of database objects to new locations. As projects advance, they adjust schedules for unplanned occurrences such as time overruns due to programming difficulties. (3)

Prepare and monitor project budgets. For example, database managers budget the cost to develop data management systems. They take into consideration complicating factors such as the requirement for software to run on multiple platforms and employ web interfaces. They establish costs and revenue requirements. They monitor costs throughout projects to prevent budget overruns. (Database Analysts) (3)

Prepare schedules for computer operations such as processing data and executing system backups. For example, schedule batch jobs to process large volumes of data such as daily medical premium applications. Schedule onerous tasks to run at night to free computer systems for daytime use. Take into account data dependencies, running sequences among the systems and times required for tracking and repairing failures. (Database Administrators) (4)

Calculate space requirements for new databases. Consider all the components of the database systems such as the system software, configuration and control files, temporary storage spaces for downloading, indexing and loading reports, cache storage, indexed data, database log files and spaces for the archive manager. Choose the appropriate formula for each system component as determined by criteria such as the type of operating system and find and substitute values in the formulae for variables including the numbers of items, index fields and versions of reports and the lengths of time necessary for storing reports. Apply multipliers such as compression ratios which vary according to the types of data being stored. In some cases, repeat the calculations through several iterations to determine final storage space requirements. (Database Administrators) (4)

Collect data and generate statistics to describe database performance. For example, database administrators collect data on the use of disk space over time to identify trends and adjust capacity. Track automated process measurements such as computer running times, transaction rates and bandwidth utilization per application on servers to identify problems and tune performance. (3)

Estimate disk and memory space requirements. For example, database analysts estimate memory space necessary for new database features and components. Data administrators estimate when to expand server capacity by analyzing data on current disk space usage and growth trends in databases. (2)

Estimate times needed to complete various job tasks. For example, a database analyst may use past experience to estimate times needed to design, program and test each module of a customer relationship management system. (2)

Database analysts and data administrators plan job tasks independently. They are frequently interrupted by co-workers and database users so they have to review priorities and revise the order of job tasks regularly. Database analysts and data administrators may aid in strategic planning for their organizations by recommending new database software applications and database configurations to enlarge the scope and range of products and services offered. Data administrators contribute to operational planning by developing database policies. (3)

Choose methods to rectify software errors and malfunctions. For example, when databases malfunction temporary fixes and patches may be used until more permanent solutions can be instituted. Consider the urgency of the repairs, the stability of the patches and known effects on database performance before proceeding. (2)

Select methods, times and sequences for administrative processes and database development projects. For example, data administrators decide how and when to expand database capacity. They consider factors such as data growth rates and disk usage statistics. They also select data to migrate, destinations for migrated data and new storage devices. (3)

Choose database designs and options. Take into account numerous factors including the projected quantities of data to process, numbers of users, types of queries required, data security needs and budgetary constraints. Consider the quality and versatility of options versus costs. Submit your choices to managers and customers for approval as appropriate. (3)

Deal with unexpected computer system failures and equipment breakdowns. For example, database analysts may not be able to access customers' files because secure Internet connections cannot be established. They try to identify defects and bugs through analyses of process variables and transaction logs. They consult co-workers, software support help files and user group forums for information. (Database Analysts) (3)

Find information on database software, libraries and other tools. Search the Internet for product reviews and locate relevant correspondence on user group websites. Discuss options with co-workers and colleagues. (3)

Find information about customers' data management systems and installations. Review forms and reports used in the customers' systems to understand data flows. In some cases, visit customers' installations to observe production and discuss objectives, current practices and standards. (Database Analysts) (3)

Find information about unusual database system errors and malfunctions. Produce, review and analyze internal tracking documents such as lists of software codes, result tables and graphs of performance data. Search for relevant information in on-line help files, trade publications and postings on user group websites. Consult co-workers, colleagues and software support personnel for assistance. Study results from tests and trials. (4)

Evaluate the quality of work done by co-workers. For example, database administrators may assess the logic of script written by quality assurance specialists before authorizing access to operational databases for tests. Database analysts may evaluate project documentation written by co-workers to ensure its adequacy, accuracy and clarity before delivery to third parties. (Database Analysts and Data Administrators) (2)

Evaluate the suitability of database configurations, software upgrades, libraries and programming languages for specific uses. Run tests and read product reviews, user comments and handbooks to assess the suitability of software and database designs for specific applications. Use evaluation criteria such as compatibility with users' operating systems, reliability of vendors, provision of technical support, cost, availability of optional features and assurance of data security. (Database Analysts and Data Administrators) (3)