Tracy is a Database Administrator for ChannelAdvisor. She has spent over 20 years in IT and has been using SQL Server since 1999 and is currently certified as a MCSE Data Platform. She also tinkered with databases in middle school to keep her sports card collection organized. She blogs at tracyboggiano.com. Her passion outside of SQL Server is volunteering with foster children as their advocate in court through casaforchildren.org.
4 WAYS YOU SHOULD COLLECT PERFORMANCE
Database administration is a fundamental responsibility but we are often reactive to a ticket, an email or conversation about something that happened after the fact. But without a set known-good measurements to compare against how do you know what to look at? This session will show you how to capture a performance baseline for a SQL Server instance. The session will help you decide what and when to capture data and where to store it. Then we will walk through different tools and scripts to use.
What I will leave with: Understanding of methods and tools to capture performance and identify issues. You will be able to start collecting performance information and be more knowledgeable about your environment.
Doug Purnell is a DBA at Elon University in North Carolina and is a co-leader for the Triad SQL BI PASS User Group. He has 15 years of experience with SQL Server and enjoys finding new ways to solve business problems with data. In his spare time you can find Doug taking photos and cooking up some BBQ on his cooker.
Fun Fact: Elon is the town Carlos grew up in.
The Right Disaster Recovery Option
So you have a good backup strategy in place, but now you have to think about recovery. Where do you start and what are your options? SQL Server offers several options, but then how do you choose the right one to meet your business requirements? In this session, we will go over some of the common DR options including log shipping, replication, mirroring, clustering, and AlwaysOn. Then we will talk about how to choose the best one to meet your business needs.
What I will leave with: How to define an RTO/RPO policy, a functionality matrix for various DR options.