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

More documents

Recommendations

Info

84Developing: Databases — <strong>Migrating</strong> SchemasMigrator, which specializes in the migration of the <strong>Oracle</strong> schema to SQL Server. TheSSMA also provides the SQL Converter tool, which converts SQL code found in <strong>Oracle</strong>objects (such as stored procedures) to their T-SQL equivalents. The SSMA tool suite canbe downloaded from http://www.microsoft.com/sql/migration. The beta version of SSMAis available as of the date of publishing this solution. Version 1.0 of SSMA is slated to beavailable in June 2005.Most tools that are employed in the administration of <strong>Oracle</strong> databases are capable ofextracting object definitions. Toad and SQL Navigator from Quest, PL/SQL Developerfrom Allround Automations, Unicenter SQL-Station from Computer Associates, RapidSQL from Embarcedero, and <strong>Oracle</strong> Enterprise Manager from <strong>Oracle</strong> are examples ofsuch tools.Modeling tools such as AllFusion (Erwin) from Computer Associates and ER/Studio fromEmbarcadero can also be employed to reverse engineer the <strong>Oracle</strong> database.The goal of this chapter is to show how an <strong>Oracle</strong> schema and its objects should bemigrated to SQL Server. Scripts should be used <strong>for</strong> per<strong>for</strong>ming most of the tasks in thisstep, because scripts make the migration easier to execute compared to the use of GUItools.Scripting Migrated Schema ObjectsThe development process is built on the requirement that when the development iscomplete, the code will be in place <strong>for</strong> unit testing and implementation. These scripts willallow recreation of the objects in a reliable manner when creating the database in theStabilizing Phase and the Deploying Phase. There are some basic rules that should befollowed when scripting the database <strong>for</strong> promotion to a staging environment <strong>for</strong> unittesting:● Script everything● Provide support documentation● Protect the scriptsEach of these basic rules is discussed under the following headings.Script EverythingScript everything associated with the database implementation. The Generate SQL Scriptfeature of SQL Server Enterprise Manager can be used to script each database object inthe migrated database. After the scripts are created, conduct a validation process toverify that the number of objects scripted is the same as the number of objects that existin the development database. This process is very important because it helps to ensurethat the database being promoted to the staging environment is identical to the databasein the development environment.Provide Support DocumentationProvide support documentation <strong>for</strong> each script. Comment the code to describe what ishappening in the script and include any observations gathered when it was last executed,such as how long execution took and how many rows were affected.Protect the ScriptsProtecting the scripts is very important <strong>for</strong> the database implementation. Treat the scriptslike production objects at this point. To ensure that the appropriate scripts are used whenthe database is promoted between development, staging, and production environments,
<strong>Solution</strong> <strong>Guide</strong> <strong>for</strong> <strong>Migrating</strong> <strong>Oracle</strong> on UNIX to SQL Server on Windows 85keep the scripts in a secured directory or under version control. Versioning is veryimportant because an <strong>Oracle</strong> to SQL Server migration is not a mere mapping of objectsfrom one database to another. The differences between <strong>Oracle</strong> and SQL Server willrequire that some of the SQL statements be rewritten <strong>for</strong> the new environment. Thesechanges in SQL will also prompt changes to the database objects and their design.These changes will be driven by the application development (migration) process and notfrom within the database migration process described here. Only the development anddeployment teams should have access to the scripts.Migrate the SchemaThis section discusses the necessary steps in migrating the schema owner and settingup the storage in preparation <strong>for</strong> migrating the schema objects and its data.The high-level steps <strong>for</strong> migrating the storage architecture of a schema are:1. Map the storage architecture.2. Create a database <strong>for</strong> the schema.3. Create filegroups <strong>for</strong> the tablespaces.4. Add datafiles to filegroups.Each of these four high-level steps is discussed in detail under the followingsubheadings.Map the Storage ArchitectureThe first step in migrating an <strong>Oracle</strong> schema is to understand the storage architectureand how these architectural components will map to their equivalents in SQL Server.In<strong>for</strong>mation on the various characteristics of the tablespaces and datafiles in which the<strong>Oracle</strong> schema is stored has to be gathered.There are several tools, both from <strong>Oracle</strong> as well as third parties, which are used inadministering <strong>Oracle</strong> databases. Any of these tools can be employed to gatherin<strong>for</strong>mation on the tablespaces and datafiles. In the example migration that is provided atthe end of this section, methods <strong>for</strong> capturing the requisite data purely using SQL areprovided.
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 89: Solution G
Page 92 and 93: 72Developing: Databases — <strong
Page 120 and 121: 100 Developing: Databases — <stro
Page 154 and 155:
134 Developing: Databases — <stro
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:
Page 284 and 285:
Page 286 and 287:
Page 289 and 290:
Solution G
Page 291 and 292:
Solution G
Page 293 and 294:
Solution G
Page 295 and 296:
Solution G
Page 297:
Solution G
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
Page 306 and 307:
Page 308 and 309:
Page 310 and 311:
Page 312 and 313:
Page 314 and 315:
Page 316 and 317:
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 330 and 331:
310 Stabilizing Phasechanges made t
Page 333 and 334:
Solution G
Page 335 and 336:
Solution G
Page 337 and 338:
Solution G
Page 339 and 340:
Solution G
Page 341 and 342:
Solution G
Page 343 and 344:
Solution G
Page 345:
Solution G
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?