Versions Compared

Old Version 14

changes.mady.by.user Le, Michelle

Saved on

compared with

New Version 15

changes.mady.by.user Le, Michelle

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

Data models are currently saved in \\tc4s0a\Groups\AARA\AARAD\DBA\<APP_NAME>\Data Model\
Stored procedures/packages are at http://tfsprod:8080/tfs/CivAv/CivAv_Database/_versionControl

Software

TOAD

To access the database, run scripts, etc.

erWin

To update data models for Data Management approval

Reference Documents

Access to Database Passwords

Access to Database Passwords

DBA Tasks

DBA process and tasks

ERWIN Guide

ERWIN guide

Data Management Naming Conventions for Data Models - Quick Reference Guide

RDIMS #1079406

Generate Data Dictionary for Data Model

ERWIN Reports Guide

Materialized Views problem

Materialized Views problems

Data Model Changes

Expand
title

...

How to make data model changes and move them through the environments

  1. Check out data model using Visual Studio

  2. Make changes (refer to ERWIN guide document)

  3. Check in data model back to TFS

  4. Send data model to DMI for review

  5. If the data model gets rejected, DMI will send back an RDIMS doc detailing the problems

    • Negotiate some of the problems with DMI and correct the rest. Update the doc and send the corrected data model to DMI again. This process might take several rounds depending on the volume and complexity of the changes.

  6. DMI will send an email letting us know when they approve the data model

  7. Save the new approved data model under: \\tc4s0a\Groups\AARA\AARAD\DBA\CCARCS\Data Model

  8. Move the previous approved data model to: \\tc4s0a\Groups\AARA\AARAD\DBA\CCARCS\Data Model\Archive

  9. Generate the scripts using erWIN (refer to ERWIN guide document for steps). Carefully review the script as sometimes there are adjustments that need to be made.

  10. Save scripts in: \\tc4s0a\Groups\AARA\AARAD\DBA\<APP_NAME>\Change Management

  11. Comment out to the DROP table command from the script

  12. Run the scripts in DEV.

    • If errors occur while executing the script, cancel the script and save the output to analyze the errors and fix them. Resume running the script until no errors.

  13. To move these changes to Acceptance / Production, open a change request (scheduled for, at minimum, 3 business days later).

    • Acceptance change: Script will need to be sent to DMI team for review.

    • Production change: In the plan, indicate that DMI will need to get the script from the ACC change.