Project Deployment Plan Template

<Consultant logo> <Client logo>
<Client Org. Name>
<Project Name> Project
Charlotte-Mecklenburg Schools (CMS)

Managing for Performance Project
Data Warehouse Deployment Plan
Distribution: Jay Parker, Jacob Porter
Prepared By: Joseph Mercier, Rafael Salas,
Derek Sanderson, Gary Miller
Status: <Draft; Final>
Initial Release Date: September 18, 2009
Latest Revision Date: November 19, 2009
<Client Name> - <Project Name> <Document Name>
©2020 , ALL RIGHTS RESERVED.

CONTENTS OF THIS DOCUMENT ARE PROPRIETARY AND MAY NOT BE DISTRIBUTED WITHOUT THE PRIOR
WRITTEN CONSENT OF MARINER <CONSULTANT> AND <CLIENT NAME>.
10/22/20 ii
Initial Approval
By CMS<Client Org.> _______________________________________
Jay Parker<Client Name> Date
System Workstream Team Lead<Title>
By <Consultant> _______________________________________
<Consultant Name> Date
<Title>
Joseph Mercier Date
Development Project Manager
10/22/20 iii
Revision History
Date Reason CMS Mariner
9/22/09 Added Standard Deployment Pattie Hale
9/28/09 Modify Standard Deployment and Fendy Huang

Sprint #5 Deployment
10/1/09 Modify Sprint #5 Deployment Matthew

Campbell
10/7/09 Added additional details Pattie Hale
11/19/09 Added Sharepoint information Cathy stadler
10/22/20 iv
Contents
PURPOSE OF THIS DOCUMENT.........................................................................................................6
DEPLOYMENT PRINCIPLES AND POLICIES....................................................................................6
DEPLOYMENT APPROACH AND PROCEDURES COMMON TO ALL RELEASES..................7
OVERVIEW...............................................................................................................................................7
INSTALLATION PROCEDURES.........................................................................................................13
SERVERS AND FILE LOCATIONS............................................................................................................13
Database............................................................................................................................ 13
Middle tier - MTS/COM+.....................................................................................................14
Web Server......................................................................................................................... 14
PREPARING THE DATABASE....................................................................................................................15
1) Establish Database.........................................................................................................15
2) Load Default Data........................................................................................................... 15
3) Create Users & Groups...................................................................................................15
4) Grant Permissions.......................................................................................................... 15
5) Verify Databases............................................................................................................ 15
SETTING UP SECURITY............................................................................................................................32
SETTING UP APPLICATION(S)..................................................................................................................32
SSIS Application:................................................................................................................ 32
Verify Setup........................................................................................................................ 42
UNINSTALL PROGRAM..............................................................................................................................42
DEPLOYMENT TOOLSETS AND TEMPLATES/SAMPLES..........................................................42
APPENDIX A. DEPLOYMENT APPROACH AND PROCEDURES UNIQUE TO THE

CURRENT RELEASE (SPRINT NO. 5, 09/30/2009..........................................................................43
SERVERS AND FILE LOCATIONS..............................................................................................................44
Database............................................................................................................................ 44
Web Server......................................................................................................................... 44
10/22/20 v
5) Verify Databases............................................................................................................ 45
SETTING UP SECURITY.........................................................................................................................45
Verify Setup........................................................................................................................ 45
UNINSTALL PROGRAM..............................................................................................................................45
APPENDIX B. DEPLOYMENT APPROACH AND PROCEDURES UNIQUE TO THE

CURRENT RELEASE (NO. N, <DATE>.............................................................................................46
SERVERS AND FILE LOCATIONS..............................................................................................................46
Database............................................................................................................................ 46
Web Server......................................................................................................................... 46
3) Create Tables, Views, Triggers & Stored Procedures.....................................................47
6) Verify Database.............................................................................................................. 47
SETTING UP SECURITY............................................................................................................................48
Verify Setup........................................................................................................................ 49
Uninstall Program................................................................................................................................49
10/22/20 vi
Charlotte-Mecklenburg Schools – Managing for Performance Project Deployment Plan
Purpose of this Document

The purpose of deployment document is to ensure that the system successfully reaches its users.
This document defines the principles and policies, approach and procedures, and toolsets that will
be followed in deploying new or updated components of the Managing for Performance data
warehouse and educational analytics<Project Name> applications from one technology environment
to another (Sandbox  QA  Production). The document will also address the procedures for
backing out of a deployment event and reverting to the previous validated version.
All of the sections of this document, which could include installation plans, installation files, database
creation and update scripts, training plans, database conversion plans and scripts, and release
notes, are designed to ensure that the system deployment is successful and repeatable.
Deployment Principles and Policies

To be defined by CMS <Client Org.> …
Environments Supporting Best Practice Development and Deployment Processes
Development Production
Environment Environment
Quality Assurance
Environment
IIS Reporting IIS Reporting IIS Reporting

Services Services Services
Server SQL Server Server SQL Server Server SQL Server
Quality Features: Quality Features: Quality Features:
1. Unit Testing of 1. First test of 1. Isolated from
all Code Artifacts deployment developer
2. Testing of 2. Full integration credentials
Application testing 2. Isolated from
Upgrades 3. Full Regression next generation
Testing
Standard development to deployment lifecycle
Emergency fix lifecycle
Figure 1
10/22/20 Page 7 <Client – Project>CMS-

Deployment Approach and Procedures Common to All

Releases
Overview
Standard Deployment Approach
1. CMS Technology Support to create full backup of current Production Databases and objects.
If rollback is necessary, then this Production copy will be the rollback point.
a. Databases
i. \\K12CentralHub
ii. \\KD12DWImport
iii. \\K12DWStage
iv. \\K12DW
v. \\Pamlico
b. SSIS
i. Hub SSIS
ii. Import SSIS
iii. Transform and Load SSIS
c. SSRS
i. ReportServer DB
ii. Reporting Services encryption keys – done from Reporting Services
configuration manager
d. SharePoint
i. Sharepoint Backups
ii. Sharepoint Database Backups
e. File System & Other Files (DLLs, etc)
2. CMS <Client Org.> Technology Support to restore Production copy of databases and objects
on QA server.
a. Databases
i. \\K12CentralHub
ii. \\K12DWImport
iii. \\K12DWStage
iv. \\K12DW
v. \\Pamlico
b. SSIS
i. Hub SSIS
ii. Import SSIS
iii. Transform and Load SSIS
c. SSRS
i. ReportServer DB
ii. Reporting Services encryption keys – from Step 2
iii.
d. SharePoint
i. Sharepoint Backups
ii. Sharepoint Database Backups
e. File System & Config Files (DLLs, etc)

3. QA Coordinator for application informs development team of date when ALL objects for
release should be in the rollout folder ready for QA promotion. This date should be 7-10
days prior to the tentative production rollout implementation.
4. QA is promoted to production only after a full week of stable testing on QA with NO

