Skip to content
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.

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

Received from community - checking SQL benchmarks on "named instances" #266

Open
flobroeder opened this issue Feb 23, 2023 · 1 comment
Open
Labels
information needed Extra attention is needed question Further information is requested
Milestone

Comments

@flobroeder
Copy link
Contributor

In reality, I attempted to run a Microsoft SQL Server 2016 policy scan in a number of different methods, but each time, it indicated that the "named instance" was inaccessible. Only the built-in instance "MSSQLSERVER" is being used by us, and I verified that your script was also using this instance when I looked at it.
For the purpose of doing a Microsoft SQL SERVER 2016 policy scan, could you please explain how to enter the user: sa account password.

@flobroeder flobroeder added the question Further information is requested label Feb 23, 2023
@perumalraja91
Copy link

Dear Florian,

Please let me know when I should expect this problem to be resolved.
MS SQL Server issue4
MS SQL Server issue3
MS SQL Server issue2
MS SQL Server issue1

@TuemmlerKelch TuemmlerKelch added the information needed Extra attention is needed label Jul 20, 2023
@TuemmlerKelch TuemmlerKelch added this to the 5.11 milestone Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
information needed Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants