Happy New Year
New Year News
MVP a go-go
In 2007, I was an MVP in Windows Server--Directory Services. This year, my category migrates (you can only be an MVP in one technology) to an area that will make me more valuable to you, the readers of To The SharePoint. I'm hopeful that this will enable me to enhance my relationships with the great folks on the SharePoint product team at Microsoft and to provide even richer insight into the technology, and to begin looking at the next generation of the Office System, currently dubbed "Office 14."
In March and April, you'll find me at several locations around the United States (details to come) including Windows Connections in Orlando, April 27 - May 1. I'll be presenting several SharePoint sessions there along with gurus Melissa Fraser and Wendy Henry. I hope to return to The Netherlands and Scandinavia, which feel like second homes to me, later in 2008, so if you're interested in any training or consulting sessions, let me know.
Technical Warm-up: SharePoint Database Options
Most of my clients are very large, so SQL Server licenses and servers are a-plenty. But in smaller environments, or test environments, do you need SQL Server itself? Maybe not. Keep in mind that there are several "for free" options. First, there is SQL Server Express, freely downloadable from Microsoft's Web site. SQL Express has limitations, however--a database can't be greater than 4GB. Now let's think about that in terms of SharePoint. If a site collection lives in a database, that site collection is limited to 4GB. But other site collections can be in other databases, right? So SQL Express could theoretically host a reasonably large and complex WSS installation. Document libraries (which can easily grow larger than 4GB) would probably be less easy to support on SQL Express.
But even more straightforward is SQL Server Embedded Edition (SSEE)--the Windows Internal Database that's installed by default when you perform a basic installation of SharePoint. Believe it or not, this puny sounding database does not have limitations on database size, so your single-server WSS intranet or your test environment may be very well supported by SSEE.
There are other considerations, of course. You'll need to download the correct administrative tools for the version of SQL Server that you use. And any reasonably large or complex or multiserver configuration will certainly be better to deploy using SQL Server. So many other applications use SQL that the reality is if you don't have SQL Server today, you'll eventually need it. So you might as well pony up the coin and get some licenses. But today? Keep in mind that SQL Server 2008 is just around the corner. Before you cough up for a version of SQL Server (2005) that is about to be supplanted, think about your technology roadmap and whether it might make sense to wait for SQL Server 2008 licenses. Also talk to your Microsoft vendor to discuss what options might exist for buying 2005 licenses today and upgrading to 2008 tomorrow. I try to avoid tracking "license" issues since they're insanely complex and likely to chang e every few weeks, so spend some time talking with your Microsoft vendors about those issues.
For me, in my clients' large production environments, like the SharePoint framework we're deploying for NBC at the Beijing Olympics, we'll be using full-fledged versions of SQL Server. In smaller environments and in my own lab, it's often the Windows Internal Database I turn to...why not?
By the way, thanks to CA Callahan for helping me brush off the cobwebs on these thoughts in my brain! If you're reading this, I owe ya a beer or something like that :)
Until next week, all the best!
danh at intelliem dot (top level commercial domain)