unresolved high or medium priority issues.
5. If ANY scripts or objects are changed WITHIN 24-48 hours of the scheduled promotion to
PRODUCTION, the Rollout is REJECTED and returns to the development team for further
testing and rescheduling.
6. Each Object and script to be deployed will be stored in TFS and when Developers determine
objects are ready for promotion to QA, Developer will copy objects into a new folder named
for that rollout date (IE: MFPRollout_09242009). The objects should also be scripted out and
placed in a shared folder (TBD – see bullet #4).
a. Databases: SQL Job scripts or script that not applicable to a particular database will
be placed in here. There is a main Database Name SQL script (i.e.
K12DWStage.SQL) contains all database objects that need to be update or modified
in each subfolder.
i. \\K12CentralHub
 K12CentralHub.sql contains all scripts for Hub, Annex, or DIG
database objects, permission, and data.
 K12CentralHubData_SSISConfigurations_QA.sql contains
configuration data for QA system.
ii. \\K12DW
 K12DW.sql contains all scripts for DW database objects, permission,
and data.
iii. \\K12DWImport
 K12DWImport.sql contains all scripts for DW Import database objects,
permission, and data.
iv. \\K12DWStage
 K12DWStage.sql contains all scripts for DW stage database objects,
 K12DWStageData_SSISConfigurations_QA.sql contains configuration
data for QA system.
v. \\Pamlico
 Pamlico.sql contains all scripts for Pamlico database objects,
b. SSIS: ETL Packages will be placed in this folder according to the functionalities.
i. Hub SSIS: ETL packages that extract data from ESIS, LAWSON<key data
sources>, or others to be loaded into the K12CentralHub Database.
ii. Import SSIS: ETL packages that extract data from K12CentralHub Database
to be loaded into the K12DWImport Database.

iii. Transform and Load SSIS: ETL packages that extract data from
K12DWImport Database to be loaded into the K12DW Database
c. SSRS: Reports will be placed in the folder according to the functionality
i. Teacher:<EndUserType1> Reports that will be used in the <EndUserType1>
Teacher Portal
ii. <EndUserType2> Principal: Reports that will be used in the <EndUserType2>
Principal Portal
iii. <EndUserType3> LC: Reports that will be used in the <EndUserType3>
Learning Community Portal
iv. <EndUserType4> District: Reports that will be used in the <EndUserType4>
District Portal
d. SharePoint: Solutions and code to be placed in the folder according to the
functionality
i. stsadm.ajaxifymoss: Enables Ajax for Web Applications
ii. CMS.MP____.ModifyWebConfigForDataLayer: Add connection strings for
datalayer on Layouts pages
iii. CMS.MP____.DataLayer: Data Layer Code
iv. ____CMS.MP.HelperMethods: Utility methods
v. ____CMS.MP.CustomPeoplePicker: Custom Entity Picker, used for search.
vi. ____CMS.MP.DIGManagement: Manage Instructional Groups pages
vii. ____CMS.MP.MasterPageFiles: Branding Feature
viii. ____CMS.MP.SiteTemplates: Site Templates for each portal
ix. ____CMS.MP.MyClassesWebPart: My Classes____ webpart
x. ____CMS.MP.MySIGsWebPart: My Shared Instructional Groups_____
webpart
xi. ____CMS.MP.StudentsInInstructionalGroupWebPart______WebPart:
Students in Instructional Group_____ webpart
xii. drop (For additional code to be run)
e. Test
7. Proposed Shared Folder Setup: for storing copies of QA-Ready scripts and objects (as well
as in TFS). Note: ALL database scripts for SSRS and SharePoint should be included in the
appropriate subfolder. Developers are responsible for including objects in the shared
folder when determined they are QA-Ready.
\\MFPQA Rollouts
\\Rollout_Date
\\SharePoint
\\Solutions
\\Code
\\Additional Instructions (Deployment Scripts)
\\SQL
\\K12CentralHub
\\K12DW
\\K12DWImport
\\K12DWStage
\\Pamlico
\\SSIS
\\CMS_Hub_ETL
\\K12DWImport_ETL
\\K12DW_ETL

\\SSRS
\\Teacher<EndUserType1>
\\<EndUserType2>Principal
\\<EndUserType3>LC
\\<EndUserType4>District
\\Test
Figure 1: Physical Structure of Rollout Folder
8. CMS Technology Support will apply scripts and promote files from Rollout folder (i.e. MFPQA
Rollouts\Rollout_20090925) to appropriate places on QA system.
a. Databases: Apply SQL script against each target database to update the objects,
permissions, or data.
i. \\K12CentralHub
ii. \\K12DWImport
iii. \\K12DWStage
iv. \\K12DW
v. \\Pamlico
b. SSIS: Replace the ETL packages on the SSIS Package Store Subfolder accordingly.
i. Hub SSIS: Make sure modify/verify the PathPackageFiles SSIS
Configuration value in the [K12CentralHub].[ETL].[SSISConfigurations]
table to point to the physical path of the Hub SSIS folder.
ii. Import SSIS: Make sure modify/verify the PathPackageFiles SSIS
Configuration value in the [K12DWStage].[ETL].[SSISConfigurations]
table to point to the physical path of the Import SSIS folder.
iii. Transform and Load SSIS: Make sure modify/verify the
DWPathPackageFiles SSIS Configuration value in the [K12DWStage].

[ETL].[SSISConfigurations] table to point to the physical path of the DW

SSIS folder.
c. SSRS – Replace the reports on the SSRS Report Manager subfolder accordingly
i. \\<EndUserType1>Teacher
ii. \\<EndUserType2>Principal
iii. \\<EndUserType3>LC
iv. \\<EndUserType4>District
d. SharePoint: Run batch file on index server to install solution file and run any
additional code against portals.
i. \\Solutions
ii. \\Code
e. Test
f. Validate: Check portals and reports. For diagnostics, check the ULS log files.
9. QA Testing will begin, and QA environment should have no further changes for ‘clean’
integration testing.
10. After QA testing has been completely reviewed, validated, and is ready for production, CMS
Technology Support will indicate date of production rollout.
11. Production Rollout:

i. CMS Technology Support will create backup of Production database and
objects as in Bullet #1.
ii. CMS Technology Support will apply scripts and promote objects from Rollout
folder (i.e. MFPQA Rollouts\Rollout_20090925) on Production.
iii. Validate Rollout.
12. Development TEAM to validate all functioning parts of Production: SSIS, Portal
WebPages, Reports, to ensure that everything is functioning as expects:
i. Portal WebPages – appear as expected without error
ii. Reports – appear as expected, and data appears
iii. ETL – SSIS packages run to completion and data is populated in DW
13. Key business users to validate changes are in production.
14. Rollout is archived and marked as successful.
Installation Procedures
Servers and File Locations
Database
QA DB Server Name:
 MFPQASQL1
 MFPQASSAS1
 MFPQASSRS01
QA Database Name:

 K12CentralHub
 K12DW
 K12DWImport
 K12DWStage
 Pamlico
QA DBO Account:
 SSIS Proxy account used to run the SSIS SQL Jobs
Production DB Server Name:
Internal
 2 Node Cluster: MFPINTSSASCL01/MFPINTSSASCL02
 2 Node Cluster : MFPINTSQLCL01/ MFPINTSQLCL02
 2 Node Cluster : MFPINTSQLCL03/MFPINTSQLCL04
 2 Node Cluster: MFPINTSSRSCL01/ MFPINTSSRSCL02
External
 2 Node Cluster: MFPEXTSSRSCL01/MFPEXTSSRSCL02
 2 Node Cluster : MFPEXTSQLCL01/ MFPEXTSQLCL02
Production Database Name:

 K12CentralHub
 K12DW
 DK12DWImport
 K12DWStage
 Pamlico
Production DBO Account:

 SSIS Proxy account used to run the SSIS SQL Jobs
Middle tier
QA Server Name:
QA Package Locations: <list>
Production Server Name:
Production Package Locations: <list>
Web Server <CMS Support Team to define>

QA Server Name:
QA Physical Directory Path:

QA Virtual Directory Name:

Production Physical Directory Path:
Production Virtual Directory Name:
Preparing the Database
Establish Load Default Create Users Grant Verify

Databases Data & Groups Permissions Databases
1) Establish Database
Run each main database script against appropriate database to create all the data types, tables,
views, triggers, stored procedures, functions, users, roles, permissions, and default data.
2) Load Default Data

