Create the database from scratch
Instead on relying on the user to create the database and all the file groups, files and getting the collation correct, source control should do this for the user. it could perhaps prompt for a file location to put all the files but if I've gone through the effort of making file groups and sizing my files just right, I want those changes to be kept!
Title: Objects need to be created using one or more non-standard filegroups. These filegroups may need to be created manually: PartScheme_Stream
I get this "warning" when I attempt to commit changes to Source Control. I see this as a deficit. I am using Partitions and Page Level Compression. I have 10 filegroups. Please make it so that I don't have to Manually Script anything. This to me seems like a big set back to adoption.
Visual SVN has a really cool feature which allows you to open a solution directly from source control. You simply open Visual Studio, enter the SVN repository path and it downloads and creates a local version on your machine.
I would be great to have this sort of functionality in this application
As well as working from inside SMSS I'm often working in the files/folders using Tortoise SVN. I think it would very handy to have a small exe inside each db root directory, which, when clicked, would ask for the SQL instance name and build the database from the files or folders
SQL Compare 8.50 comes with the SSMS Integration Pack, which allows you to get the latest version of the db or a specific version of the db to a new database. This will use all the defaults for your new db.
I found a work around use the options
System.Data.SqlClient.SqlException: Invalid filegroup
Richard Sterling commented
What does this error message actually mean? My colleague created these filegroups for performance related reasons using guidelines from Microsoft. Why is RedGate complaining about it?
Sidharth Nayyar commented
I agree with John. We can use sqlcompare through command prompt to do continuous integration but the missing piece is the creation of the database. If this was also stored in source control then continuous integration should have the option to also create a new database.
John Fuex commented
I think it ought to script the database itself and let you store that in source control. Then it would be able to create the DB completely from source control.