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

More documents

Recommendations

Info

102 Developing: Databases — <strong>Migrating</strong> SchemasCreate the Schema ObjectsThis section discusses the migration of the schema objects from <strong>Oracle</strong> to SQL Server.The following is a complete list of objects that are classified by <strong>Oracle</strong> as schema objects:●●●●●●●●●●●●●●●●TablesClustersObject TablesIndex-organized TablesConstraintsTriggersIndexesViewsObject ViewsFunctionsStored ProceduresPackagesSynonymsSequencesDatabase LinksObject TypesTable 6.2 provides a high-level view of how the <strong>Oracle</strong> schema objects map toSQL Server.Table 6.2: SQL Server Objects that Replace <strong>Oracle</strong> Schema Objects<strong>Oracle</strong>TableClusterObject TableIndex-organized TableConstraintsTriggersIndexViewObject ViewSynonymSequenceDatabase LinkObject TypesProcedureFunctionPackageSQL ServerTableTableClusterTable (with clustered index)ConstraintsTriggersIndexViewN/AViewIdentityLinked ServerN/AStored ProcedureFunctionStored Procedure
<strong>Solution</strong> <strong>Guide</strong> <strong>for</strong> <strong>Migrating</strong> <strong>Oracle</strong> on UNIX to SQL Server on Windows 103Some of these objects fall under broader classifications, such as tables and views. Whilethe discussion of some of the objects is beyond the scope of this guide, the following arecovered in this chapter:● Tables● Comments● Constraints● Triggers● Views● Indexes● Stored Programs, including functions, stored procedures, and packages● Objects not found in SQL Server, including sequences, synonyms, and databaselinksThe data definition language (DDL) <strong>for</strong> defining objects is in accord with ANSI SQLstandards. Because both <strong>Oracle</strong> and SQL Server maintain compliance with SQL-92 andSQL-99 standards, the syntax <strong>for</strong> defining objects is very similar.Identifiers and Naming<strong>Oracle</strong> object and column names are generally not case-sensitive. However, noassumptions should be made because they can be <strong>for</strong>ced to be case sensitive bydelimiting them (enclosing them) in double quotation marks (“). For example, the nameTRANSACTION_DATE can be made case sensitive by using “Transaction_Date”. Also,quotes can be used to create irregular identifiers such as “Transaction Date” (with a blankspace). Similarly, object and column names in SQL Server are not case-sensitive bydefault, but this default behavior can be changed by modifying configuration settings.Nonstandard or delimited identifiers can be created just as in <strong>Oracle</strong> using eitherquotation marks (“) or brackets ([ ]). Read the "Using Identifiers" section in SQL ServerBooks Online <strong>for</strong> rules about the construction and use of regular and delimited identifiers.<strong>Oracle</strong> table and column names are stored in data dictionary tables as uppercase stringsunless <strong>for</strong>ced to be case sensitive using delimiters. In contrast, the default SQL Serverbehavior is to store them in the case used when they were created. Because scripts <strong>for</strong>use with <strong>Oracle</strong> are written with such expectations, it is recommended you useuppercase identifiers while creating the objects in SQL Server (without <strong>for</strong>cing case byusing delimiters).Qualifiers and Name ResolutionThe names of objects are influenced by uniqueness requirements. <strong>Oracle</strong> object nameshave to be unique <strong>for</strong> a schema. In SQL Server, the same owner can own objects of thesame name in two different databases, that is, the combination of owner.table_nameneeds to be unique only within a database. Hence objects are qualified in <strong>Oracle</strong> as[schema.]object_namewhereas in SQL Server the complete qualifier is[database.]owner.]object_nameRules have been established in both <strong>Oracle</strong> and SQL Server <strong>for</strong> resolving anobject_name that is not qualified.In <strong>Oracle</strong>, the resolution is governed by synonyms and the concept of namespaces.Tables, views, snapshots, sequences, synonyms, procedures, functions, and packagesare in a single namespace. Triggers, indexes, and clusters each have their own individual
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 89: Solution G
Page 92 and 93: 72Developing: Databases — <strong
Page 120 and 121: 100 Developing: Databases — <stro
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?