Home → Problems →

SqlPackage error 'DatabaseServiceObjective' is not a valid argument for the 'Publish' action

• Edit

Karlkim Suwanmongkol

Oct 28, 2015 @ 06:07 PM

I try to have AppVeyor publish dacpac to Azure SQL Database with the specific performance level (e.g., S0, S1, and so on) using "DatabaseServiceObjective" option. However, in AppVeyor, I got an error 'DatabaseServiceObjective' is not a valid argument for the 'Publish' action.

On my local machine, running sqlpackage /a:publish /?, I see the option below.

SqlPackage: Command-line tool for creating and deploying SQL Server databases and DACPAC packages.
Copyright (c) 2015 Microsoft Corporation.  All rights reserved.
...
/p:DatabaseServiceObjective=(STRING)
 Defines the performance level of a Microsoft Azure SQL Database such as "P0" or "S1".

However, on AppVeyor, it's still older 2014 version.

C:\Program Files (x86)\Microsoft SQL Server\120\DAC\bin\SqlPackage.exe
SqlPackage: Command-line tool for creating and deploying SQL Server databases and DACPAC packages. 
Copyright (c) 2014 Microsoft Corporation.  All rights reserved.

Could we upgrade the SqlPackage.exe? I believe it comes with SQL Server 2014 CU5 or SQL Server 2014 SP1.

1. Support Staff 1 Posted by Feodor Fitsner on Oct 30, 2015 @ 12:17 AM

   

   Oh, there is SP1 already! Will schedule the deployment - thanks for letting me know.

   • Edit

2. Support Staff 2 Posted by Feodor Fitsner on Oct 30, 2015 @ 01:18 AM

   

   Apparently, the most recent SqlPackage.exe tool is located in the following locations:

   VS 2013:

   C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\SQLDB\DAC\120
   

   VS 2015:

   C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\SQLDB\DAC\120
   

   • Edit

3. 3 Posted by Karlkim Suwanmo... on Oct 30, 2015 @ 03:33 AM

   

   Thanks. I tried the SqlPacakge.exe on VS2015 image, but I got another error though. :-(

   The provided database option 'Service_Objective' 
   is not supported in this version of 
   Microsoftr SQL Serverr Transact-SQL ScriptDom library. 
   You need to install a newer version of the library.
   

   Hopefully, the problem will disappear after the SP1 upgrade.

   • Edit

4. Ilya Finkelshteyn closed this discussion on Aug 25, 2018 @ 02:01 AM.