Truncate SQL log on development machines

By default the recovery model in SQL Server is full, so if you have a development server that doesn't have scheduled backup, the database log file can potentially grow out of control.  You can either set the recovery model to "simple", and then truncate the file.  Or keep the recovery model as full and force truncation.  Obviously shouldn't do this blindly in production unless you understand the implications.  This gets asked frequent enough, but not enough to remember the syntax, so this post is here as a memory jogger.

USE dbname

BACKUP LOG dbname WITH TRUNCATE_ONLY

DBCC SHRINKFILE (logical_log_filename, 10)

Sharepoint VSeWSS 1.1

If you are doing WSS or MOSS development, do check out the VSeWSS 1.1 release.  It provides some help to develop .WSP package right inside visual studio.  The new 1.1 release allows you to have more control over the WSP solution creation.

If you have been only using Sharepoint designer for customising WSS or MOSS or have your own scripts to generate and maintain sharepoint features, give VSeWSS 1.1 a go.  See the sharepoint team blog entry at http://blogs.msdn.com/sharepoint/archive/2008/02/11/announcing-the-final-release-of-vsewss-1-1-and-the-upcoming-version-1-2.aspx