Database Management. The Sector, acting through its Manager, will maintain the database(s) of vessel trip reports (VTR), dealer, At Sea (ASM), NEFOP Observer, and Dockside (DSM) monitoring reports. In addition, the Sector will maintain any other database it determines necessary for its operations.
Database Management maintain accurate and complete employee information and history on human resource information system, based on information provided by Subscriber.
Database Management. “Database Management” shall be a Resource Unit Category. One
(1) Resource Unit for this Resource Unit Category shall be equal to one (1) billable server instance as defined in Section 22.1.2
(a) (i) where Service Provider provides database management service on a server categorized as a Database in the CMDB. There are three (3) distinct Resource Unit Categories of Database Management:
(i) Full (Level 1) – Support services as defined in Exhibit 2.3.
(ii) Partial (Level 2) – Support Services as defined in the Service Management Manual.
(iii) Minimal (Level 3) – Support Services as defined in the Service Management Manual.
Database Management. Prepare and maintain database, which will include the information collected in Subtasks a. through c. above.
Database Management. Supplier’s responsibilities for database management include:
(a) Building and installing databases and providing DBMS support for databases as directed by Gap, which shall include managing database availability and performing remote database administration.
(b) Maintaining, operating, and upgrading all Supplier-provided automated monitoring tools to monitor database performance.
(c) Performing database shutdowns and restarts in accordance with Section 11 (Incident and Problem Management) and Section 10 (Change Management) of this SOW.
(d) Performing reorganizations and preventative maintenance to optimize performance as required, including monitoring archive log growth and database reorganizations.
(e) Maintaining the databases to meet performance standards, maximize efficiency and minimize outages.
(f) Maintaining, updating, and implementing database archive processes and procedures as defined by Gap to recover from an outage or corruption to meet Gap’s business requirements.
(g) Providing physical database management support including providing backups and restores to recover data and meet Gap’s business requirements.
6.1 Gap/IBM Confidential and Proprietary Information Second Amended and Restated Master Services Agreement (h) Installing, maintaining and supporting database Software products (e.g., installation of patches and service packs for major and minor releases) and testing and implementing database environment Changes as Approved by Gap in accordance with Section 10 (Change Management) of this SOW.
(i) Proactively providing capacity planning to prevent and Resolve Incidents caused by lack of capacity (e.g., dataset or table space capacity events, full log datasets etc.).
(j) Performing Incident and Problem detection and fault isolation for downtime and database utilization events.
Database Management. 3.1. All customers are tracked throughout the lifecycle of their participation in the Program on the CTCdb
3.2. Tracking parameters include but are not limited to the following:
3.2.1. Inquiries
3.2.2. Enrollment
3.2.3. Appointments
3.2.4. Installation routing
3.2.5. Work order tracking
3.2.6. Quality control
3.2.7. Service calls
3.2.8. Reporting
3.2.9. Tracking and verification of complaints
3.3. PacifiCorp retains the right to have special queries prepared and executed by Comverge for the purposes of internal and/or regulatory reporting
3.3.1. These queries will be written and executed at no additional cost to PacifiCorp
Database Management. (a) Corporate - XX.Xxxxxxxx@xxxxxxxxxxxxxxxx.xxx
(b) Xxxxxxx Institute/SJC: xxxxxxxx@xxxxxxxxxxxxxxxx.xxx; and
(c) Xxxxxxx Institute/Chantilly:xxxx.x.xxxxxxxxx@xxxxxxxxxxxxxxxx.xxx
Database Management. Service Provider responsibilities include:
1. Perform control functions in adherence to Change Management procedures to support systems existing as of the Commencement Date, as well as any planned new systems development.
2. Plan for changes in the size of databases that result from business growth and project implementation, in conjunction with Capacity Management as described in Exhibit 2.1.2.
3. Maintain, operate, and upgrade automated monitoring tools to monitor database performance.
4. Perform database shutdowns and restarts.
5. Proactively perform database optimization.
6. Recommend to DCS Customer and perform activities to avoid incidents and performance degradations.
Database Management. A documentation system is provided by the Program and is required to track patient education and outcomes information. If not already a recognized Outcomes Personal Pharmacist, pharmacists must enroll and complete training for the OutcomesMTM ® system. Data must be kept current for all Participants by the Pharmacist Network Provider. Minimum dataset requirements are defined in the Program tools.
Database Management. ACS will provide the database management Services and activities associated with the maintenance and support of databases contained in Schedule L of the Agreement (e.g., MS SQL server, IMS, and DB2). This includes responsibility for managing data, namely data set placement, database performance, and data recovery and integrity at a physical level. The following table identifies the database management roles and responsibilities. For this table, 3.
1.2.4 specific roles and responsibilities that denote sub-categories for Microsoft SQL Server with Symetra identified as the responsible Party, Symetra will be the primary resource for that task, and ACS will provide secondary support as defined in the SDRM.
