Database Change Management Plan

You are tasked with creating a comprehensive database change management plan based on the provided information. Follow these instructions carefully to generate a detailed plan that adheres to the standard operating procedure (SOP).

First, review the change details:

Change Description:
{{CHANGE_DESCRIPTION}}

Affected Tables:

{{AFFECTED_TABLES}}

Estimated Impact: {{IMPACT_LEVEL}}
Urgency: {{URGENCY_LEVEL}}

Now, create a database change management plan that covers the following sections:

1. Local development phase test cases and validation criteria
   - Outline specific test cases to validate the change in the local development environment
   - Define clear validation criteria for each test case

2. Production data testing methodology
   - Describe the approach for testing the change using production-like data
   - Include steps to ensure data integrity and security during testing

3. Peer review requirements and participants
   - List the required participants for the peer review process
   - Specify the review criteria and expected outcomes

4. Production deployment schedule and steps
   - Provide a detailed timeline for the deployment
   - Break down the deployment process into clear, sequential steps

5. Rollback procedures
   - Outline a comprehensive rollback plan in case of deployment issues
   - Include specific steps to revert the changes and restore the previous state

6. Post-deployment verification tests
   - List the tests to be performed immediately after deployment
   - Specify the criteria for determining deployment success

7. Documentation updates needed
   - Identify all documentation that requires updating as a result of this change
   - Provide guidelines for updating each document

For each section, provide detailed and specific information relevant to the change described. Consider the impact level and urgency when determining the depth and breadth of each section.

After addressing all the sections, include a paragraph on special considerations based on the nature of this change. Take into account the affected tables, impact level, and urgency to highlight any unique aspects or potential risks that require additional attention.

Present your database change management plan in a clear, well-structured format. Use headings for each main section and bullet points or numbered lists for detailed steps within each section. Ensure that the plan is comprehensive, easy to follow, and aligns with the provided change details.