Editorials

Webcast Today: ASP .NET Dynamic Data Starter

Featured Article(s)
Troubleshooting SQL Server 2005 Joins (Part 2)
In this article, Alexander Chigrik explains some problems that you can have when you work with SQL Server 2005 joins. He also tells how to resolve these problems.

Quick Start: ASP .NET Dynamic Data Starter
Get up to speed with ASP.NET Dynamic Data in just a few minutes. In this demo you’ll see how to quickly setup a Dynamic Data web application. Presented by: Rachel Appel
> Register Now
> 8/12/2009 at 12:00pm Noon Pacific

SharePoint Administration and SQL Server
As I hear from more and more readers about SharePoint, the things you’re facing and working through in adding this to your environment and so-on, it’s clear that it really is a good deal like the Access departmental database in so many ways. I’ve heard many times that SharePoint does, indeed, need the same care and feeding as a SQL Server installation, but at the same time the user expectations are different for a SharePoint install.

I can also tell you that SQL Server 2008 R2 will be emphasizing "plays well with SharePoint" as more and more sharing (pardon the pun) and overall BI-related work is done. The clear direction is SharePoint as the central repository and enabling technology behind the empowered user that’s building their reports and working with the information in your SQL Server, be it an OLTP system or your OLAP or data warehouse system. In other words, we have to figure this out, and it’s going to be a whole lot easier for everyone if we can work from the get-go on getting systems in place. To say that the "accidental DBA" is going to be commonplace is an understatement, if only in the fact that a SharePoint installation won’t necessarily require a full time DBA, but will require many of the same administrative-type tasks and best practices.

To be clear, I don’t think this is a "problem," but rather something we need to be incorporating in the overall plan and approach to working with SQL Server.

More from readers, starting with Eileen, "I am having the same difficulty in my organization. I generally find out about SharePoint installations after the fact then I am asked to set up maintenance. I am not involved with the architecture or securing of these environments although I should be.

a) No the DBAs are not involved with all SharePoint installations.
b) no we have not applied same SQL Server Models (see answer 1)
c) partially supporting SharePoint from a SQL perspective (see above)
"

Mike’s short and sweet comments were intriguing too, "Not involved. The network folks seem to be keeping this one to themselves."

Which leads to an interesting point. SharePoint isn’t seen as a database environment, even though it’s based heavily in that technology. Time to help out and get involved.

Weekly SelectViews Show
(Part 2) Stephen Wynkoop and Chris Shaw talk about top SQL Server Performance Tips. Part 2 of 2 – things you can try, things you should know about, tips for your SQL Server.
[Watch the Show Here]

Previously:
[Watch Here] (Part 1) Stephen Wynkoop and Chris Shaw talk about top SQL Server Performance Tips
[Watch Here] vConference Session Sample: Thomas LaRock SQL Server 2008 Maintenance Plans. Learn about the ins and outs of maintenance plans in SQL Server 2008 – what do you really need to know?
[Watch Here] The show today features RAID and Defrag tips, backup optimization with filegroups, baseline stats and industry news. Also, find out about virtual learning opportunities, the SQL tip, the developer/AJAX thoughts and much more.

Featured White Paper(s)
How to Manage and Configure SSIS Packages – A SQL Server Technical Article
Administering SSIS can be a challenging task for a DBA who’s not familiar with the SSIS environment and some of the new hurdl… (read more)