June 12, 2015 at 9:32 am
I have someone that wants to install Sql Server Core on a new Server.
He states that the major benefits of using Core is reducing the management\operational overhead on the server as well as reducing the attack surface of the server.
He also states that anything that can be done in SSMS can be done using sqlcmd.exe on the server.
How do you feel about that? I would think it would reduce functionality and increase the time that it take to recover etc.
You input would be greatly appreciated.
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/
June 12, 2015 at 10:00 am
My main concern is not having SSMS on the Server and the learning curve to use command line.
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/
June 12, 2015 at 10:02 am
Considering that no one should be using SSMS directly on the server anyway, that's a very minor concern.
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
June 12, 2015 at 10:05 am
So use the command line for everything?
What do you mean that is a minor one?
I only use it if the Server is not allowing remote connections.
Thanks.
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/
June 12, 2015 at 10:06 am
I meant to post this in the 2014 forum.
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/
June 12, 2015 at 10:11 am
sqlcmd.exe only? you should know better.
you can use your local SSMS GUI to connect to any version of SQL, including a remote SQL Server Core instance.
SSMS doesn't care if the engine is running on Server Core or not. it's just a connection via SQL native client, exactly the same as any other application would be doing. there is nothing special about SSMS.
the installation for SQL Core avoids installing the client tools, really.
Lowell
June 12, 2015 at 10:16 am
I misunderstood. :blush:
So you can install SSMS on the Server?
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/
June 12, 2015 at 10:21 am
Welsh Corgi (6/12/2015)
I misunderstood. :blush:So you can install SSMS on the Server?
No.
the point is there is no need to have SSMS on the server.
you already have it local, installed on your everyday woorkstation, you just connect that way.
Lowell
June 12, 2015 at 10:25 am
Didn't realize that SQL Server had a CORE version. I know that Windows Server can be installed as a core server limiting the surface area of an attack on a server by only installing those services that are needed.
June 12, 2015 at 10:34 am
Lowell (6/12/2015)
Welsh Corgi (6/12/2015)
I misunderstood. :blush:So you can install SSMS on the Server?
No.
the point is there is no need to have SSMS on the server.
you already have it local, installed on your everyday woorkstation, you just connect that way.
I have had frequent occasions where no one including could not connect via SSMS on their PC that I had to log onto the Server open up SSMS and start executing commands.
I did not intent to cause any heartburn.
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/
June 12, 2015 at 10:36 am
Welsh Corgi (6/12/2015)
So you can install SSMS on the Server?
In Server Core installation, no, but since you should never be using SSMS on the server, that's hardly a large problem.
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
June 12, 2015 at 10:38 am
Welsh Corgi (6/12/2015)
So use the command line for everything?
Hell no. Use SSMS from a client machine. There's pretty much no case I can think of where you'd need to use SSMS directly on the server, except maybe if the network was down and you had to go into the data centre and work at the console, but that should be incredibly rare.
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
June 12, 2015 at 10:41 am
Welsh Corgi (6/12/2015)
Lowell (6/12/2015)
Welsh Corgi (6/12/2015)
I misunderstood. :blush:So you can install SSMS on the Server?
No.
the point is there is no need to have SSMS on the server.
you already have it local, installed on your everyday woorkstation, you just connect that way.
I have had frequent occasions where no one including could not connect via SSMS on their PC that I had to log onto the Server open up SSMS and start executing commands.
I did not intent to cause any heartburn.
Did that include using DAC (Dedicated Admin Connection)?
June 12, 2015 at 10:44 am
I can't speak for anyone else and I'm sure that it will rub some folks' sensibilities the wrong way but I do install the full monty on my servers and it has saved my keester a couple of times when the only way in was by RDC (and, no... sorry, I don't remember the exact details. It was quite a while ago).
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2015 at 10:48 am
GilaMonster (6/12/2015)
Welsh Corgi (6/12/2015)
So use the command line for everything?Hell no. Use SSMS from a client machine. There's pretty much no case I can think of where you'd need to use SSMS directly on the server, except maybe if the network was down and you had to go into the data centre and work at the console, but that should be incredibly rare.
That is what I'm talking about. The rare situations. Use SSMS only in a rare situation.
I sure that you will correct me if I'm wrong but my understanding is that if you have SQL Server core you can't install SSMS on the Server.
Thank you.
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/
Viewing 15 posts - 1 through 15 (of 50 total)
You must be logged in to reply to this topic. Login to reply