sqlpackage

We are using Sql Server database projects to create deployment scripts from DacPac using SqlPackage.exe. We have different SQL Server Filegroups setup in various environments. When deploying we exclude Filegroups as we want objects to create in the default Filegroup. In database project settings the default Filegroup is not changed from PRIMARY. This presents a problem when attempting to deploy to an environment where the default Filegroup is not PRIMARY because the following code is included... ALTER DATABASE [$(DatabaseName)] MODIFY FILEGROUP [PRIMARY] DEFAULT; Is there a way to prevent this

I have a SQL Server Database Project targeting a SQL Server 2012 RC0 database. The project was created in Visual Studio 2010 + SQL Server Data Tools CTP4. The project type is different than the regular Visual Studio 2010 database projects (it's the next version of SQL Developer Tools CTP3 Juneau). It deploys fine in the IDE. How can I deploy it via the command line? I tried VSDBCMD.exe but it expects a .deploymanifest file which is not created by the new project type. Keith Use sqlpackage.exe , located in C:\Program Files\Microsoft SQL Server\{version}\DAC\bin or C:\Program Files (x86)

I've been successfully publishing DACPACs to SQL Server 2008-2012 instances using SqlPackage.exe, as installed by SQL Server Data Tools (and typically found in C:\Program Files (x86)\Microsoft SQL Server\110\DAC\bin ). However, in attempting to publish a 2014-targeted DACPAC to a SQL Server 2014 instance using this same SqlPackage.exe, I get the following: *** Could not deploy package. Internal Error. The database platform service with type Microsoft.Data.Tools. Schema.Sql.Sql120DatabaseSchemaProvider is not valid. You must make sure the service is loaded, or you must provide the full type