Load default SSIS configuration data files to make sure the SSIS package connection strings for
all the connection managers are pointed to the right database server, file location with
appropriate permission.
3) Create Users & Groups

Additional users and groups need to be created for SharePoint applications.
4) Grant Permissions
<List scripts or other measures required for granting permissions to appropriate users and
groups for the database>
5) Verify Databases
SQL Jobs
Verify the following SQL jobs were created:
 CMS_Hub_ETL_Manual
 CMS_K12DW_ETL
 CMS_K12DW_ETL_HistoricalLoad
 CMS_K12DWFactStudentAssessment_ABCTableALoad
 CMS_K12DWFactTableBFactStudentAssessment_AYPLoad
 CMS_K12DWImport_ETL_Manual
 CMS_K12DWTransformLoad_ETL_Manual
K12CentralHub Database

Tables Created
Verify the following tables were created:
 Annex.Assessment
 Annex.AssessmentContentStandard
 Annex.AssessmentDevelopment
 Annex.AssessmentFamily
 Annex.AssessmentLevelItem
 Annex.AssessmentModule
 Annex.AssessmentRelationshipType
 Annex.AssessmentReportingMethod
 Annex.AssessmentRevision
 Annex.AssessmentSection
 Annex.AssessmentType
 Annex.Authority
 Annex.AuthorityType
 Annex.AuthorizingEntityType
 Annex.GradeLevel
 Annex.LEA
 Annex.LEAArea
 Annex.OperationalStatus
 Annex.RelatedAssessment
 Annex.School
 Annex.SchoolGrade
 Annex.SchoolHistory
 Annex.SchoolType
 Annex.SEA
 Annex.SourceSchoolMapping
 DIG.Filter
 DIG.InstructionalGroup
 DIG.InstructionalGroupClass
 DIG.InstructionalGroupFilter
 DIG.InstructionalGroupRight
 DIG.InstructionalGroupSchool
 DIG.InstructionalGroupScope
 DIG.InstructionalGroupStaff
 DIG.InstructionalGroupType
 DIG.InstructionalPosition
 ETL.SSISConfigurations
 HUB.CMS_Calendar
 HUB.COUNTRIES
 HUB.COURSE_SELECTIONS
 HUB.COURSES
 HUB.CR_YEAR_PARAMS
 HUB.DPI_ABCSUMMARY600
 HUB.DPI_AYPABCDPI
 HUB.EDUCATION_HANDICAPPED_COND
 HUB.EDUCATIONAL_HANDICAP

 HUB.ESIS_ADMISSION_CODES
 HUB.ESIS_ADMISSION_WITHDRAW
 HUB.ESIS_ATT_ARCHIVE_SUMMARY
 HUB.ESIS_ATTENDANCE_CODES
 HUB.ESIS_COURSE_LENGTHS
 HUB.ESIS_CREDITS
 HUB.ESIS_ELEM_ATTENDANCES
 HUB.ESIS_ENROLMENTS
 HUB.ESIS_HOMEFORM_BY_GRADE
 HUB.ESIS_HOMEFORM_ENROLMENTS
 HUB.ESIS_HOMEFORMS
 HUB.ESIS_HOMEFORMS_STUDENTS
 HUB.ESIS_INCIDENT_ACTION_TYPE
 HUB.ESIS_INCIDENT_CAUSE_CODES
 HUB.ESIS_INCIDENT_CODES
 HUB.ESIS_INCIDENT_LOCATION_CODES
 HUB.ESIS_INCIDENT_OCCURRED_TIME_CODES
 HUB.ESIS_INCIDENT_TYPES
 HUB.ESIS_INCIDENT_VICTIMS
 HUB.ESIS_INCIDENTS
 HUB.ESIS_MUNICIPALITIES
 HUB.ESIS_REGISTRATIONS
 HUB.ESIS_SCHOOL_PERIOD_TIMES
 HUB.ESIS_SCHOOL_SCHEDULES
 HUB.ESIS_SEC_ATTENDANCES
 HUB.ESIS_SPED_DELIVERY_LEVELS
 HUB.ESIS_STUDENT_INCIDENTS
 HUB.ESIS_STUDENT_INCIDENTS_VICTIM
 HUB.ESIS_TRIBAL_CODES
 HUB.ESIS_WITHDRAW_CODES
 HUB.GRADES
 HUB.LANGUAGE_CODES
 HUB.LAWSON_STAFF_DEV_JOBS
 HUB.LAWSON_STAFF_DEV_SCHOOLS
 HUB.MASTER_TIMETABLES
 HUB.MINISTRY_COURSE_CODES
 HUB.NUTRITION
 HUB.PARENTS
 HUB.PROG_ENTRY_REASON_CODES
 HUB.PROGRAM_ASSIGNMENTS
 HUB.PROGRAM_TYPES
 HUB.ROOMS
 HUB.SCHEDULES
 HUB.SCHOOL_GRADES_TAUGHT
 HUB.SCHOOLS
 HUB.SPARTA_ABCs_ALG1_Growth
 HUB.SPARTA_ABCs_ALG2_Growth
 HUB.SPARTA_ABCs_BIOL_Growth

 HUB.SPARTA_ABCs_CECO_Growth
 HUB.SPARTA_ABCs_CHEM_Growth
 HUB.SPARTA_ABCs_ENG1_Growth
 HUB.SPARTA_ABCs_GEOM_Growth
 HUB.SPARTA_ABCs_HIST_Growth
 HUB.SPARTA_ABCs_Math_Growth
 HUB.SPARTA_ABCs_PHYS_Growth
 HUB.SPARTA_ABCs_PSCI_Growth
 HUB.SPARTA_ABCs_Read_Growth
 HUB.SPED_EXCEPTIONALITIES
 HUB.SPED_EXCEPTIONALITY_CODES
 HUB.STAFF_DEV_EMPLOYEES
 HUB.StaffToTeacherMappingByRule
 HUB.StaffToTeacherMappingRules
 HUB.STANDARD_SUB_TESTS
 HUB.STANDARD_TEST_SCORES_NEW
 HUB.STANDARD_TESTS_NEW
 HUB.STATE_MINISTRY_COURSES
 HUB.STUDENT_PLANS
 HUB.STUDENT_SUB_TEST_ATTEMPTS
 HUB.STUDENT_SUB_TEST_SCORES
 HUB.STUDENT_TEST_ATTEMPTS
 HUB.STUDENTS
 HUB.SystemStudentXRef2
 HUB.TEACHERS
 HUB.TEST_EXEMPTION_CODES
 HUB.TEST_SCORE_TYPES
 HUB.TEST_TYPES
