The document compares Oracle and SQL Server across several categories including performance, high availability, and new features in Oracle 11g. Key differences summarized are: - Oracle supports real application clusters for high availability while SQL Server 2000/2005 do not support this type of clustering. - Oracle Data Guard provides disaster recovery capabilities while SQL Server Database Mirroring has similar goals but differences in capabilities. - New features in Oracle 11g include database replay, SQL performance analyzer, transparent tablespace encryption, flashback data archive, and SQL plan management.

1. ORACLE & SQL Server Comparison

3. Performance

4. Information Integration

5. High Availability

6. Automatic Storage Management

8. Concurrency Model

9. Indexing

10. Partitioning

11. Parallel Execution

15. Indexing(Cont….)

18. The differences in parallel execution

19. Oracle will execute INSERT, UPDATE, DELETE, and MERGE statements in parallel

23. Federation

24. Replication

26. Homogeneous Federation

27. Supported by both by different manner

30. Messaging Queuing (Cont)

32. Unplanned Downtime

33. System Failures

34. Data Failures

35. Disaster Recovery

36. Human Errors

37. Planned Downtime (Maintenance)

38. System Changes

41. Database Replay

42. SQL Performance Analyzer

43. Partitioning

44. Transparent Tablespace Encryption

45. Flashback Data Archive

46. SQL Plan Management

47. Private Statistics

48. More Concurrency

50. Disaster Recovery(Cont)

52. Features & CapabilitiesASM Diskgroup Mirroring Striping Striping Failgroup1 Failgroup2

53. Files, Extents, and Failure Groups Files and extent pointers Fail groups and ASM mirroring

55. ASM and Oracle Managed Files

56. ASM Database

57. ASM Components

58. Disk Group Redundancy

59. Performance

61. ASM extends the power of Oracle Managed Files

62. Creates and manages Files automatically

63. Understands different Oracle file types

64. Offers built-in data mirroring and striping Capabilities

65. Automatically balances I/O load across disk group(s)

67. When ASM is enabled, Oracle automatically creates a small database for storing ASM-related meta-data

68. The default database name is “+ASM”

69. The default RAC instances are “+ASMn”, where n is the node number

70. The ASM database may be managed with srvctl commands

72. Disk Groups

73. Oracle may provide disk mirroring (optional)

74. Oracle will stripe files across all available disks

75. Using ASM striping across a group of hardware striped LUNs can be beneficial to performance

76. Disks assigned to ASM Disk groups become ASM Disks

77. Files written on ASM disks become ASM files

78. Files are named with an Oracle-defined format

79. File name aliases may be defined for convenience

82. ASM Disk Groups may be defined with different levels of redundancy

83. NORMAL redundancy indicates that Oracle will create a software mirror for each disk

84. HIGH redundancy indicates that Oracle will create two mirror disks per data disk

85. Disk mirrors may be segregated into different locations by designating Failure Groups

86. EXTERNAL redundancy indicates that Oracle will not create any software mirrors. Hardware mirrors (if any) will be used instead

88. ASM performance is sensitive to the number of disk spindles utilized

89. Just like traditional storage, the number of IOs/second that can be sustained is directly proportional to the number of disks in the disk group

90. Always use External Redundancy if you are using RAID-capable storage hardware

91. Multiple RAID 1 disks can be utilized in a Disk Group

92. ASM will provide the disk striping

93. Another option is to use multiple four disk RAID 10 groups as the building block for ASM Disk Groups

95. ACMCMD

96. SQLPLUS

98. Takes your data and automatically puts it elsewhere

99. Makes it available for Failover in case of failure.

100. The other capabilities are pure bonus.

101. Switchover for Maintenance

102. Reporting

103. Off-loading Queries

106. Data Guard comprises of two parts

107. REDO APPLY (DR)

108. Maintains a physical, block for block copy of the Production (also called Primary) database.

109. SQL APPLY (Reporting)

111. Uses the database recovery functionality to apply changes

112. Can be opened in read-only mode for reporting/queries

113. Can also perform backup, offloading production database

115. Contains the same logical information (rows) as the production database

116. Physical organization and structure can be very different

117. Can host multiple schemas

118. Can be queried for reports while logs are being applied via SQL

119. Can create additional indexes and materialized views for better query performance

122. The application of changes received from the primary can be delayed at standby to allow for the detection of user errors and prevent standby to be affected

124. Database Replay

125. SQL Performance Analyzer

126. Partitioning

127. Transparent Tablespace Encryption

128. Flashback Data Archive

129. SQL Plan Management

130. Private Statistics

131. More Concurrency

134. Database Patch Installation

135. RAC related changes(adding nodes, interconnect changes, …)

136. OS platform changes and upgrades

138. SQL Performance Analyzer EM Support:

140. Supported Encryption Algorithm

141. 3DES168

142. AES128

143. AES192

145. Supported Encryption Algorithm

146. 3DES168

147. AES128

148. AES192

151. Create flashback archive far1 tablespace ts_far1 quota 1g retention 1 year;

152. Alter table test flashback archive far1;

153. By adding table test to flashback archive, whenever the table is changed, the past image will be stored in the flash recovery area.

154. Flashback Data Archive advantage over triggers:

155. The process done by oracle software code and oracle internal process it self. So there is no trigger related performance impact , no context-switching or checking for dependencies.

157. To enable this feature we should set below parameter to TRUE:

159. In Oracle Database 11g there are two major enhancement to improve concurrencies like these:

160. You can add a column to the table event when another transaction holds row locks on the table

161. You can instruct the session to executing the DDL to wait for some specified time in seconds.

163. To use of this feature:

164. Set the result_cache_max_size SQLQuery Result Cache SELECT … SELECT … Session 1 Session 2

165. SQL Server Migration To Oracle: An Oracle database provides you with better scalability, reliability, increasedperformance, and better security than other third-party databases. For this reason,organizations migrate from their current database, such as Microsoft SQL Serverand Microsoft Access, to an Oracle database.