I have just read the following post on SO;
Do you source control your databases
We are working with Sitecore and normally Attach 3 standard databases to our MSSQL server.
We have a Core , Master and Web database. In the proces of developing the different templates on the backend of Sitecore we all use one database and just publish our database changes using Sitecore CMS. When for example I create a datatemplate, my collegue will see the same datatemplate appear when he refreshes his “content tree”. From what I’ve read in the post linked above Database Source control is needed when you have multiple versions of source code with different databases. Is it needed to bring our databases under source control? Looking at this knowing that Sitecore is actually handling the publication of items to the different databases etc, and we all work on the same database through Sitecore CMS, I think this won’t be needed. I’m curious if there would be any advantage of still putting the databases under version control.
Sitecore 6 introduced very cool feature called Item Serialization. No need to keep your entire database files under source control. You can store just the serialized versions of necessary items. Those are simple text files on your file system.
Take a look at this blog post from Alex for more details.