The SQL Database Administrator (DBA) is responsible for providing technical support for the MS SQL database environment including the overseeing the deployment and organization of databases, assessment and implementation of new technologies. Alexander Forbes relies on the DBA to ensure that on-line processing database systems offer the highest reliability, recoverability and performance possible.

1 SQL Server Adminsitration

The following section details the responsibilities of the DBA with regards to the SQL servers in the Alexander Forbes Environment

1.1 Implementation

The DBA is responsible for:

• All installations of SQL servers in the environment according to the set standards
• Ensuring SQL servers have the latest security patches installed.
• Configure SQL servers for optimal availability and performance.

1.2 Standards and documentation

The DBA is required to contribute to:

• Contributing to the setting of AF SQL standards in the environment
• Updating the relevant documentation after approval by SQL Architect
• Ensuring these standards are adhered to when deploying all servers
• Adding and updating the SQL knowledge base with work around and solutions regarding SQL Servers

1.3 Performance

The DBA is responsible for:

• Ensuring the SQL servers are configured for optimal performance
• Working with Dimension Data engineers to ensure the servers are configured for optimal performance and have minimal downtime.
• Working with Dimension Data engineers to ensure the servers are maintained for optimal performance. This would include disk capacity, memory and CPU
• Monitor and ensure SQL maintenance is performed regularly to optimize performance

1.4 Security

The DBA is responsible for:

• Applying and adhering the AF SQL security standards defined by the AF Security and Compliance team and the SQL Architect
• SQL Server security must be regularly reviewed to ensure standards are maintained
• SQL DBA is granted full privileges to the environment and must treat this privilege responsibly and with discretion.

2 SQL Database Administration

The following section details the responsibilities of the DBA with regards to the SQL databases in the Alexander Forbes Environment

2.1 Implementation

The DBA is responsible for:

• Ensuring all deployments of databases are implemented according to AF SQL standards and processes.
• Have a basic understanding of database components to facilitate troubleshooting of issues.
• The DBA is responsible for all production and staging database deployments.
• The DBA is responsible for ensuring the environment has sufficient capacity when deploying a database

2.2 Performance

The DBA is responsible for:

• The database is configured and maintained for optimal performance
• Ensuring all database indexes are optimized and maintained
• Troubleshoot database performance issues

2.3 Security

The DBA is responsible to ensure:

• All security access is applied according to AF Standards and processes
• All exceptions to the security requirements are discussed and agreed with the SQL Architect.
• SQL logins passwords are maintained and changed annually.
• The Windows accounts passwords are stored in the SQL password repository
• All failed logins are attended to in the call logging process

2.4 Maintenance

The DBA is responsible for:

• Ensuring the database maintenance is performed weekly and attend to any issues.
• The maintenance of the database space requirements
• Ensure all scheduled jobs run successfully and troubleshoot any failures.

2.5 Support

The DBA is required to have:

• Have a good understanding of database structure components to facilitate troubleshooting of issues
• Have a basic understanding of how to optimize a database through indexing, table and file structure

3 SQL REPORTs ADMINSTRATION

The following section details the responsibilities of the DBA with regards to the SQL Reporting Services in the Alexander Forbes Environment

3.1 Implementation

The DBA is responsible for:

• Implementation of SQL Reports to the environment standards
• Maintaining the folder structure within the report server to ensure the data is secure.
• Setup report schedules and ensure there are limited reports running at the same time.
• Apply shared schedules to multiple report schedules that occur at the same time.

3.2 SUpport

The DBA is required to:

• Apply deployment of SQL reports according to standards
• Troubleshoot reports errors in the production and staging environments
• Have a basic working knowledge of the components of a SQL Report
• Have basic knowledge of creating and designing reports to assist with troubleshooting or issues

4 SQL integration Services

The following section details the responsibilities of the DBA with regards to the SQL Integration Services (SSIS) in the Alexander Forbes Environment

4.1 Implementation

The DBA is responsible for:

• Implementation of SQL SSIS packages to the environment standards
• Maintaining the folder structure within the SSIS server to ensure the data is secure.
• Setup scheduled jobs to run the packages and ensure there is minimal conflict on the shared server

4.2 SUpport

The DBA is required to:

• Deployment of SQL SSIS packages according to standards
• Troubleshoot SSIS errors in the production and staging environments
• Have a basic working knowledge of the components of a SQL SSIS package
• Have basic knowledge of creating and designing SSIS packages to assist with troubleshooting or issues

5 SQL Analysis Services

The following section details the responsibilities of the DBA with regards to the SQL Analysis Services (SSAS) in the Alexander Forbes Environment

5.1 Implementation

The DBA is responsible for:

• Implementation of SQL SSAS databases to the environment standards
• Maintaining the security within the SSAS server to ensure the data is secure.
• Setup scheduled jobs to run the backups of the databases to ensure recoverability

