Editorials

Best Practices for SQL Server and SharePoint?

Featured Article(s)
Doing More with Less Money on Your Servers
In the past I have worked at corporations where we had a limited budget and we were always expected to do more with what we had. I always loved the way that the budget was done based on what we spent and performed at the previous year and yet, when we did the planning for the new year, there was always a new project

Learn about managing your SQL Server data recovery vulnerabilities
In this session we’ll look into the different options you have available to protect your SQL Server investment. Learn about backup and restore, log shipping, replication and other tools you can use to help reduce risk. Find out what is involved, the pros and cons and where you can go to learn more about each option.

> Register Now
> Live date: 2/25/2009

Using SharePoint?
What have you learned about your use of SQL Server specifically as it relates to your SharePoint installation? What surprises have you come across? What went exactly as you expected?

I’m really interested in hearing about your lessons-learned, things that go into the planning and support of a SharePoint installation. I know that many times as the system is scoped and sized, the fact that you’re storing a number of different data types and user-generated content can surprise with the amount of storage/disk required. Additionally, splitting and managing storage locations can be helpful for your SharePoint install – both from a recovery standpoint and a performance standpoint.

What items do you see? Are there things you sort of slapped your forehead, said a quiet (or loud) D’OH! and had to re-think?

[Drop me a note here with your experiences]

Featured White Paper(s)
How to Deal with managing jobs and job failures in Multiple Data Centers
As a SQL Server DBA, I have often found myself stretched pretty thin trying to monitor SQL Server Agent across a plethora o… (read more)

Uncovering a Hidden SQL Server Performance Killer
So youve checked all the likely suspects, but your SQL Server performance is still poor. Before you put that capital request… (read more)