Stored Procedures Created

Verify the following stored procedures were created:
 NA
Functions Created
 HUB.ETLGetInstructionalLevel
 HUB.ETLGetSubjectArea
 Annex.ETLPercentileRecord
 DIG.fInstructionalGroupStaffSourceDataQuery
Triggers Created
Verify the following triggers were created:
 Annex.Assessment.tuAssessment
 Annex.AssessmentContentStandard.tuAssessmentContentStandard
 Annex.AssessmentDevelopment.tuAssessmentDevelopment

 Annex.AssessmentFamily.tuAssessmentFamily
 Annex.AssessmentLevelItem.tuAssessmentLevelItem
 Annex.AssessmentModule.tuAssessmentModule
 Annex.AssessmentRelationshipType.tuAssessmentRelationshipType
 Annex.AssessmentReportingMethod.tuAssessmentReportingMethod
 Annex.AssessmentRevision.tuAssessmentRevision
 Annex.AssessmentSection.tuAssessmentSection
 Annex.AssessmentType.tuAssessmentType
 Annex.Authority.tuAuthority
 Annex.AuthorityType.tuAuthorityType
 Annex.AuthorizingEntityType.tuAuthorizingEntityType
 Annex.LEA.tuLEA
 Annex.LEAArea.tuLEAArea
 Annex.OperationalStatus.tuOperationalStatus
 Annex.School.tuSchool
 Annex.SchoolGrade.tuSchoolGrade
 Annex.SchoolHistory.tuSchoolHistory
 Annex.SchoolType.tuSchoolType
 Annex.SEA.tuSEA
 Annex.SourceSchoolMapping.tuSourceSchoolMapping
Views Created
Verify the following views were created:
 Annex.vAssessment
 Annex.vSchool
 Annex.vSchoolCurrentGrade
 Annex.vSchoolHistoryGrade
 HUB.vExceptionChildStatus
 HUB.vGet504Status
 HUB.vLastestExceptionChildStatus
 HUB.vStaffToTeacher
 HUB.vStudentESLStatus
 HUB.vStudentLEPStatus
Users and Groups Created, Permissions Granted & Default Data Loaded
Prepare a series of tests to validate users, groups, permissions and default data were all created
properly.

As <user x> run following select statement to verify <describe user, permissions & default data being
tested and expected results>:
SELECT SEAID, FIPSStateCode
FROM Annex.SEA
As <SSIS Proxy> run following select statement to verify <describe user, permissions & default data
being tested and expected results>:
SELECT top 10 *
FROM DIG.fInstructionalGroupStaffSourceDataQuery()
being tested and expected results >:
SELECT [ConfigurationFilter]
,[ConfiguredValue]
,[PackagePath]
,[ConfiguredValueType]
FROM [K12CentralHub].[ETL].[SSISConfigurations]
WHERE [ConfigurationFilter] = 'PathPackageFiles'
K12DW Database
Tables Created
 DW.DimAssessment
 DW.DimAssessmentAdministered
 DW.DimAssessmentLevel
 DW.DimAttendanceInfo
 DW.DimClass
 DW.DimCommonProgram
 DW.DimCourse
 DW.DimCourseWorkTaken
 DW.DimDate
 DW.DimDemographic
 DW.DimEntryExitInfo
 DW.DimIncident
 DW.DimProgram
 DW.DimRelatedAssessment
 DW.DimScenario
 DW.DimSchool

 DW.DimServiceSetting
 DW.DimSnapshotInfo
 DW.DimStaff
 DW.DimStudent
 DW.FactSchoolEnrollment
 DW.FactStudentAssessment
 DW.FactStudentClassAssessment
 DW.FactStudentClassEnrollment
 DW.FactStudentCourseAssessment
 DW.FactStudentCourseWork
 DW.FactStudentDailyClassAttendance
 DW.FactStudentProgram

 RPT.pGetAssessmentLevels_ByAssessmentID
 RPT.pGetAssessments_AllCourseInstancesForInstructor_ByClassSourceIDAndAssessment
Family
 RPT.pGetAssessments_ByClassSourceIDAndAssessmentFamily
 RPT.pGetBasicEOGReportHeader_ByClassSourceIDAndAssessmentID
 RPT.pGetEOGEOCByPeriodReport_ByClassSourceIDAndAssessmentID
 RPT.pGetEOGEOCByStudentReport_ByClassSourceIDAndAssessmentID
 RPT.pGetEOGEOCByTeacherReport_ByClassSourceIDAndAssessmentID
 RPT.pGetStaffDetails_ByStaffSourceID
Triggers Created
 NA
Views Created
 NA
properly.

SELECT [ClassID____ID]
,[SchoolID_____ID]
,[UniqueSourceID]
FROM [K12DW].[DW].[DimClass]
WHERE ClassID = -1
SELECT [ScenarioID]
,[ScenarioCode]
,[Scenario]
FROM [K12DW].[DW].[DimScenario]
K12DWImport Database
Tables Created
 Import.DimAssessment
 Import.DimAssessmentLevel
 Import.DimAttendanceInfo
 Import.DimClass
 Import.DimCommonProgram
 Import.DimCourse
 Import.DimDate
 Import.DimDemographic
 Import.DimEntryExitInfo
 Import.DimProgram
 Import.DimRelatedAssessment
 Import.DimSchool
 Import.DimServiceSetting
 Import.DimStaff
 Import.DimStudent
 Import.FactSchoolEnrollment
 Import.FactStudentAssessment
 Import.FactStudentClassEnrollment
 Import.FactStudentCourseAssessment
 Import.FactStudentDailyClassAttendance
 Import.FactStudentProgram


 NA
Functions Created
Verify the following functions were created:

 Import.fGenerateDimCommonProgramDataset
 Import.fGenerateDimDemographicDataset
 Import.fGenerateDimEntryExitInfoDataset
 Import.fGenerateDimServiceSettingDataset
Triggers Created
 NA
Views Created
 NA
properly.
SELECT TOP 10 [ID]
,[RecognizedDate]
,[AdministeredDate]
,[EnrolledStateAgencyNumber]
,[StudentSISID]
,[SourceAssessmentSectionID]
FROM [K12DWImport].[Import].[FactStudentAssessment]
SELECT TOP 10 * FROM Import.fGenerateDimCommonProgramDataset()
K12DWStage Database
Tables Created
 DW.DimAssessmentLevelStage
 DW.DimAssessmentStage

 DW.DimAttendanceInfoStage
 DW.DimClassStage
 DW.DimCommonProgramStage
 DW.DimCourseStage
 DW.DimDateStage
 DW.DimDemographicStage
 DW.DimEntryExitInfoStage
 DW.DimProgramStage
 DW.DimRelatedAssessmentStage
 DW.DimSchoolStage
 DW.DimServiceSettingStage
 DW.DimStaffStage
 DW.DimStudentStage
 DW.FactSchoolEnrollmentStage
 DW.FactStudentAssessmentStage
 DW.FactStudentClassEnrollmentStage
 DW.FactStudentCourseAssessmentStage
 DW.FactStudentDailyClassAttendanceStage
 DW.FactStudentProgramStage
 ETL.SSISConfigurations
 NA
