3/23/2017 6:13 AM © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

Construyendo sistemas de alta disponibilidad con SQL Server™ 2005 Ruben Dillon Solution Architect MCSE, MCAD.Net, MCSD.Net, MCDBA SQL Server Hewlett Packard

Actualización inmediata 3/23/2017 6:13 AM ¿Cuando tomar ventaja de SQL 2005? Cuanto trabajo se requiere para aprovechar la tecnología? Diseño y arquitectura Actualización inmediata Mínimo trabajo Partial Database Availability Online Piecemeal Restore Instant File Initialization Fast Recovery Online Index Operations When Criteria Met Snapshot Isolation Statement-level Snapshot Snapshot Isolation Transaction-level Snapshot (RO) Failover Clustering Database Mirroring Log Shipping Database Snapshots Online Index Operations When Criteria NOT Met (minority) Snapshot Isolation With Update Conflict Detection Replication Most of the Availability Features fall within the Upgrade Immediate and Minimal Work to Leverage categories… But there are many other features to work with once you’ve designed your database to stay available. This slide is not meant for any depth whatsoever… it’s meant to be an “impressive list of options” slide. Depending on the type of failure you have, technologies/features are available to prevent and/or provide immediate to latent failover recovery. Additionally, there is probably more than one that may address the expected barriers that you will encounter. Likely not only one feature but possibly a few features that may help your database stay online and already available. Do NOT spend any real time on this slide and don’t even mention these by name. Hit very general highlights here and give them some insight into things we’ll discuss within this presentation: Some of these features will be immediately available – just by upgrading while others require only a minimal amount of code to leverage. Bolded items are new and upcoming technologies for SQL Server™ 2005 Many of the established technologies (such as Failover Clustering) are not radically different but have been improved with some great new features/capabilities. We will not only discuss but also demonstrate how many of these technologies will help your databases stay available through a variety of barriers to availability. The first area that we will cover are the features that are immediately available – just upgrade. Then we will work through a couple of the minimal work to leverage features and then move to high availability/scalability and touch on the large number of technologies possible here. Mejorando la disponibilidad desde la instalación al diseño Disponibilidad en capas para minimizar el downtime y la pérdida de datos © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

Que ocurre cuando Operaciones de lectura y escritura quieren acceder los mismos datos En SQL Server™ 2000 Se utilizan técnicas de bloqueo para obtener el nivel de aislamiento deseado Los usuarios deben esperar para acceder los datos bloquedos La concurrencia y el rendimiento se ven comprometidos La consistencia se ve comprometida cuando se utilizan niveles de bloqueo inferiores para evitar los bloqueos En SQL Server™ 2005 Se pueden utilizar técnicas de bloqueo o versionamiento para lograr el nivel de aislamiento deseado Cuando se usa versionamiento las operaciones de lectura no bloquean las operaciones de escritura y viceversa La consistencia no se ve comprometida debido a niveles de bloqueo inferiores

Snapshot Isolation Mejorando la concurrencia en Mixed Workloads 3/23/2017 6:13 AM Snapshot Isolation Mejorando la concurrencia en Mixed Workloads SQL Server™ 2000 Isolation es implementado unicamente por locking Mixed workloads puede experimentar: Problemas de concurrencia debido a bloqueos El problema de análisis de inconsistencia SQL Server™ 2005 Isolation es implementado usando locking y versionamiento Mixed workloads puede mejorar la consistencia en la lectura y performance usando: Read committed with Statement-level snapshot a nivel de instrucción Snapshot Isolation a nivel transacción Snapshot Isolation also has two primary areas that it falls into: Read Committed with statement-level snapshot (RCSI) = Statement-level Consistency This mode is definitely a minimal work to leverage feature as it only requires the database option (READ_COMMITTED_SNAPSHOT) to be turned on. Once on, every statement uses versioning - automatically. This is [very] minimal work to leverage. However, if transaction-level snapshot is desired and will be used with transactions that include modifications and not only reads, then application changes are required in order to resolve and detect update conflicts - as well as to even use snapshot isolation. © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

