Dba - SQL Server

Job title Production Database Administrator -DBA - SQL SERVER Reports to IT Operation Manager DOMAIN : HEALTHCARE CLIENT : COLUMBIA ASIA CONTRACT : SANCY - 2 Years (can be extended) NATIONALITY - OPEN (Locals favoured) JOINING : Immediate Job purpose A database administrator (DBA) is responsible for the performance, integrity and security of a database. They will also be involved in the planning and development of the database (Upgrades), as well as troubleshooting any issues on behalf of the users. A DBA makes sure that databases have the following qualities: - data remains consistent across the database; - data is clearly defined; - users access data concurrently 24/7 - there is provision for data security and recovery control (all data is retrievable in an emergency). Roles and responsibilities Installation, configuration, upgrade, and migration The DBA is responsible to installs the database software and selects from various options in the product to configure it for the purpose it is being deployed. As new releases and patches are developed, it's the DBA's job to decide which are appropriate and to install them. If the server is a replacement for an existing one, it's the DBA's job to get the data from the old server to the new one. Perform database software maintenance: - Assist in installation and specify initial installation options - Develop and test database migration procedures with help of Development Team - Perform database migrations - Evaluate and test new features/functionality as recommended by Development Team - Upgrade/migrate databases to current release levels as recommended by Development Team - Document migration procedures and test results - Perform database maintenance functions - Move, rebuild, or change database objects as required in production Production DBA Roles & Responsibility Backup and recovery DBAs are responsible for developing, implementing, and periodically testing a backup and recovery plan for the databases they manage. DBA has final responsibility for making sure that the backups are being done as scheduled and that they include all the files needed to make database recovery possible after a failure. When failures do occur, the DBA needs to know how to use the backups to return the database to operational status as quickly as possible, without losing any transactions that were committed. DBAs are responsible in making sure data are always in sync between production database and disaster recovery center. Any issue/differences identified between Production database and DR backup should be immediately communicated to the management team. Database security The DBA must understand the all security model that the database product uses and how to use it effectively to control access to the data. The three basic security tasks are authentication (setting up user accounts to control logins to the database), authorization (setting permissions on various parts of the database), and auditing (tracking who did what with the database). Storage and capacity planning The primary purpose of a database is to store and retrieve data, so planning how much disk storage will be required and monitoring available disk space are key DBA responsibilities. Watching growth trends are important so that the DBA can advise management on long-term capacity plans. Performance monitoring and tuning The DBA is responsible for monitoring the database server on a regular basis to identify bottlenecks (parts of the system that are slowing down processing) and remedy them. Tuning a database server is done on multiple levels. The capacity of the server hardware and the way the operating system is configured can become limiting factors. The way the database is physically laid out on the disk drives and the types of indexing chosen also have an effect. The way queries against the database are coded can dramatically change how fast results are returned, the DBA is responsible to identify any such bad queries and provide the details to development team for remedy. This also requires regular monitoring and tune memory usage for databases and manage physical database resources Troubleshooting When things do go wrong with the database server, the DBA needs to know how to quickly ascertain the problem and to correct it without losing data or making the situation worse. High availability Being on a Hospital Industry which operates 24/7 and Care21 / CALIMS being the hospital’s operating system, the system is available 24x7, so must the underlying database. Managing a database in this environment requires an understanding of which types of maintenance operations can be done online (with the database available to users) and which must be scheduled for a maintenance "window" when the database may be shut down. It also requires planning for redundant hardware and/or software components, so that when one fails, others will keep the total system available