1. Windows Architecture for Oracle Users Saptak Sen Technical Evangelist, Windows Server Evangelism saptaks@microsoft.com

2. Agenda Synergies Windows Platform Database Architecture Oracle Failsafe Active Directory, Visual Studio Integration Summary

3. Commitment to Windows Oracle7 was the first database to ship on Windows in 1994 Windows Server is a base development platform for Oracle Windows Server is a Tier 1, fully supported platform for Oracle Focused Engineering and Product management groups for Windows-specific integration projects Supported both 32-bit and 64-bit Windows Server 2003 on day of O/S release

4. Partnering with Microsoft Oracle sponsors Microsoft events (PDC 2003, TechEd 2004, 2005) Microsoft sponsors Oracle events OracleWorld 2004, UKOUG Communication channels open at various levels in the organizations Joint support contacts for customer escalations How we jointly solve problems Conference calls, briefings, etc.

5. Oracle on Windows: Widely Deployed 29% of Oracle’s revenues are from Windows Growth of 8.4% on previous year 2004 Oracle Revenues by OS for new license sales Source: Gartner Research - May 2005 ID G00127787 Unix 49% Linux 20% Windows 29% Other 2% 8.4%

6. Available December 20, 2005 Source: Transaction Processing Council (TPC), http://www.tpc.org World Record TPC-H 1000 GB Benchmark Using an Bull NovaScale 5160 with 16 Intel Itanium 2 processors on 64-bit Windows 2003, Oracle Database 10 g Release 2 achieved 15,070 QphH@1000GBQphH@1000GB with a price-performance 44.33 US $ per QphH@1000GB.

7. Information Sources Oracle Web http://otn.oracle.com/windows Windows IT Pro http://www.windowsitpro.com/oracleonwindows Microsoft http://www.microsoft.com Search for ORACLE

8. Agenda Synergies Windows 64-bit Platform Database Architecture Oracle Failsafe Active Directory, Visual Studio Integration Summary

9. x64 Platform Opportunities Scalability Breadth of Applications 64-bit IPF Most Scalable Versatile Mainstream 64-bit x64 32-bit x86

10. Source Code Bases Windows now supports three architectures: x86, x64 and Itanium All binary versions of Windows for a given release are created from the same source base that follows cross-platform coding rules and is compiled to a specific instruction set Does not mean that each binary version has the same features A single binary version of Windows for x64 supports both AMD’s AMD64 and Intel’s EM64T architectures RTM Summer 2006 Released Mar, 2005 32-bit – Service Pack 1 for 2003 releases 64-bit – Service Pack 1 for 2003 releases and full releases of Windows Server 2003 (STD, ENT, DTC) x64 Editions and Windows XP Professional x64 Edition Windows Compute Cluster Server 2003 (X64) Windows Server 2003 SP 1 (x86, X64, Itanium) Windows XP Professional x64 Edition Windows Server 2003 Code Base

11. Memory and CPU Limits General Memory Limits32-bit64-bit Total Virtual Address Space 4 GB 16 TB Virtual Address Space per 32-bit process 2GB (3 GB if system is booted with /3gb switch) 4GB if compiled with /LARGEADDRESSAWARE 2GB otherwise Virtual Address Space per 64-bit process Not applicable8 TB Paged Pool 470 MB 128 GB Non-Paged Pool 256 MB 128 GB System Cache 1 GB 1 TB Physical Memory and CPU Limits 1 32-bit64-bit Windows Compute Cluster Server 2003 NA32 GB / 1-4 CPUs Windows Server 2003 Standard Edition 4 GB / 1-4 CPUs32 GB / 1-4 CPUs Windows Server 2003 Enterprise Edition 64 GB / 1-8 CPUs1 TB / 1-8 CPUs Windows Server 2003 Datacenter Edition 64 GB / 1-32 CPUs1 TB / 1-64 CPUs

12. Features Not Supported in any 64-bit Windows Product Subsystems Microsoft ® DOS 16-bit OS/2 subsystem Portable Operating System Interface for UNIX (POSIX)* Legacy Transport Protocols

13. 32-Bit Application Support 64-bit Windows supports 32-bit code via a 32-bit emulation component called Windows on Windows 64 (WOW64) Most 32-bit applications operate seamlessly Applications using 16-bit application installers 64-bit Windows does not run 16-bit code Detect many 16-bit installers and transparently instantiates 32-bit version Microsoft is working with existing installer vendors Applications that require 32-bit file system filter drivers or other kernel- mode drivers 64-bit Windows requires all such drivers to be 64-bit native Applications that explicitly install and require a 32-bit kernel-mode system Microsoft is working with application vendors

14. / LARGEADDRESSAWARE Switch available on all current MS linkers On 32-bit Windows, enables 3GB of VA for application (when booted /3GB) Same 32-bit app on Win64 gets full 4GB of user- mode VA, no /3GB necessary Default for 64-bit applications

15. x64 Server Options x64 hardware supports multiple configurations Extends hardware investment by allowing gradual migration to 64-bit computing Server Hardware Device Drivers Windows Servers Applications 32-bit Stack64-bit Stack Hybrid Stack x64 32-bit x64 32-bit x64

