Skip to content

[DbScopedconfigMaxDOPSecondary property is not working as expected #597

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
llali opened this issue Apr 2, 2025 · 0 comments
Open

[DbScopedconfigMaxDOPSecondary property is not working as expected #597

llali opened this issue Apr 2, 2025 · 0 comments
Assignees
@llali
Labels
bug Something isn't working

Comments

@llali
Copy link
Member

llali commented Apr 2, 2025

  • SqlPackage or DacFx Version:
  • .NET Framework (Windows-only) or .NET Core:
  • Environment (local platform and source/target platforms):

Steps to Reproduce:

  1. create a sqlproject and set DbScopedconfigMaxDOPSecondary property to a value
  2. add any other db options to the sqlporject
  3. build and publish the project

Expected: both db options are set in the target database
Actual: DbScopedconfigMaxDOPSecondary is not set correctly

Did this occur in prior versions? If not - which version(s) did it work in?

(DacFx/SqlPackage/SSMS/Azure Data Studio)
@llali llali added the bug Something isn't working label Apr 2, 2025
@llali llali self-assigned this Apr 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@llali llali

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@llali