Friday, March 28, 2008

Watch the #49 Nascar Team this weekend

OK I'll admit that I'm a NASCAR slappy. I enjoy watching the cars go around and around making left turns the whole day. It's been something that even my son and wife are into so it's pretty much a family affair that is enjoyable for all of us. So when Microsoft announced that they are sponsoring one of the nice guys in the sport, Ken Schrader and his #49 team I was glad to hear it. However Ken only has been in 2 races this year so far. But low and behold he just qualified seventh for this weekend's race. So he'll definitely be in the race this weekend at Martinsville. Must have been some serious motivation there! So if you're flipping the channels and see the race this Sunday look for the #49 Microsoft Small Business Toyota with Ken at the wheel. And don't forget that the blue Small Business Specialist logo is the same one that we have at TAZ Networks.

Thursday, March 13, 2008

Sharepoint 3.0 Config Database Growing Out of Control?

Recently we've seen a growth in disk space on our SBS servers. A big culprit? The config database for Windows Sharepoint Services 3.0.
You'll probably see the database in the C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data directory.

How do we shrink this puppy ASAP?
1. Download the SQL Server 2005 Management Studio Express if you don't have it installed. http://www.microsoft.com/downloads/details.aspx?FamilyId=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&DisplayLang=en
2. Start up Management Studio Express. You'll probably see SERVER1\MICROSOFT##SSEE in the Server Name. However for the embedded edition that Sharepoint Services uses this will not work. You'll get an error that an error has occurred while establishing a connection to the server. It will also tell you that the default settings SQL Server does not allow remote connections. So instead put in np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query to connect to the instance.
3. Once Studio Express is up click on New Query.
4. Enter the following commands in replacing your db name for the one below:

use master
go
backup log "SharePoint_Config_0832ab09-b60f-4e16-a0c7-86ab757e8246" with truncate_only
use "SharePoint_Config_0832ab09-b60f-4e16-a0c7-86ab757e8246"
go
DBCC SHRINKFILE ('SharePoint_Config_0832ab09-b60f-4e16-a0c7-86ab757e8246_log',1)
go

5. Hit Ctrl-E to run the command

Your Sharepoint Config database should now be back to a reasonable size. Don't forget to set a backup or maintenance plan on Sharepoint to avoid this from happening again!