SqlServerDacpacDeployment has been deprecated and WinRM - SQL Server Database Deployment is the recommended replacement. However, the WinRM implementation adds an extra hoop I need to jump through that is completely unnecessary. I use self-hosted Azure DevOps agents that are installed on dedicated virtual servers with everything needed to deploy our solutions. The agents run under accounts that have just enough privileges to deploy database changes to our SQL Servers. SqlServerDacpacDeployment works perfectly in this environment using Windows Authentication ad no admin rights required.
Now, with the WinRM implementation, I have to create an extra service account that has admin rights on my SQL Server. Then I have to install SQLPackage.exe on all the SQL Servers I want to deploy to. Best case, I need to create another VM to run all this stuff when my infrastructure budget is already strapped.
I see the value in this feature for people that are not using self-hosted agents, but the feature needs to be optional. Deprecating SqlServerDacpacDeployment before a complete replacement is ready is also a big mistake.
SqlServerDacpacDeployment has been deprecated and WinRM - SQL Server Database Deployment is the recommended replacement. However, the WinRM implementation adds an extra hoop I need to jump through that is completely unnecessary. I use self-hosted Azure DevOps agents that are installed on dedicated virtual servers with everything needed to deploy our solutions. The agents run under accounts that have just enough privileges to deploy database changes to our SQL Servers. SqlServerDacpacDeployment works perfectly in this environment using Windows Authentication ad no admin rights required.
Now, with the WinRM implementation, I have to create an extra service account that has admin rights on my SQL Server. Then I have to install SQLPackage.exe on all the SQL Servers I want to deploy to. Best case, I need to create another VM to run all this stuff when my infrastructure budget is already strapped.
I see the value in this feature for people that are not using self-hosted agents, but the feature needs to be optional. Deprecating SqlServerDacpacDeployment before a complete replacement is ready is also a big mistake.