Triggers Created
 NA
Views Created
 NA
properly.

SELECT TOP 10 [AssessmentLevelID]
,[AssessmentTitle]
,[AssessmentPurpose]
,[LevelforwhichDesigned]
FROM [K12DWStage].[DW].[DimAssessmentLevelStage]
SELECT * FROM ETL.SSISConfigurations
WHERE ConfigurationFilter = 'DWPathPackageFiles'
Pamlico Database
Tables Created
 dbo.sysssislog
 ETLAudit.DataErrorSeverity
 ETLAudit.ETLContainerExecution
 ETLAudit.ETLControl
 ETLAudit.ETLDataError
 ETLAudit.ETLExecutionStatus
 ETLAudit.ETLPackageExecution
 ETLAudit.ETLPackageType
 ETLAudit.ETLProcessImportedBatch
 ETLAudit.ETLSSISLog
 ETLAudit.SSISConfigurations
 meta.Authority
 meta.BusinessElement
 meta.BusinessProcess
 meta.BusinessRule
 meta.CodeSet
 meta.CodeValue
 meta.Connection
 meta.ConnectionManager
 meta.ConnectionType
 meta.ConstraintType
 meta.DataElement

 meta.DataElementComments
 meta.DataElementLogicalType
 meta.DataElementMapping
 meta.DataElementNotFound
 meta.DataElementPhysicalType
 meta.DataElementValue
 meta.DataGroup
 meta.DataGroupLogicalType
 meta.DataGroupMapping
 meta.DataGroupNotFound
 meta.DataGroupPhysicalType
 meta.DataMappingSet
 meta.DataMappingSetType
 meta.DataSource
 meta.DataSourceType
 meta.Domain
 meta.DomainLogicalType
 meta.DomainPhysicalType
 meta.DomainValue
 meta.EnvironmentType
 meta.ETLContainer
 meta.ETLPackage
 meta.ETLPackageConstraint
 meta.ETLProcess
 meta.ETLProcessConstraint
 meta.Host
 meta.Pamlico
 meta.Report
 meta.ReportBusinessElement
 meta.ReportBusinessProcess
 meta.ValueMapping
 Report.Images
 Report.Info

 dbo.sp_ssis_addlogentry
 ETLAudit.pGetLastCompletedETLControl
 ETLAudit.pInsertETLContainerExecution
 ETLAudit.pInsertETLControl
 ETLAudit.pInsertETLPackageExecution
 ETLAudit.pInsertSSISLogEntry
 ETLAudit.pUpdateETLContainerExecution
 ETLAudit.pUpdateETLControl
 ETLAudit.pUpdateETLPackageExecution
 ETLAudit.usp_ManageLogs
 ETLReporting.pMonitor
 meta.pInsertDataElementMapping
 meta.pInsertDataGroupMapping
 meta.pSynchronizeExecutionMetadata
 meta.pUpsertETLContainer
 meta.pUpsertETLPackage
Functions Created
Verify the following functions were created:
 meta.ETLValueMappingLookUp
Views Created
 meta.vSSISLogErrorsNotOnReport
properly.
SELECT TOP 10 [CodeSetID]
,[AuthorityID]
,[CodeSetName]
,[CodeSetDefinition]
,[ReferenceCodeSet]
FROM [Pamlico].[meta].[CodeSet]
SELECT ReferenceCode,

CodeValue,
CodeValueDefinition,
DataElementValue
FROM [meta].[ETLValueMappingLookUp] (N'NCES Grade Level', N'eSIS',
N'ADMASSIST', N'GRADES', N'GRADE_CODE');
Setting Up Security
<describe measures for setting up security, roles, etc.>
Setting Up Application(s)
SSIS Application:
1) Make sure there are two Environment Variables created as:
 CMS_Data_Hub_ETL_Configuration : Point to the K12CentralHub database on QA system

(i.e. Data Source=<SQL Server Name>;Initial
Catalog=K12CentralHub;Provider=SQLNCLI10.1;Integrated Security=SSPI;)
 CMS_PerformanceDwDW_ETL_Configuration: Point to the K12DWStage database on QA

