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!
Philip Flynn
shared this idea
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.
For more information, see http://www.red-gate.com/supportcenter/Content.aspx?p=SQL%20Compare&c=SQL_Compare/help/8.50/ssmsip_deploy_new_database.htm&toc=SQL_Compare/help/8.50/toc1280663.htm.
-
mark
commented
I found a work around use the options
System.Data.SqlClient.SqlException: Invalid filegroup
<IgnoreFileGroups>True</IgnoreFileGroups>
-
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.