Database Administrator

Job Title: Database Administrator Job ID: 25-10619 Location: Austin, TX Duration: 02 months of contract Introduction The Agency has an on-premise installation of Claris FileMaker Server v13 software. The Agency needs to recover administrative‑level user access to this software and then port the database running on it to FileMaker Cloud. This project would occur in three successive phases. In Phase1 of the project, project staff will recover administrative‑level user access to FileMaker Serverv13. Project staff will then create new administrative‑level user access credentials for the Agency. Finally, project staff will create two (2) backups of the database running on the FileMaker Server software. In Phase2 of the project, project staff will create a new database for the Agency on the FileMaker Cloud platform. This database will be identical to the structure (schema) of the Agency's existing on‑premise FileMaker database. In Phase3 of the project, project staff will upload a copy of the Agency's on‑premise FileMaker database to the new FileMaker Cloud database created in Phase2. Project staff will then verify the success of the database transfer to the cloud via a series of verification checks. Background The Agency desires to modernize its database infrastructure by moving to FileMaker Cloud. To do this, the Agency needs project staff to access its instance of FileMaker Serverv13 and backup the database running on it, create a new instance of its database on the FileMaker Cloud platform, and then transfer a copy of its existing on‑premise FileMaker database to FileMaker Cloud. The Agency's existing on‑premise database has approximately 7,300 records. Each record has the same forty‑five (45) fields: 25 Text fields 9 Number fields 4 Date fields 4 Calculation fields 3 Summary fields The database does not appear to have any container fields. The Agency already has a subscription to FileMaker Cloud. Scope of Work Phase1: Recover Admin‑Level Access to FileMaker Server Project staff will gain administrative‑level user access to the Agency's on‑premise instance FileMaker Serverv13 and create a new set of administrative‑level access credentials for the Agency. Project staff will then create two local backups of the Agency's FileMaker database. 3.1.1. Recover administrative‑level user access to FileMaker Serverv13. 3.1.2. Create one (1) set of administrative‑level user access credentials to FileMaker Server. 3.1.3. Create two (2) backups of the database running on FileMaker Server. Phase2: Create New Database in FileMaker Cloud Identical in Structure to Existing On‑Premise Database Project staff will create a new (unpopulated) database on the FileMaker Cloud platform that duplicates the structure (schema) of the Agency's existing on‑premise FileMaker database. 3.2.1. Create new database on FileMaker Cloud duplicating the existing on‑premise database structure and function. Phase3: Transfer a Copy of the On‑Premise FileMaker Database to FileMaker Cloud Project staff will upload a copy of the Agency's on‑premise FileMaker database to the new FileMaker Cloud database created in Phase2. Using the existing on‑premise database as a reference, project staff will then verify that the new cloud database is accurately populated and fully functional. 3.3.1. Verify readiness of on‑premise FileMaker database copy for upload to FileMaker Cloud. 3.3.2. Remediate any pre‑upload issues (if necessary). 3.3.3. Upload database copy to FileMaker Cloud. 3.3.4. Verify cloud database functionality and accuracy by... 3.3.4.1. Ensuring all records have successfully uploaded. 3.3.4.2. Ensuring all record data fields function properly. 3.3.4.3. Selecting at least 350 nonsequential records and comparing them to the same record in the on‑premise database to ensure all data fields have properly populated. 3.3.4.4. Certifying the above to the Agency. Note: Task3.3.3 may be adjusted to uploading a sample of individual records should no backup copy of the Agency's entire database be successfully created during Phase1. A modified version of Task3.3 and verification process for Task3.4 would then follow. The Agency and project staff will mutually agree upon a revised sample size for Task3.3 and verification process for Task3.4 if Phase1 work cannot be completed. Deliverables Phase1:

• 1) One (1) set of functional FileMaker Server administrator‑level user access credentials.
• 2) Two (2) backup copies of on‑premise FileMaker database.

Phase2: (3) New FileMaker Cloud database identical in structure and function to existing on‑premise FileMaker database. Phase3:

• 4) Populated and functional FileMaker Cloud database.
• 5) Certification that all database records have successfully transferred to cloud.
• 6) Certification that all record data fields function properly.
• 7) Report on test of 350 nonsequential records.
• 8) Certification that cloud database is accurately populated and fully functional.

Candidate Skills and Qualifications Minimum Requirements: Candidates that do not meet or exceed the minimum stated requirements (skills/experience) will be displayed to customers but may not be chosen for this opportunity. YearsRequired/PreferredExperience4RequiredExperience recovering FileMaker Server access, experience working with FileMaker Server and FileMaker Cloud, and experience transferring on‑prem FileMaker databases to FileMaker Cloud. Contact Jaya Balaji: View email address on click.appcast.io | View phone number on click.appcast.io | URL: #J-18808-Ljbffr Sunrise Systems