16. Microsoft ® Visual Studio ® 2005 Provides a 32-bit Integrated Development Environment (IDE) Installs on 32-bit and 64-bit versions of Windows Contains 64-bit tools and components such as the Microsoft ®.NET Framework and Common Language Runtime x64 and Itanium at parity in this release including: Visual Studio IDE for editing, building, and debugging 64- bit projects Microsoft ® C++ ® compilers targeting either x64 or Itanium (64-bit-hosted and cross-compilers) Managed code generation which can be agnostic, 32-bit only, or 64-bit only Support for MFC and ATL frameworks in 64bit environment Platform SDK

17. x64 Performance Improvements x64 removes x86 virtual address (VA) limitations As much as 170% improvement in system VA constrained scenarios like TS Currently 32% improvement in user VA constrained scenarios like SAP SD 2-tier Large memory aware applications benefit from 4GB of user VA space on x64 Additional registers and improved calling interface benefit many applications

18. Enterprise Workloads: TS Knowledge-worker W2K3 x64 supports 170% more users than W2K3 x86 Improvements x64 removes x86 VA limitations x64 runs 32-bit user-mode apps at full speed Locking improvements Registry improvements Scheduling and timer handling improvements Memory management improvements

19. Enterprise Workloads: SAP SD 2-tier user, W2K3 x64 32% more users W2K3 x86 on Single Core (SC) Opteron 74% more users on Dual Core (DC) compared to SC Improvements Memory management improvements (all architectures) WinSock improvements for better and more reliable connections SAP improvements 64 bit versions avoid map/un-map operations on every transaction Source:http://www50.sap.com/benchmarkdata/sd2tier.asp as of May 20, 2005

20. Enterprise Workloads: TPC-C Improvements W2K3 SP1 ADS supports 64gb vs. 32gb on W2K3 Storport and overall I/O improvements Disk driver performance affects overall x64 performance ±5% Windows Server 2003 x64 x64 provides 4gb user virtual address space for large memory aware 32-bit applications Native x64 allows “flat memory model” removing need for AWE map and un- map Source: http://www.tpc.org as of May 20, 2005http://www.tpc.org

21. File Server: NetBench Peak Throughput W2K3 sp1 x86: 12% higher than RTM Improvements Avoid split-writes Stable storage flag Increased VA does not help NetBench workload because it has a small working set Configuration HP DL 585 4P 2.4GHz AMD64 Single Core 8GB RAM

22. Web Server: Hosting Site capacity W2K3 sp1 x86 can host 25% more sites than W2K3 with 16 GB RAM W2K3 x64 can host more sites than W2K3 sp1 x86 20k site startup time W2K3 = 39.5 seconds W2K3 sp1 x86 = 9.5 seconds W2K3 sp1 x64 = 9.5 seconds Improvements Reduced metabase accesses and optimized lookups improved startup Utilization of workstation GC heap improved capacity. Configuration 4p AMD Opteron 2.4 GHz Single Core 16 GB RAM 32 bit, 32 GB RAM 64 bit

23. Web Server: HTTP.SYS Kernel-mode support for SSL 50% better SSL performance on SPECweb99ssl Latency improvements in HTTP.SYS Avoid delayed-ack or WAN latency impact on worker processes Centralized W3C logging Provides most of the performance benefits of centralized binary logging with text output Greater connection capacity Lower per connection memory usage Smarter throttling (triggered by NPP usage rather than pre- set limit)

24. Networking: Connection Scalability Sustained Connections W2K3 SP1 x64 has 2 times the capacity of x86 (with 2GB RAM) Capacity should now scale with CPU/physical memory Improvements x86 VA limitations removed Configuration HP DL145 2P 1.8GHz AMD64 Single Core 2GB RAM

25. Networking Improvements Algorithm and data structure changes for W2K3 sp1 Connection management improvements for internet-facing servers 50% reduction in CPU usage for MSN servers Syn-attack detection improvements 50% reduction in syn-attack detection overhead WinSock improvements for SAP poll() and select() improvements Internet2 Land Speed Record (multi-stream) on 64-bit Windows AMD64 sender, IA64 receiver 7.1 Gbps sent from Caltech to CERN (Geneva)

26. Server Performance Summary Improvements Terminal Server KW: 170% more users on x64 compared to x86 SAP SD 2-tier: 32% more users on x64 compared to x86 TPC-C: 6.5% higher throughput on x64 compared to x86 NetBench: 12% W2K3 to W2K3 sp1 x86 Hosting Capacity: 88% W2K3 to W2K3 sp1 x86 LCW: 10% W2K3 to sp1 x86 +.NET sp1 SSL: 50% better SPECweb99ssl Connection scalability: 2x from x86 to x64 Reduced impact of firewall, latency Diagnostics improvements

27. Agenda Synergies Windows 64-bit Platform Database Architecture Oracle Failsafe Active Directory, Visual Studio Integration Summary