system (i.e. Data Source=<SQL Server Name>;Initial
Catalog=K12DWStage;Provider=SQLNCLI10.1;Integrated Security=SSPI;)
2) Copy all the SSIS packages from Rollout folder (\\MFPQA Rollouts\Rollout_Date\SSIS\) to the
SSIS Package Store folder (\MFP___\) on QA system.
Figure 2: SSIS Rollout Folder
Figure 3: SSIS Package Store Folder
3) Verify all the packages existed in the SSIS Package Store subfolder accordingly.
 CMS_Hub_ETL
 CMS_Hub_ETL_Load_CMS_Calendar

 CMS_Hub_ETL_Load_Course_Selections
 CMS_Hub_ETL_Load_Courses
 CMS_Hub_ETL_Load_CR_YEAR_PARAMS
 CMS_Hub_ETL_Load_DIG_BaseInstructionalGroups_Classes
 CMS_Hub_ETL_Load_DPI_ABCSUMMARY600
 CMS_Hub_ETL_Load_DPI_AYPABCDPI
 CMS_Hub_ETL_Load_Education_Handicapped_Cond
 CMS_Hub_ETL_Load_Educational_Handicap
 CMS_Hub_ETL_Load_ESIS_ADMISSION_CODES
 CMS_Hub_ETL_Load_ESIS_Admission_Withdraw
 CMS_Hub_ETL_Load_ESIS_ATTENDANCE_CODES
 CMS_Hub_ETL_Load_ESIS_Credits
 CMS_Hub_ETL_Load_ESIS_ELEM_ATTENDANCES
 CMS_Hub_ETL_Load_ESIS_Enrolments
 CMS_Hub_ETL_Load_ESIS_HOMEFORMS
 CMS_Hub_ETL_Load_ESIS_Homeforms_Students
 CMS_Hub_ETL_Load_ESIS_INCIDENT_ACTION_TYPE
 CMS_Hub_ETL_Load_ESIS_INCIDENT_CAUSE_CODES
 CMS_Hub_ETL_Load_ESIS_INCIDENT_CODES
 CMS_Hub_ETL_Load_ESIS_INCIDENT_LOCATION_CODES
 CMS_Hub_ETL_Load_ESIS_INCIDENT_OCCURRED_TIME_CODES
 CMS_Hub_ETL_Load_ESIS_INCIDENT_TYPES
 CMS_Hub_ETL_Load_ESIS_INCIDENT_VICTIMS
 CMS_Hub_ETL_Load_ESIS_INCIDENTS
 CMS_Hub_ETL_Load_ESIS_MUNICIPALITIES
 CMS_Hub_ETL_Load_ESIS_REGISTRATIONS
 CMS_Hub_ETL_Load_ESIS_SEC_ATTENDANCES
 CMS_Hub_ETL_Load_ESIS_SPED_DELIVERY_LEVELS
 CMS_Hub_ETL_Load_ESIS_STUDENT_INCIDENTS
 CMS_Hub_ETL_Load_ESIS_STUDENT_INCIDENTS_VICTIM
 CMS_Hub_ETL_Load_ESIS_TRIBAL_CODES
 CMS_Hub_ETL_Load_ESIS_Withdraw_Codes
 CMS_Hub_ETL_Load_GRADES

 CMS_Hub_ETL_Load_LANGUAGE_CODES
 CMS_Hub_ETL_Load_LAWSON_Staff_DEV_JOBS
 CMS_Hub_ETL_Load_LAWSON_Staff_DEV_SCHOOLS
 CMS_Hub_ETL_Load_Master_Timetables
 CMS_Hub_ETL_Load_Ministry_Course_Codes
 CMS_Hub_ETL_Load_Nutrition
 CMS_Hub_ETL_Load_Parents
 CMS_Hub_ETL_Load_Program_Assignments
 CMS_Hub_ETL_Load_Program_Entry_Reason_Code
 CMS_Hub_ETL_Load_Program_Types
 CMS_Hub_ETL_Load_Rooms
 CMS_Hub_ETL_Load_Schedules
 CMS_Hub_ETL_Load_SCHOOL_GRADES_TAUGHT
 CMS_Hub_ETL_Load_Schools
 CMS_Hub_ETL_Load_Sparta_ABCs_ALG1_Growth
 CMS_Hub_ETL_Load_Sparta_ABCs_ALG2_Growth
 CMS_Hub_ETL_Load_Sparta_ABCs_BIOL_Growth
 CMS_Hub_ETL_Load_Sparta_ABCs_CECO_Growth
 CMS_Hub_ETL_Load_Sparta_ABCs_CHEM_Growth
 CMS_Hub_ETL_Load_Sparta_ABCs_ENG1_Growth
 CMS_Hub_ETL_Load_Sparta_ABCs_GEOM_Growth
 CMS_Hub_ETL_Load_Sparta_ABCs_HIST_Growth
 CMS_Hub_ETL_Load_Sparta_ABCs_MATH_Growth
 CMS_Hub_ETL_Load_Sparta_ABCs_PHYS_Growth
 CMS_Hub_ETL_Load_Sparta_ABCs_PSCI_Growth
 CMS_Hub_ETL_Load_Sparta_ABCs_READ_Growth
 CMS_Hub_ETL_Load_SPED_EXCEPTIONALITIES
 CMS_Hub_ETL_Load_SPED_Exceptionality_Codes
 CMS_Hub_ETL_Load_Staff_Dev_Employees
 CMS_Hub_ETL_Load_StaffToTeacherMapping
 CMS_Hub_ETL_Load_Standard_Sub_Tests
 CMS_Hub_ETL_Load_Standard_Test_Scores_New
 CMS_Hub_ETL_Load_Standard_Tests_New

 CMS_Hub_ETL_Load_Student_Plans
 CMS_Hub_ETL_Load_Student_Sub_Test_Attempts
 CMS_Hub_ETL_Load_Student_Sub_Test_Scores
 CMS_Hub_ETL_Load_Student_Test_Attempts
 CMS_Hub_ETL_Load_Students
 CMS_Hub_ETL_Load_Teachers
 CMS_Hub_ETL_Load_Test_Exemption_Codes
 CMS_Hub_ETL_Load_Test_Score_Types
 CMS_Hub_ETL_Load_Test_Types
 K12DW_ETL
 CMS_PerformanceDw_ETL_Transform_DimAssessment
 CMS_PerformanceDw_ETL_Transform_DimAssessmentLevel
 CMS_PerformanceDw_ETL_Transform_DimAttendanceInfo
 CMS_PerformanceDw_ETL_Transform_DimClass
 CMS_PerformanceDw_ETL_Transform_DimCommonProgram
 CMS_PerformanceDw_ETL_Transform_DimCourse
 CMS_PerformanceDw_ETL_Transform_DimDate
 CMS_PerformanceDw_ETL_Transform_DimDemographic
 CMS_PerformanceDw_ETL_Transform_DimEntryExitInfo
 CMS_PerformanceDw_ETL_Transform_DimProgram
 CMS_PerformanceDw_ETL_Transform_DimRelatedAssessment
 CMS_PerformanceDw_ETL_Transform_DimSchool
 CMS_PerformanceDw_ETL_Transform_DimServiceSetting
 CMS_PerformanceDw_ETL_Transform_DimStaff
 CMS_PerformanceDw_ETL_Transform_DimStudent
 CMS_PerformanceDw_ETL_Transform_FactSchoolEnrollment
 CMS_PerformanceDw_ETL_Transform_FactStudentAssessment
 CMS_PerformanceDw_ETL_Transform_FactStudentAssessment_ABCFeed
 CMS_PerformanceDw_ETL_Transform_FactStudentClassEnrollment
 CMS_PerformanceDw_ETL_Transform_FactStudentDailyClassAttendance
 CMS_PerformanceDw_ETL_Transform_FactStudentProgram
 CMS_PerformanceDw_ETL_Load_DimAssessment
 CMS_PerformanceDw_ETL_Load_DimAssessmentLevel

 CMS_PerformanceDw_ETL_Load_DimAttendanceInfo
 CMS_PerformanceDw_ETL_Load_DimClass
 CMS_PerformanceDw_ETL_Load_DimCommonProgram
 CMS_PerformanceDw_ETL_Load_DimCourse
 CMS_PerformanceDw_ETL_Load_DimDate
 CMS_PerformanceDw_ETL_Load_DimDemographic
 CMS_PerformanceDw_ETL_Load_DimEntryExitInfo
 CMS_PerformanceDw_ETL_Load_DimProgram
 CMS_PerformanceDw_ETL_Load_DimRelatedAssessment
 CMS_PerformanceDw_ETL_Load_DimSchool
 CMS_PerformanceDw_ETL_Load_DimServiceSetting
 CMS_PerformanceDw_ETL_Load_DimStaff
 CMS_PerformanceDw_ETL_Load_DimStudent
 CMS_PerformanceDw_ETL_Load_FactSchoolEnrollment
 CMS_PerformanceDw_ETL_Load_FactStudentAssessment
 CMS_PerformanceDw_ETL_Load_FactStudentClassEnrollment
 CMS_PerformanceDw_ETL_Load_FactStudentDailyClassAttendance
 CMS_PerformanceDw_ETL_Load_FactStudentPrgram
 K12DWImport_ETL
 CMS_PerformanceDw_ETL_Historical_Import_DimAssessment
 CMS_PerformanceDw_ETL_Historical_Import_DimAssessmentLevel
 CMS_PerformanceDw_ETL_Import_DimAssessment
 CMS_PerformanceDw_ETL_Import_DimAssessmentLevel
 CMS_PerformanceDw_ETL_Import_DimAttendanceInfo
 CMS_PerformanceDw_ETL_Import_DimClass
 CMS_PerformanceDw_ETL_Import_DimCommonProgram
 CMS_PerformanceDw_ETL_Import_DimCourse
 CMS_PerformanceDw_ETL_Import_DimDate
 CMS_PerformanceDw_ETL_Import_DimDemographic
 CMS_PerformanceDw_ETL_Import_DimEntryExitInfo
 CMS_PerformanceDw_ETL_Import_DimProgram
 CMS_PerformanceDw_ETL_Import_DimRelatedAssessment
 CMS_PerformanceDw_ETL_Import_DimSchool

 CMS_PerformanceDw_ETL_Import_DimServiceSetting
 CMS_PerformanceDw_ETL_Import_DimStaff
 CMS_PerformanceDw_ETL_Import_DimStudent
 CMS_PerformanceDw_ETL_Import_FactSchoolEnrollment
 CMS_PerformanceDw_ETL_Import_FactStudentAssessment
 CMS_PerformanceDw_ETL_Import_FactStudentAssessment_ABCFeed
 CMS_PerformanceDw_ETL_Import_FactStudentAssessment_AYPFeed
 CMS_PerformanceDw_ETL_Import_FactStudentClassEnrollment
 CMS_PerformanceDw_ETL_Import_FactStudentDailyClassAttendance
 CMS_PerformanceDw_ETL_Import_FactStudentProgram

