Author: Edwin Sarmiento

Last year I started to get involved in the SharePoint community, particularly the SharePoint Saturday events. As a SQL Server DBA, I thought that SharePoint administrators needed to have a fair understanding of the underlying database because it is the…

In the first part of this series on Filtered Indexes, I talked about how SQL Server navigates through the index structure and used a clustered index as an example to demonstrate how the process works. To continue this series, we’ll look at…

“During one of my SQL Server Index Internals presentation, an attendee asked me how filtered indexes look like and if they are stored exactly the way the traditional indexes are. I was tempted to show the internals of how filtered…

When I was in high school, my practical arts teacher asked us to create a miniature of a structure. This meant looking at the blueprints of an existing structure and using it to create a small replica. I thought that…

This post should give you some insights into the risk that your databases are in by switching to the bulk-logged recovery model. So, what do you need to do to avoid this risk? Make sure that you run a backup immediately after the transactions you are running under the bulk-logged recovery model complete.

I describe AlwaysOn Availability Groups as a “database mirroring configuration sitting on top of a Windows Failover Cluster infrastructure.” Why do I say this? It’s because I want SQL Server DBAs to leverage what they already know on features like database mirroring and failover clustering and apply them when dealing with AlwaysOn Availability Groups.

I’ve rewritten this blog post in the series to include other new features in SQL Server 2012 outside of high availability and disaster recovery. Ever since the product has been released, I’ve had a chance to look at features that will address performance challenges and business intelligence requirements.

I’ve been playing with SQL Server 2012, codenamed “Denali,” since the CTP days and am very happy with some of the features that they have introduced to address high availability and disaster recovery requirements. For me, these are more than enough reasons to consider upgrading to SQL Server 2012.

I was reading my session evaluation results and came accross comment that said: “copy and paste coder.” I’ve been doing this specific presentation for almost 5 years now with a few tweaks every once in a while based on feedback. Yes, I live and breathe disaster recovery as part of my day-to-day job. However, there are several reasons why I do not type nor write code during my presentations. Here are a few of them.

In this blog post, I’ll talk about key items that we sometimes tend to ignore when creating a disaster recovery strategy – the lion, the “switch” and the wardrobe