1. MISSION CRITICAL COMPUTING SQL Server Special Considerations

2. MISSION CRITICAL COMPUTING Overview SQL Server High Availability Unicode

3. MISSION CRITICAL COMPUTING Lesson: SQL Server High Availability Designing for High Availability (HA) Where to Start? OS options for SQL Server SQL Server High Availability Windows Clustering Terminology Cluster Resource Dependencies Troubleshooting SQL Server HA information

4. MISSION CRITICAL COMPUTING Designing for High Availability (HA) HA is about people and processes – technology is just the enabler Understand the level of HA expected so you can focus  99.999%5 minutes per year98%7.3 days per year  99.99%53 minutes per year97%11 days per year  99.9%8.8 hours per year95%18.3 days per year  99%3.6 days per year90%36.5 days per year Identify risks and exposures, and understand tradeoffs Review all single points of failure Redundancy is crucial, but don’t forget plans for contingency/disasters

5. MISSION CRITICAL COMPUTING Where to Start? What is the level of HA expected? Configure enough processing power to handle the workload after a failover. Use compatible hardware. Entire cluster solution must be in the Windows Catalog or on the former Hardware Compatibility List (HCL). Use only certified drivers. Crucial for disk devices Use the right version of the OS Use the right version of SQL Server Goal is to have a supported and known configuration Check for best practices. Look for White Papers on networking, configuration, etc.

6. MISSION CRITICAL COMPUTING OS options for SQL Server Windows 2000 Advanced Server  Max 8 Processors  Max 8 Gb Memory Windows 2000 Datacenter Server  Max 32 Processors  Max 32 Gb Memory Windows Server 2003 Enterprise Edition  Max 8 Processors  Max 32 Gb Memory (32-bit) or Max 64 Gb Memory (64-bit) Windows Server 2003 Datacenter Edition  Min 8 Processors and Max 64 Processors  Max 64 Gb Memory (32-bit) or Max 512 Gb Memory (64-bit)

7. MISSION CRITICAL COMPUTING SQL Server High Availability Failover clustering  Automatic  Great for close distances Log Shipping  Manual/Scheduled  OK for some levels of HA.  Great for disaster recovery or spanning distances Native SQL Server Replication  Not an option unless applying schema changes outside of Siebel Tools Backup and Restore  Always test your backups!  Coordinate with backup/restore of Siebel File System

8. MISSION CRITICAL COMPUTING Windows Clustering Terminology SQL Server 2000 availability clustering built on top of Windows Clustering. Failover Clustering Windows OS server cluster. Not for scale out. Windows Clustering SQL Server 2000 scale out. Federated Server/Cluster (formerly referred to as Active/Passive ) Only one SQL Server virtual server concurrently running. Single Instance Cluster (formerly referred to as Active/Active ) Up to 16 SQL Server virtual servers per virtual cluster. Multiple Instance Cluster

9. MISSION CRITICAL COMPUTING Cluster Resource Dependencies SQL Server resources in a Cluster are dependent on other resources to run Resources start in a particular order based on defined dependencies Unless absolutely necessary, do not add resources as dependencies to the SQL Server resources. May cause an outage that has no relation to SQL Server

10. MISSION CRITICAL COMPUTING Troubleshooting Diagnose in this order every time: 1.Hardware issues 2.OS issues 3.Networking issues 4.Security issues 5.Windows Server cluster issues 6.SQL Server issues Most problems are not related to SQL Server

11. MISSION CRITICAL COMPUTING SQL Server HA information SQL Server 2000 High Availability  754 pages.  Published by Microsoft Press. SQL Server 2000 Failover Clustering. http://www.microsoft.com/technet/prodtechnol/sql/2000/ maintain/failclus.mspx http://www.microsoft.com/technet/prodtechnol/sql/2000/ maintain/failclus.mspx Cluster Services in Windows Server 2003. http://www.microsoft.com/technet/prodtechnol/windowss erver2003/technologies/clustering/default.mspx http://www.microsoft.com/technet/prodtechnol/windowss erver2003/technologies/clustering/default.mspx

12. MISSION CRITICAL COMPUTING Lesson: Unicode Unicode Fundamentals and Terminology Unicode and Localization Unicode and Siebel Data Types and Storage

13. MISSION CRITICAL COMPUTING Unicode Fundamentals and Terminology The Unicode standards introduced a mapping from the set of integers established by the CCS to a set of code units which are integers in binary form represented as actual data inside a computer. The CEF’s have various types of which the most common are the UTF-8, UTF-16 and UCS-2, which is a derivative of UTF-16. The Unicode standards introduced a mapping from the set of integers established by the CCS to a set of code units which are integers in binary form represented as actual data inside a computer. The CEF’s have various types of which the most common are the UTF-8, UTF-16 and UCS-2, which is a derivative of UTF-16. Character Encoding Form (CEF) A coded character set (CCS) meaning an abstract character has been mapped to a non-negative numeric value, usually represented by a hexadecimal value. Code Page Data in a database is stored as a sequence of bytes (numbers). A standard that attempts to provide a unique number for storing and displaying every character of all the worlds languages, past and present including scientific and technical symbols. Computer systems, e.g. Operating systems (Windows), Databases (SQL, Oracle, DB2) and Applications (Siebel) must decide how they will encode data internally. A standard that attempts to provide a unique number for storing and displaying every character of all the worlds languages, past and present including scientific and technical symbols. Computer systems, e.g. Operating systems (Windows), Databases (SQL, Oracle, DB2) and Applications (Siebel) must decide how they will encode data internally. Unicode More Information: http://www.unicode.org/unicode/reports/tr17/

14. MISSION CRITICAL COMPUTING Unicode and Localization Unicode is the storage of the data, whereas Localization is the display/usage of the data Localization is a set of rules or processes guiding how locale-sensitive data is interpreted when input by a user and how such data is presented to the user.  USA:10/20/2004 2:30:33 pm  Germany:2004/10/20 14:30:33

15. MISSION CRITICAL COMPUTING Unicode and Siebel Support for Unicode will depend on your version of the Siebel product and the database*  Siebel on DB2 and SQL Server will support UCS-2  Siebel Oracle will support UTF-8 UCS-2 is a fixed length double byte code page UTF-8 is a variable length single byte code page * Siebel’s support for Unicode on a particular database does not imply that the database only supports that encoding format.

16. MISSION CRITICAL COMPUTING Data Types and Storage Languages Code Page UTF-8 UTF16 UCS-2 English and Latin based non accented characters. 1 Byte 1 Byte No Change 2 Bytes Western European (Accented Characters Only) 1 Byte2 Bytes Eastern European (e.g. Cyrillic, Greek) 1 Byte2 Bytes Asian 2 Byte3 Bytes 2 Bytes No Change Thai 1 Byte3 Bytes2 Bytes Surrogate Pairs (All languages) N/A6 Bytes4 Bytes It’s important to note where conversions will increase your database size and where there will be no change. Language – Encoding Format Chart:

17. MISSION CRITICAL COMPUTING Review SQL Server High Availability Unicode

18. MISSION CRITICAL COMPUTING Microsoft Contacts for More Information More Information – seblhelp@microsoft.comseblhelp@microsoft.com Microsoft Contacts:  Anu Chawla – anuchaw@microsoft.com  Frank Mcbath – Frankmcb@microsoft.com