0

I am trying to add a traceflag as a startup parameter to a distant SQL Server 2016, installed on a Windows 2016 core server and I am following these instructions

At this point in the document:

In the console tree, expand Services and Applications, and then expand SQL Server Configuration Manager to manage the remote computer's services.

There is no SQL Server Configuration Manager here.

enter image description here

  • Is this a permissions issue?
  • Does anyone know what permission needs to be added and where so I can see SQL Server Configuration manager under Services and Applications?
  • Does core have anything to do with this?

Thanks, Craig

  • Do you have SQL Server installed on the local server? If you choose add/remove Snap-In in MMC do you see an entry for "SQL Server Configuration Manager"? I'm not sure which installation component installs the SQL Server Configuration Manager component, but it has to be installed locally. – David Browne - Microsoft Sep 18 '18 at 13:55
  • @DavidBrowne-Microsoft, SQL is definitely installed on the remote server because I am able to connect to it via SSMS. On the jump server, in the Add/remove snap-in I don't see SQL Server Configuration Manager. – Craig Efrein Sep 18 '18 at 14:12
  • @DavidBrowne-Microsoft, for info, I am able to manage the remote computer via Computer management. I just don't have access to SQL Server Configuration manager. – Craig Efrein Sep 18 '18 at 14:15
  • The Computer Management snap-in comes with Windows. The SQL Server Configuration Management snap-in is part of SQL Server. – David Browne - Microsoft Sep 18 '18 at 14:16
  • @DavidBrowne-Microsoft, I was over complicating things, and just remembered that there are scripts to add startup parameters with PS. – Craig Efrein Sep 19 '18 at 8:13
0

All I wanted to do was add a startup parameter to SQL Server and to do that, I can use this script.

  1. Copy the script to the remote server
  2. Connect to the remote server on powershell

    Enter-PSSession -ComputerName some_server_with_sql -Credential some_user

  3. Add the Traceflag startup parameter

    [some_server_with_sql]: PS C:\Scripts> .\AddStartupParameters.ps1 '-Tsome_trace_flag_number'

And you are done,

  1. Then to check, you can run this SQL query

    SELECT * FROM sys.dm_server_registry WHERE registry_key LIKE '%Parameters'

enter image description here

Et Voilà as the French would say.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.