At my shop, we've been looking into the source code control integration that's available for our database objects such as stored procedures, functions, triggers, etc.  Since we are in the progress of migrating from SQL Server 2000 to SQL Server 2005, we looked at the integration that's available betweem VSS 2005 and SQL Server Management Studio ...

In a nutshell, you can create a SQL Server Management Studio solution (*.ssmssln) that contains any number of SQL scripts (*.sql).  You have the option of scripting the entire database, including schema and code, in a single script, or scripting each object individually.  These scripts can then be managed by VSS 2005 as you would manage any piece of source code ...

The only thing lacking is the fact that you can't directly manage what's checked into VSS at the "source" level vs. what's compiled in SQL Server.  However, if your development team is disciplined enough to use SQL Server Management Studio as the sole tool for managing SQL scripts (and executing the scripts as they are checked in), then source code management of SQL Server objects can be achieved using the combination of SQL Server Management Studio and VSS 2005 ...