5.2 SUpport

The DBA is required to:

• Deployment of SQL SSAS databases according to standards
• Troubleshoot SSAS errors in the production and staging environments
• Have a basic working knowledge of the components of a SQL SSAS databases.

6 SQL REplication

It is the responsibility of the DBA to:

• Ensure the Replication solution runs successfully and troubleshoot any issues

7 Backup and Recovery

The following section details the responsibilities of the DBA with regards to the SQL backup and recovery in the Alexander Forbes Environment

7.1 Full database backups

It is the responsibility of the DBA to:

• Ensure all databases in the environment have a daily full backup run successfully
• If the database utilizes a differential backup strategy the full backup should occur at least once a week.
• The DBA must troubleshoot any issues that may occur with backups.
• The database backups require ad-hoc restore tests to ensure the backups are valid

7.2 Differential database backups

It is the responsibility of the DBA to:

• Ensure all databases in the environment have successful daily differential backups if required
• The DBA must troubleshoot any issues that may occur with backups.
• The database backups require ad-hoc restore tests to ensure the backups are valid

7.3 T-Log backups

It is the responsibility of the DBA to:

• Ensure all databases in the environment have successful t-log backups if required
• The DBA must troubleshoot any issues that may occur with backups.
• The database backups require ad-hoc restore tests to ensure the backups are valid

7.4 Disaster Recovery Plans

It is the responsibility of the DBA to:

• Ensure the DR solution runs successfully and troubleshoot any issues

8 Call Management

To best administer the SQL environment all activities, requests and issues must be logged and attended to through the service desk. The following section details the responsibility of the SQL DBA.

8.1 Change Calls

The DBA is responsible for:

• Conducting impact analysis of the RFC in support of the responsible RFC approver. Even if this is done at implementation
• Implementing the RFC at the scheduled date and time.
• Liaising with the Change Control Team and requestor if any issues or failures occur
• Closing off the Change call on completion

8.2 Task Calls

The DBA is responsible for:

• Attending to the task call within 4 hours of the call being logged
• Completing the call within 2 working days. If not possible, call updates to be completed every week until solution is found
• Liaise with the requestor on the status of the call
• Close the call on completion

8.3 Incident Calls

The DBA is responsible for:

• Attending to the task call within 2 hours of the call being logged
• Completing the call within 8 hours. If not possible, call updates to be completed every day until solution is found
• Liaise with the requestor on the status of the call
• Close the call on completion

8.4 Ad-Hoc Requests

All ad-hoc requests must be logged to the helpdesk. The SQL DBA must ensure the requestor logs the call as it will reflect on the correct requestor details and ensure a call is logged then next time.

9 Operational Responsibility

The following section details the responsibility of the DBA within the Group IT operational environment.

9.1 Office hours

The DBA is assigned working hours to ensure the SQL environment is administered 7 am to 6 pm. The DBA is responsible for:

• Ensuring the work hours are adhered to
• If alternative hours are required, this must be arranged with the team lead 48 hours prior.
• In the event of an emergency or illness an sms or phone call must be made first thing in the morning to notify the team lead.

9.2 SOHO DAYS

The DBA is permitted to work from home one day a week. The DBA is to adhere to the following rules:

• Always a minimum of two engineers in the office. If not possible SOHO is forfeited. If there is staff shortage due to leave, sickness or training SOHO is forfeited if there is not 2 engineers in the office.
• Must be logged into Cisco IP communicator or IP phone – no call forward to cell phone unless away from your desk
• There is no SOHO on the Monday after Downtime weekend. Rearrange SOHO on a different day or forgo the SOHO
• If you are SOHO and you are due to attend CAB, rearrange the attendance or the SOHO day.
• If leaving your SOHO desk notify team and update OCS status – “Will be back at 14:00”
• If SOHO falls on a public holiday the SOHO is forfeited.

9.3 Meetings

The DBAs are to attend the following meetings when required:

• Weekly CAB meeting

If the DBA is unable to attend, please arrange another DBA to attend or provide your apologies 24 hours before the meeting.

At times the operational tasks will require attendance and the full meeting attendance will need to be cancelled. Request the facilitator to call you in for the database part if possible.

9.4 Overtime

At times it is required the DBA work outside the normal office hours. In the event of such a request the DBA is required to:

• Obtain an order number and cost centre for any work requested by business.
• If the work is Group IT related, approval form Andrew Geere is required.
• Submit all overtime using the IT Overtime portal

9.5 Standby

Due to the criticality of the SQL server environment, an SQL DBA is required to be on standby for one week. This is rotated between the team. It is the DBA responsibility to:

• Ensure cell phone contact is available after hours
• If the DBA is unable to be on standby due to leave or illness, alternative arrangements must be made with the team
• Standby allowance is claimed through the IT Overtime portal

To apply, send your CV to