Sharepoint Applications:
4) Copy the folders from the Sharepoint directory to the QA server
Deploy Order Deployment Package Deployment Script to Run
1 stsadm.ajaxifymoss deploywithstsadmnocontenturls.bat
Additional Info: This package installs additional stsadm-commands that enables/disables
AJAX for the SharePoint web application.
Once this package is deployed, run the following command:
stsadm -o addajax35 -url <url of the web application>
example:
stsadm -o addajax35 -url http://moss.vdomain.cms.k12.nc.us/
Testing Open the web.config and ensure <system.webServer> is present n the web.config, other
chages are made to web.config by the package besides this adding this node.
2 CMS.MP____.ModifyWebConfigForDataLa deploywithstsadmnocontenturls.bat
yer
Feature Name: UpdateWebConfigForDataLayer
Feature Scope: Web
Description: This package has a feature with the Web application scope, the feature will
update the web.config to insert connection strings and update the assemblies section for
data layer access by the layout pages. Once the solution is deployed, go to the “web
application features” in the “Application Management” in the Central admin Admin and
activate the feature.
Testing To verify the feature has activated go to the web.config of the SharePoint web Application
and ensure the connection strings are present. Change the connection string appropriately
to point to the correct database server.
4 Activate Publishing Feature deploywithstsadmnocontenturls.bat

Implementation Activate Publishing feature (if not already activated) on the site collection that has the
Managing for Performance site.
To activate Publishing Feature, go to the ‘site collection features’(site actions->site

settings-> modify all site settings->site collection features) and find “Office SharePoint
Server Publishing Infrastructure” and activate it.
After this is activated at the site collection level, it must also be activated at the site level.
Go to the ‘site features’(site actions->site settings-> modify all site settings->site features)
and find “Office SharePoint Server Publishing” and activate it.
Testing Click ‘Site Settings’. If the dropdown has a final entry of ‘Manage Content and Structure’,
then the site has publishing enabled.

5 CMS.MP.DIGManagement deploywithstsadm.bat
This displays the layout pages.
Testing Goto the C:\Program Files\Common Files\Microsoft Shared\Web Server
Extensions\12\TEMPLATE\LAYOUTS\MP folder to find the staffauth.aspx page.
CMS.MP.CustomPeoplePicker deploywithstsadm.bat
Testing Check GAC (C:\Windows\Assembly) and ensure that CMS.MP.CustomPeoplePicker.dll is
present.
CMS.MP____.DataLayer deploywithstsadmnocontenturls.bat
Testing Check GAC (C:\Windows\Assembly) and ensure that CMS.MP____.DataLayer.dll is
present.
CMS.MP____.HelperMethods deploywithstsadmnocontenturls.bat
Testing Check GAC (C:\Windows\Assembly) and ensure that CMS.MP____.HelperMethods.dll is
present.
CMS.MP____.MyClassesWebPart______W deploywithstsadm.bat
ebPart
Implementation Activate Feature: In SharePoint, site actions->site settings-> modify all site settings, and
under ‘Site Administration’ select ‘Site Features’. Locate the ‘My Classes_____ Web Part’
feature and activate it.
Testing In SharePoint, site actions->site settings-> modify all site settings and under ‘Galleries’
select ‘Web Parts’. Ensure that
‘CMS.MP____.MyClassesWebPart_____WebPart.webpart’ is listed.
CMS.MP.MySIGsWebPart deploywithstsadm.bat
under ‘Site Administration’ select ‘Site Features’. Locate the ‘My Shared Instructional
Groups’ feature and activate it.
select ‘Web Parts’. Ensure that ‘CMS.MP.MySIGsWebPart.webpart’ is listed.
CMS.MP.StudentsInInstructionalGroupWe deploywithstsadm.bat
bPart

under ‘Site Collection Administration’ select ‘Site Collection Features’. Locate the
‘Students In Instructional Group’ feature and activate it.
select ‘Web Parts’. Ensure that ‘CMS.MP.StudentsInInstructionalGroupWebPart.webpart’
is listed.
CMS.MP____.MasterPageFiles deploywithstsadm.bat
Purpose This adds the required master pages, page layouts, css, and images to the Site Collection
for styling.
Implementation Deploy the solution using the deploy command.
In Site Collection features, activate the MP___IntranetMasterPages feature.
select ‘Master Pages and Page Layouts’. Ensure that ‘MP___Default.master’ &
‘MP___Default.aspx’ are listed.
CMS.MP____.SiteTemplates deploywithstsadmnocontenturls.bat
Purpose This adds the Site Template to the gallery for the Site Collection.
Implementation Deploy the solution using the deploy command.
In Site Collection features, activate the MP_____SiteTemplates feature.
select ‘Site Templates’. Ensure that ‘ST_TeacherPortal.stp is listed.
Run Code in the drop folder to provision the site
FileName CreateWeb.bat
Output ULS Logs
See screenshot below.
Testing In SharePoint, make sure the new site exists.
LOGS: Search for to check informational messages “MOSSFunctions”
Verify Setup
<Describe how the application installation should be verified. For example, describe a sequence of
actions that can be executed along with verifiable results or behaviors that will yield sufficient
confidence that the application has been setup properly.>

Uninstall Program
<Describe the uninstall program and anything special about using it or other measures needed to be
taken to uninstall the application(s)>
Deployment Toolsets and Templates/Samples

To be defined…
Appendix A. Deployment Change Request Form

General Information:
Requestor: Date of Req Type:
Request:
Application:
Databases:
Environment
:
Description: __________________________________________________________________________________________
Details:
Pr
Index Data
Req Data eci
Table/Stored Procedure Name Column Name/ Comments Defaults Load
Type Type sio * Req’d?
n
*If part of a composite index, list 1, 2, 3 ... based on order required; otherwise Y
Permissions:
Table / Stored Procedure User ID New Select Read Write Delete Execute
Authorization Requested Implementation