28. Database Architecture Thread model, not a port of Oracle’s process architecture Oracle.exe, 1 process many threads 3GB (32-bit) or 8TB (64-bit) maximum memory per database instance. VLM support allows >3GB on 32-bit.

29. 32-bit: VLM Support SGA Code Windows Server 2003 Memory Limits (32-bit) Standard Edition: 4GB Enterprise Edition: 32GB Datacenter Edition: 64GB database threads/ memory 3GB with AWE 16GB rest of RAM For O/S, other apps For Kernel 1GB

30. 32-bit: VLM Support SGA minus db buffers SGA Code rest of RAM For O/S, other apps 3GB with AWE 16GB Window on db buffers in AWE mem Extended memory available for db buffers via AWE calls Memory from AWE calls used for db buffers only. The amount of AWE memory allocated equals db_block_size times db_block_buffers. Oracle operating system process. Normally limited to 3GB of address space. With VLM, Oracle can get up to 64GB of database buffers. For Kernel 1GB

31. 64-bit Interoperability between 32-bit clients and 64-bit servers and vice versa Improved performance, availability and scalability Timeline 10.1.0.4 available NOW 32-bit to 64-bit upgrade process is simple 32-bit data files are compatible with 64-bit DB No need to recreate the database Full export and import not required Database Upgrade Assistant automates process Transparent migration for end-user applications No changes required to existing client applications when running against 64-bit database

32. Database Architecture File I/O Oracle10g supports asynchronous I/O to all types of files Logical and physical raw files and partitions are fully supported (faster than NTFS) Full 64-bit file I/O internally Maximum file size is 64GB Maximum database size is 4 petabytes

33. Database Architecture Developed for Windows Integration with Performance Monitor Integration with Event Log Integrated with Windows Services 10TB database in production Unlimited scalability on 64-bit

34. New for Oracle10g User-thread support An extension of the thread support already in place since Oracle7. Run the database in user-thread mode, which employs Oracle-scheduled user-mode threads (or fibers) instead of O/S-scheduled threads. For CPU intensive apps, this will provide a performance boost and reduce CPU utilization.

35. New for Windows Server 2003 Large Page support For instances with large memory requirements, large page support can improve performance. NUMA support for memory/scheduling Database intelligently allocates memory and schedules threads based on node configuration

36. Oracle on Windows All development Tools in place ODP Drivers 10.1.0.4 ODP.Net driver available Oracle Developer Tools for Visual Studio.NET Oracle Explorer Designers and Wizards Automatic Code Generation PL/SQL Editor Beta Support for.Net Language Stored Procedures Stored Procedure Testing Oracle Data Window SQL Query Window Integrated Help System

37. Cross-platform Security Integration (Kerberos) With the Oracle Advanced Security Option, cross- platform Kerberos support is enabled A Windows client can connect to a non-Windows server securely Integrated with Microsoft Key Distribution Center (MSKDC)

38. Active Directory Integration Database registration and name resolution Store and resolve connect descriptors through AD Eliminate tnsnames.ora on clients Centralize configuration, reduce administration Enhanced tools support for storing connect descriptors Windows Explorer, AD Users and Computers Oracle DB Configuration Assistant, Net Manager, Net Configuration Assistant

39. Database Name Resolution Microsoft AD Windows Environment 2 - User specifies AD-stored connect string 4- Connection to database is established 3 - Connect string is resolved from ADS via Oracle Net Oracle 10g 1 – Admin uses Oracle Net Manager or DBCA to populate AD connect string data

40. Single Sign-on Support (client/server) Windows Native Authentication adapter provides: O/S authentication for database users Database lookup of O/S-enabled roles Authentication done via Kerberos With the purchase of the Advanced Security Option, single sign-on can be done over SSL as well Integrated with Microsoft Certificate Store (MCS) for X.509 certificates

41. Single Sign-on Support (three-tier) Oracle’s mid-tier Single Sign-On server (SSO) is also integrated with Windows and Active Directory Allows single sign-on support via Web browser credentials Windows Authentication Plug-in allows interoperability between Oracle iAS (application server) and AD

42. User Sign-On to Oracle Oracle Portal Delegated Administration Console Oracle E-Business Suite Release 11i Oracle Internet Directory Oracle10g Single Sign-On Microsoft Active Directory Windows Environment 1- User attempts to sign on 2- Oracle Authentication 3- User identity confirmed 4- Authentication via Windows Plug-in

43. Agenda Synergies Database Architecture Systems Management Oracle Failsafe Summary

44. Oracle Fail Safe High Availability for solutions deployed on Windows clusters Supports Windows Server 2003 (and Windows 2000 Server and Windows NT Server) clusters Support for Oracle Database, iAS, E-Business Suite 11i, Forms 6i, and Reports 6i Provides fast fail over, high availability Supports up to 8 nodes on Windows Server 2003 Integrates with MSCS for resource failover

45. Conclusion Oracle has been committed to Windows Server since its inception Oracle is strongly integrated with the Windows Server Platform Oracle is a top performing DBMS on Windows Server Oracle is available on all Windows Server implementations (all editions, 32-bit, 64-bit Itanium, & this year 64-bit AMD/EM64T)