Concurrencia Read Committed w/Statement-level Snapshot 3/23/2017 6:13 AM Concurrencia Read Committed w/Statement-level Snapshot Habilitar DB Option: READ_COMMITTED_SNAPSHOT locking para escrituras, versioning para lecturas Incrementa disponibilidad de data mientras reduce deadlocks No se bloquea reportes ni ad hoc queries Readers no bloquea writers; writers no bloquea readers Resulta en una consistencia a nivel de instrucción (statement-level) por medio de versionamiento por row Impacto a las aplicaciones No se requieren cambios para transacciones de lectura Snapshot Isolation also has two primary areas that it falls into: Read Committed with statement-level snapshot (RCSI) = Statement-level Consistency This mode is definitely a minimal work to leverage feature as it only requires the database option (READ_COMMITTED_SNAPSHOT) to be turned on. Once on, every statement uses versioning - automatically. This is [very] minimal work to leverage. However, if transaction-level snapshot is desired then application changes should be made to resolve and detect all conflicts - as well as to even use snapshot isolation. © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

Snapshot isolation 3/23/2017 6:13 AM © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

Database Scale Out Replicación Peer to Peer Replication 3/23/2017 6:13 AM Database Scale Out Replicación Peer to Peer Replication Bases de datos idénticas trabajan sincronizadas Permite escalar la carga de trabajo en consultas más allá de una única base de datos Example: Distributed Trading System Chicago London Tokyo Targeted at scenarios that have two requirements: Geographic HA and read scale out. This is an evolution of the reporting server concept. Customers often used the reporting server to recover from failures and perform maintenance. As time went on, they distributed a greater portion of their workload across the publisher and subscribers and then started replicating bi-directionally. SQL Server™ 2005 added new logging to maintain the originator of changes to allow more complex topologies (damps the system and prevents changes from looping recursively). Many customers deploy this scenario using less sophisticated bus topologies in SQL Server™ 2000. Passport, Xbox Online, a large Telco, Wildcard systems (credit card processing) are all examples. Note: The applications are responsible for distributing the SQL workload across the participating databases. NLB can be used to balance read workload. insert/update/delete workload will not scale higher than a single node as nodes are added. To scale insert/update/delete workload, customers should investigate manual partitioning across the databases Insert/update/deletes to the same rows must not occur at the same time at different nodes. This is not supported in P2P and will cause replication to stop pending corrective action to resolve the data conflict(s). See BOL © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

Replicación Peer-to-Peer 3/23/2017 6:13 AM Replicación Peer-to-Peer Basado en replicación Bi-direccional Transaccional Todos los participantes son peers Schema es idéntico en todos los sitios Se publica las actualizaciones hechas en “su” data Se subscribe a otros para tomar sus cambios No existe una arquitectura jerarquica como lo sería una replicación transaccional “normal” Un mismo conjunto de datos sólo pueden ser modificado en un único sitio al mismo tiempo La propiedad de los datos es puramente lógica; no previene conflictos SQL Server prevé la replicación cíclica de un cambio © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

Peer to Peer replication 3/23/2017 6:13 AM Peer to Peer replication © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

HP Systems Architecture Analysis

HP Systems Architecture Analysis Analiza la arquitectura actual Oportunidades que se generan Actualización y startup de plataforma, Migración de plataforma, Consolidación, Virtualización Compara la arquitectura actual contra mejores practicas MSA, WSSRA BOIS Security and Operation Guides Solution Accelerators HP Active Answers Presenta un plan de proyectos

HP Systems Architecture Analysis 3/23/2017 6:13 AM HP Systems Architecture Analysis Plan de proyectos Se presentan distintas alternativas en base a la información recolectada Entrevistas con personal de la empresa Captura automatizada de asset y performance de equipamientos involucrados © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

© 2005 Microsoft Corporation. All rights reserved. 3/23/2017 6:13 AM ruben.dillon@hp.com © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.