Date

Appendix B. Deployment Approach and Procedures

Unique to the Current Release (Sprint No. 5, 09/30/2009
Overview
CMS Managing for Performance Project Production Release Sprint #5 consists of the
following:
CMS K12 DataWarehouse Databases: The databases support the project
SSIS Packages
SSRS Reports
SharePoint Solutions
Database
Same as Standard
Middle tier
QA Server Name:
Web Server
QA Server Name:

Same as standards

Establish Load Default Create Users Grant Verify

Databases Data & Groups Permissions Databases
Same as standard

Same as standard

Same as standard
Same as standard
5) Verify Databases
Same as standard
Setting Up Security
<describe measures for setting up security, roles, etc.>
<Describe how to install the application(s)>
Verify Setup
<Describe how the application installation should be verified. For example, describe a
sequence of actions that can be executed along with verifiable results or behaviors that
will yield sufficient confidence that the application has been setup properly.>
Uninstall Program
<Describe the uninstall program and anything special about using it or other measures
needed to be taken to uninstall the application(s)>

Appendix C. Deployment Approach and

Procedures Unique to the Current Release
Sprint No. 6, 11/30/2009
Overview
CMS Managing for Performance Project Production Release Sprint #6 consists of the
following:
Updates to SSIS Packages
Updates to SSRS Reports
Base Teacher Portal
SharePoint Solutions
Database
QA DB Server Name:
QA Database Name:
QA DBO Account:
Production DB Server Name:
Production Database Name:
Production DBO Account:
Middle tier
QA Server Name:
Web Server
QA Server Name:



<Include this section if the application requires database preparation>
Establish C C L G V
Database R R O R E
E E A A R
A A D N I
T T T F
E E D Y
E P
U T F E S
S A A R E
E B U M T
R L L I U
S E T S P
S S
& , D I
A O
G T T N
R R A S
O I
U G
P G
S E
R
S
&
S
T
O
R
E
D
P
R
O
C
E
D
U
R
E
S
<List scripts or other measures required to create the database>

<List scripts or other measures required to create database users and groups>
3) Create Tables, Views, Triggers & Stored Procedures

<List scripts or other measures required to create tables, views, triggers & stored
procedures for the database>


<List scripts or other measures required to load any default data for the database>
<List scripts or other measures required for granting permissions to appropriate
users and groups for the database>
6) Verify Database
Tables Created
<list tables that were created above>

<List stored procedures that were created above>
Triggers Created
<List triggers that were created above>
Views Created
<List tables that were created above>
Prepare a series of tests to validate users, groups, permissions and default data were all
created properly.
As <user x> run following select statement to verify <describe user, permissions &
default data being tested and expected results>:
SELECT <column1{, column2, …column}>
FROM <table1{, table2, …tableN}>
WHERE <expression>
As <user y> run following select statement to verify <describe user, permissions &
default data being tested and expected results >:
WHERE <expression>

As <user …> run following select statement to verify <describe user, permissions &
default data being tested and expected results >:
WHERE <expression>
Setting Up Security
Ensure the CMS & Mariner Sharepoint Development teams have at least Visitor, or
Read permissions on the Base Teacher Portal.
In QA, when logged in as administrator, update the webpart property
SourceSystemStaffID to 36076 on the MyClasses webpart to test functionality of the My
Classes, My Shared Instructional Groups, and Students in Instructional Group webparts
on the Base Teacher Portal pages.
Verify Setup
Verify that the My Classes grid has data.
Click on a Class and verify that the Students in Instructional Group grid has data.
Create and manage a new instructional group.
Uninstall Program
Rollback to Production copy
Send log file to project team for diagnosis of application deployment failure.

Project Deployment Plan Template

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project Deployment Plan Template

Uploaded by

Copyright:

Available Formats

<Consultant logo> <Client logo>

<Client Org. Name>

<Project Name> Project

Charlotte-Mecklenburg Schools (CMS)

©2020 , ALL RIGHTS RESERVED.

9/22/09 Added Standard Deployment Pattie Hale

9/28/09 Modify Standard Deployment and Fendy Huang

10/1/09 Modify Sprint #5 Deployment Matthew

10/7/09 Added additional details Pattie Hale

11/19/09 Added Sharepoint information Cathy stadler

DEPLOYMENT PRINCIPLES AND POLICIES....................................................................................6

DEPLOYMENT APPROACH AND PROCEDURES COMMON TO ALL RELEASES..................7

DEPLOYMENT TOOLSETS AND TEMPLATES/SAMPLES..........................................................42

APPENDIX A. DEPLOYMENT APPROACH AND PROCEDURES UNIQUE TO THE

APPENDIX B. DEPLOYMENT APPROACH AND PROCEDURES UNIQUE TO THE

Purpose of this Document

Deployment Principles and Policies

Environments Supporting Best Practice Development and Deployment Processes

IIS Reporting IIS Reporting IIS Reporting

Standard development to deployment lifecycle

Emergency fix lifecycle

10/22/20 Page 7 <Client – Project>CMS-

Deployment Approach and Procedures Common to All

10/22/20 Page 8 <Client – Project>CMS-

4. QA is promoted to production only after a full week of stable testing on QA with NO

10/22/20 Page 9 <Client – Project>CMS-

10/22/20 Page 10 <Client – Project>CMS-

Figure 1: Physical Structure of Rollout Folder

10/22/20 Page 11 <Client – Project>CMS-

[ETL].[SSISConfigurations] table to point to the physical path of the DW

11. Production Rollout:

14. Rollout is archived and marked as successful.

10/22/20 Page 12 <Client – Project>CMS-

Production Database Name:

Production DBO Account:

Web Server <CMS Support Team to define>

10/22/20 Page 13 <Client – Project>CMS-

QA Virtual Directory Name:

Preparing the Database

Establish Load Default Create Users Grant Verify

2) Load Default Data

3) Create Users & Groups

10/22/20 Page 14 <Client – Project>CMS-

10/22/20 Page 15 <Client – Project>CMS-

10/22/20 Page 16 <Client – Project>CMS-

Stored Procedures Created

10/22/20 Page 17 <Client – Project>CMS-

10/22/20 Page 18 <Client – Project>CMS-

10/22/20 Page 19 <Client – Project>CMS-

Verify the following stored procedures were created:

10/22/20 Page 20 <Client – Project>CMS-

10/22/20 Page 21 <Client – Project>CMS-

Verify the following stored procedures were created:

Verify the following functions were created:

SELECT TOP 10 * FROM Import.fGenerateDimCommonProgramDataset()

10/22/20 Page 22 <Client – Project>CMS-

Stored Procedures Created

Verify the following stored procedures were created:

10/22/20 Page 23 <Client – Project>CMS-

10/22/20 Page 24 <Client – Project>CMS-

Verify the following stored procedures were created:

10/22/20 Page 25 <Client – Project>CMS-

10/22/20 Page 26 <Client – Project>CMS-