December 9, 2015 at 4:16 am
A network Type installed Windows Server Core on a Server for security reasons.
There is in GUI.
How do you manage SQ Server without a GUI?
I have had numerous occasions where I had to remote into a Server when I could not connect remotely.
Your advise is welcome.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
December 9, 2015 at 4:30 am
I have several servers here like that. I have SSMS on my PC and connect to them from that. If a remote connection isn't possible then probably Powershell.
https://technet.microsoft.com/en-us/library/ee441255(v=ws.10).aspx
December 9, 2015 at 4:50 am
BrainDonor (12/9/2015)
I have several servers here like that. I have SSMS on my PC and connect to them from that. If a remote connection isn't possible then probably Powershell.https://technet.microsoft.com/en-us/library/ee441255(v=ws.10).aspx
It does not make my job easy
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
December 9, 2015 at 5:03 am
As Steve mentioned Powershell Or you can use SQLCMD. Among these two PS is better.
December 9, 2015 at 5:55 am
BrainDonor (12/9/2015)
I have SSMS on my PC and connect to them from that. If a remote connection isn't possible then probably Powershell.
Yup, this exactly. Since you shouldn't be logging into the server directly and managing SQL from there, it should make very little difference that the windows server is the Core install. For the rare occasions where SQL's not allowing remote connections, Powershell or SQLCMD. Configure remote DAC and it should be even fewer cases.
The answers are probably going to be the same as last time you asked this http://www.sqlservercentral.com/Forums/Topic1694123-2799-1.aspx
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 9, 2015 at 6:53 am
Post removed.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
December 9, 2015 at 6:57 am
Well that is great.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
December 9, 2015 at 10:43 am
GilaMonster (12/9/2015)
BrainDonor (12/9/2015)
I have SSMS on my PC and connect to them from that. If a remote connection isn't possible then probably Powershell.Yup, this exactly. Since you shouldn't be logging into the server directly and managing SQL from there, it shouldhen I want to logon to the server\ make very little difference that the windows server is the Core install. For the rare occasions where SQL's not allowing remote connections, Powershell or SQLCMD. Configure remote DAC and it should be even fewer cases.
The answers are probably going to be the same as last time you asked this http://www.sqlservercentral.com/Forums/Topic1694123-2799-1.aspx
I like the flexibility of using the client tools on the server if everything goes bad,
Yes you can use power shell but it limits your vision. I want to be able to quickly navigate among screens,
I do not want to be limited fully to what I can do.
Respectfully Am I asking too much?
I want to react quickly and if I can't connect remotely
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
December 9, 2015 at 1:35 pm
You are asking too much of Server Core.
If you're remote, and you need client tools in a GUI, then you should have a remote machine that you connect to, which has client tools. A PC or a full Server version that has client tools and can connect to the instance.
IF you really need to be quick, and on the local host, then don't use Core, or learn to use SQLCMD and have scripts on the machine you can run. SQLCMD allows you to run scripts.
December 9, 2015 at 4:03 pm
Steve Jones - SSC Editor (12/9/2015)
You are asking too much of Server Core.If you're remote, and you need client tools in a GUI, then you should have a remote machine that you connect to, which has client tools. A PC or a full Server version that has client tools and can connect to the instance.
IF you really need to be quick, and on the local host, then don't use Core, or learn to use SQLCMD and have scripts on the machine you can run. SQLCMD allows you to run scripts.
I agree. I do not want to use core.
I am trying to justify a case against using core.
Thanks for your input.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
December 14, 2015 at 7:12 am
I have always tried to get an environment where my administration tools are on a separate Windows instance to the database servers. One of the main reasons is that logging on to a database server adds risk in terms of my ad-hoc memory and CPU use affecting performance, and simply having a Windows desktop open adds stability risk to the server.
There have already been other people recommending you do your SQL administration from a separate machine. Using a separate machine is not something weird and unusual, but is considered standard practice in many installations.
Your Windows folks are right to want to use Core wherever possible. There is a track record of Core being more stable and needing less patches. As a DB professional IMHO this is something you should encourage.
There are some situations where Core cannot be used due to technical limitations, a major one being that Core does not support SSRS. However, whenever I see a DB server role that can run with Core then I try to get the Windows people to use it.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
December 14, 2015 at 7:26 am
EdVassie (12/14/2015)
I have always tried to get an environment where my administration tools are on a separate Windows instance to the database servers. One of the main reasons is that logging on to a database server adds risk in terms of my ad-hoc memory and CPU use affecting performance, and simply having a Windows desktop open adds stability risk to the server.There have already been other people recommending you do your SQL administration from a separate machine. Using a separate machine is not something weird and unusual, but is considered standard practice in many installations.
Your Windows folks are right to want to use Core wherever possible. There is a track record of Core being more stable and needing less patches. As a DB professional IMHO this is something you should encourage.
There are some situations where Core cannot be used due to technical limitations, a major one being that Core does not support SSRS. However, whenever I see a DB server role that can run with Core then I try to get the Windows people to use it.
What if you can't establish a remote session to SQL Server via SSMS?
How do you use configuration manager from a remote machine?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
December 14, 2015 at 8:22 am
What if you can't establish a remote session to SQL Server via SSMS
I can remember maybe less than 5 situations like this over more than 10 years. In these situations I used SQLCmd on the box itself.
Core does not stop you loging on the the DB box, it just does not have a GUI.
How do you use configuration manager from a remote machine
This works with Core.
Configuration Manager tends to be needed when the box is being built and commissioned, and mostly never used after that.
The Administration Servers that were used were typically Windows Server instances managed in the same way as other Windows boxes, but designated for the DBA Admin role. Typically there would be one Admin server in each physical location to give some redundancy, and we would RDP on to these servers to do day-to-day work.
We really did have very few problems with the Admin servers and getting them to talk to the DB boxes. Most of the problems we did get were establishing RDP from our desktop to the Admin server, but multiple networks and server redundancy dealt with these. Where we did have RDP issues, it was probably easier to deal with from a network and security perspective that our target was one of a small number of Admin servers rather than a much larger number of DB servers. Using Admin servers definitely helped security because we could prevent the DB servers from being accessed by anything outside of the data center.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
December 14, 2015 at 9:07 am
Welsh Corgi (12/14/2015)
How do you use configuration manager from a remote machine?
Start building scripts: http://powershell.com/cs/forums/t/19301.aspx
Some ideas:
http://stefanteixeira.com/2015/09/01/automating-sqlserver-config-with-powershell-wmi/
Viewing 14 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply