I’m very excited to be selected to speak at the SharePoint Evolution Conference 2013 in London, April 15 - 17. Having attended all four previous editions, I can say with confidence that it’s the best SharePoint conference out there. It offers tremendous value for money, a most impressive line-up of speakers, outstanding entertainment and networking opportunities and of course great content. Steve Smith and his team at Combined Knowledge succeed in making every aspect of this conference an amazing experience, with great attention to detail.
You can follow the event on Twitter with hashtag #spevo13
I’ll be delivering a session on SQL Server best practices for SharePoint professionals in the Community Track. In my daily consulting practice I see a lot of SharePoint implementations supported by SQL Servers that aren’t managed by “real” DBA’s. This seems to be more prevalent in the SharePoint world than in other Microsoft ecosystems. Sadly a lot of these systems are poorly setup and managed, and that’s exactly what my session will be about. I’ve more or less made it my personal goal to spread the word on SQL good practices in the SharePoint community, so this will be the right opportunity to do so.
This is the session abstract:
SharePoint and the involuntary DBA
Session COM715, Wednesday April 17, 1:45PM
As SharePoint professionals we all know we probably shouldn’t, but we do: setting up and managing SQL Servers. We often spend so much time meticulously architecting every small detail of our precious SharePoint farm but next-next-finish our way through SQL Server setup. Yet we all know that the single most important contribution to SharePoint performance is a properly configured database platform. In this session we’ll explore the wonderful world of SQL Server for non-DBA’s. We’ll discuss real-world configuration and setup practices that make a difference and benefit your SharePoint environment. What are the SharePoint-specific settings you need to know about? How do you keep it running? We’ll also touch upon some typical problems you might encounter when managing a SQL Server - perpetual log file growth anyone? Everything you always wanted to know but were afraid to ask.