Solution Guide for Migrating Oracle on UNIX to SQL Server - Willy .Net

More documents

Recommendations

Info

310 Stabilizing Phasechanges made to these documents during the pilot have to be noted and thedocumentation updated accordingly.Note Ultimately, the pilot leads to a decision to either proceed with a full deploymentor to delay deployment so that issues can be resolved.Evaluating the PilotAt the end of the pilot, its success is evaluated to determine whether deployment shouldbegin. The project team then needs to decide whether to continue the project beyond thepilot.It is important to obtain in<strong>for</strong>mation about both the design process and the deploymentprocess. Review what worked and what did not work so that it is possible to revise andrefine the plan be<strong>for</strong>e deployment. Examples of in<strong>for</strong>mation to be gathered include:● Training required <strong>for</strong> using the solution● Rollout process● Support required <strong>for</strong> the solution● Communications● Problems encountered● Suggestions <strong>for</strong> improvementsThe feedback is used to validate that the delivered design meets the design specification,and the business requirements. After the data is evaluated, the team must make adecision. The team can select one of following strategies:● Stagger <strong>for</strong>ward. Prepare another release candidate and release it to the originalpilot group, then to additional groups. The release to more than one group mighthave been part of the original plan or might have been a contingency triggered byan unacceptable first pilot.● Roll back. Return the pilot group to their pre-pilot state.● Suspend the pilot. Put the solution on hold or cancel it.● Patch and continue. Fix the build that the pilot is running and continue.● Proceed to the Deploying Phase. Move <strong>for</strong>ward to deploy the pilot build to the fulllive production environment.Finalizing the ReleaseThe Stabilizing Phase culminates in the Release Readiness Approved Milestone. Thismilestone occurs when the team has addressed all outstanding issues and has releasedthe solution and made it available <strong>for</strong> full deployment. This milestone is the opportunity<strong>for</strong> customers and users, operations and support personnel, and key project stakeholdersto evaluate the solution and identify any remaining issues they need to address be<strong>for</strong>ebeginning the transition to deployment and, ultimately, release.After all of the stabilization tasks are complete, the team must <strong>for</strong>mally agree that theproject has reached the milestone of release readiness. As the team progresses from therelease milestone to the next phase of deploying, responsibility <strong>for</strong> on-going managementand support of the solution officially transfers from the project team to the operations andsupport teams. By agreeing, team members signify that they are satisfied with the workthat is per<strong>for</strong>med in their areas of responsibility.
<strong>Solution</strong> <strong>Guide</strong> <strong>for</strong> <strong>Migrating</strong> <strong>Oracle</strong> on UNIX to SQL Server on Windows 311Project teams usually mark the completion of a milestone with a <strong>for</strong>mal sign-off. Keystakeholders, typically representatives of each team role and any important customerrepresentatives who are not on the project team, signal their approval of the milestone bysigning or initialing a document stating that the milestone is complete. The sign-offdocument becomesa project deliverable and is archived <strong>for</strong> future reference.
Page 1:
Solution G
Page 5 and 6:
ContentsvDeveloping: Databases —
Page 7:
ContentsviiIntroduction and Goals..
Page 11 and 12:
Solution G
Page 13 and 14:
Solution G
Page 15 and 16:
Solution G
Page 17 and 18:
Solution G
Page 19:
Solution G
Page 22 and 23:
2Introduction to the Microsoft <str
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
10Introduction to the Microsoft <st
Page 32 and 33:
12Introduction to the Microsoft <st
Page 34 and 35:
14Envisioning PhaseTable 2.1: Major
Page 36 and 37:
16Envisioning PhaseMaximize ROITCO
Page 38 and 39:
18Envisioning Phase●●http://msd
Page 40 and 41:
20Envisioning Phase●●●If ther
Page 42 and 43:
22Envisioning PhaseFigure 2.1 repre
Page 44 and 45:
24Envisioning Phase●Database Conn
Page 46 and 47:
26Envisioning PhaseOracle</
Page 48 and 49:
28Envisioning Phase●●●It is d
Page 50 and 51:
30Envisioning PhaseOptimal Strategy
Page 52 and 53:
32Envisioning PhaseRole Project res
Page 54 and 55:
34Envisioning Phase●●●●●C
Page 56 and 57:
36Envisioning PhaseConfiguration Ma
Page 59 and 60:
Solution G
Page 61 and 62:
Solution G
Page 63 and 64:
Solution G
Page 65 and 66:
Solution G
Page 67 and 68:
Solution G
Page 69 and 70:
Solution G
Page 71 and 72:
Solution G
Page 73 and 74:
Solution G
Page 75 and 76:
Solution G
Page 77 and 78:
Solution G
Page 79 and 80:
Solution G
Page 81 and 82:
Solution G
Page 83 and 84:
Solution G
Page 85 and 86:
Solution G
Page 87 and 88:
Solution G
Page 89:
Solution G
Page 92 and 93:
72Developing: Databases — <strong
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
100 Developing: Databases — <stro
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 173 and 174:
Solution G
Page 175 and 176:
Solution G
Page 177 and 178:
Solution G
Page 179 and 180:
Solution G
Page 181 and 182:
Solution G
Page 183 and 184:
Solution G
Page 185 and 186:
Solution G
Page 187 and 188:
Solution G
Page 189 and 190:
Solution G
Page 191:
Solution G
Page 194 and 195:
174 Developing: Applications — In
Page 196 and 197:
176 Developing: Applications — In
Page 198 and 199:
178 Developing: Applications — <s
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 243 and 244:
Solution G
Page 245 and 246:
Solution G
Page 247 and 248:
Solution G
Page 249 and 250:
Solution G
Page 251 and 252:
Solution G
Page 253 and 254:
Solution G
Page 255:
Solution G
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 275 and 276:
Solution G
Page 277 and 278:
Solution G
Page 279: Solution G
Page 282 and 283: 262 Developing: Applications — <s
Page 289 and 290: Solution G
Page 318 and 319: 298 Stabilizing PhaseTestingThe Sta
Page 320 and 321: 300 Stabilizing Phaseindividual com
Page 322 and 323: 302 Stabilizing PhasePerfor
Page 324 and 325: 304 Stabilizing PhaseFor example, w
Page 326 and 327: 306 Stabilizing PhaseFigure 18.1Bug
Page 328 and 329: 308 Stabilizing PhaseUser Acceptanc
Page 348 and 349: 328 OperationsWindows Environment O
Page 350 and 351: 330 OperationsSecurityFor detailed
Page 352 and 353: 332 AppendicesOracle</stron
Page 354 and 355: 334 AppendicesFigure A.2Ora
Page 356 and 357: 336 AppendicesIn SQL Server, the te
Page 358 and 359: 338 AppendicesProcess/Thread Archit
Page 360 and 361: 340 AppendicesTransaction Architect
Page 362 and 363: 342 AppendicesData DictionaryThe da
Page 364 and 365: 344 Appendices●●●Using the BU
Page 366 and 367: 346 AppendicesAvailabilityAvailabil
Page 368 and 369: 348 AppendicesThe perfor</s
Page 370 and 371: 350 AppendicesInfor</strong
Page 372 and 373: 352 AppendicesQuery AnalyzerT he SQ
Page 374 and 375: 354 AppendicesTable A.5: Network An
Page 376 and 377: 356 AppendicesPerfor</stron
Page 378 and 379: 358 AppendicesAppendix D: Installin
Page 380 and 381:
360 Appendices7. Type the following
Page 382:
362 AppendicesAppendix E: Reference
show all

Solution Guide for Migrating Oracle on UNIX to SQL Server - Willy .Net

Create successful ePaper yourself

Delete template?

Save as template?