Skip to content

diagnostic-connection-for-database-administrators with SSMS#4153

Closed
ChadSimmons wants to merge 1 commit intoMicrosoftDocs:livefrom
ChadSimmons:patch-1
Closed

diagnostic-connection-for-database-administrators with SSMS#4153
ChadSimmons wants to merge 1 commit intoMicrosoftDocs:livefrom
ChadSimmons:patch-1

Conversation

@ChadSimmons
Copy link
Copy Markdown

Add steps for creating a DAC from SQL Server Management Studio to address the error "Dedicated administrator connections are not supported via SSMS as it establishes multiple connections by design. (Microsoft.SqlServer.Management.SqlStudio.Explorer)"

Add steps for creating a DAC from SQL Server Management Studio to address the error "Dedicated administrator connections are not supported via SSMS as it establishes multiple connections by design. (Microsoft.SqlServer.Management.SqlStudio.Explorer)"
@PRMerger17
Copy link
Copy Markdown
Contributor

@ChadSimmons : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@MikeRayMSFT
Copy link
Copy Markdown
Contributor

Thank you @ChadSimmons - reviewing


> [!Note]
> To establish a DAC from SQL Server Management Studio
> - Disconnect all connections to the related database
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Disconnect all connections to the related SQL Server instance, including the Object Explorer and all open query windows.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apologies for the delay. GitHub notifications got marked as spam in an Outlook.com account (how is that possible!?).
Anyway, I would happily accept the change if I could figure out how. I even phoned a friend and we're stumped.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No worries! I think you need to rewrite your change to match my review, I don't think there's a way to automatically accept it.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't figure it out. I'm going to manually take in the changes @bluefooted recommended in our private repository.

@ChadSimmons thanks for the submission.

> To establish a DAC from SQL Server Management Studio
> - Disconnect all connections to the related database
> - From the menu select **File** > **New** > **Database Engine Query**
> - From the connection dialog box in the Server Name field, enter **admin:** if using the default instance or **admin:\<*instance_name*\>** if using a named instance
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

admin:<server_name> if connecting to a default instance or admin:<server_name><instance_name> if connecting to a named instance.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would happily accept the change if I could figure out how.

@bluefooted
Copy link
Copy Markdown
Contributor

I'm good with adding this, but I have requested a few changes to the wording, see my review above.

@MikeRayMSFT
Copy link
Copy Markdown
Contributor

@ChadSimmons, feel free to incorporate the proposed changes, or let me know and I will. Thank you.

@MikeRayMSFT
Copy link
Copy Markdown
Contributor

I'm closing this pull request and publishing in https://github.com/MicrosoftDocs/sql-docs-pr/pull/14735

We couldn't submit the update because the clone that was used for the original pull request is not available. Don't know why. I just manually added it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants