Sql Server Core vs Full blown version of SQL Server

Question

Sql Server Core vs Full blown version of SQL Server

Viewing 15 posts - 31 through 45 (of 50 total)

You must be logged in to reply to this topic. Login to reply

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 1

I have had many occasions here I could not connect to SQL Server and I had to make a remote connection to the Server to resolve the issue.

Why make it so complicated. Yes you can use power shell but I want to get the Server up fast without entering a bunch of commands.

This is a no brainer. Install the client as a last resort.

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/

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 2

dan-572483 (12/9/2015)
While I usually use SSMS from my workstation there are a few occasions where I'm happy it was on a server:
1) During an evening power outage at the office my workstation was not on UPS so I could not remote to it from home. Fortunately, I knew of one server where SSMS was installed (our standard practice is to not install it) and I was able to remote in and do my work (on a different server).
2) If you have a mix of different versions of SQL and tend to use SQL instances until the end of Extended Support. During a recent project to migrate everything off of Windows 2003, I discovered there are a couple things you can't do on a SQL 2005 instance using SSMS 2012. Fortunately, the instance I referred to in my first example was SQL 2005 so I was able to accomplish everything using that. Since Compatibility Level 90 is not supported in SQL 2014, I would not be confident managing a SQL 2005 instance with SSMS 2014. Will you be able to manage a 2008 Instance with SSMS 2016? I wouldn't count on it.
So it is a good idea to have places other than your workstation to manage SQL.

I agree with you.

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/

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 3

Install SSMS, Configuration Manager , etc

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/

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 4

GilaMonster (6/12/2015)
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.

I think that it is stupid to not to have the functionality of the GUI is a major liability.

How many commands do you need to execute to identify the problem?

A non GUI environment is not the best choice.

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/

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 5

Welsh Corgi (12/9/2015)
GilaMonster (6/12/2015)
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.
I think that it is stupid to not to have the functionality of the GUI is a major liability.
How many commands do you need to execute to identify the problem?
A non GUI environment is not the best choice.

You should consider it from a security standpoint as well. The smaller the attack surface on the server the harder to breach the server. Using server core to host SQL Server instance(s) actually makes sense from that aspect.

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 6

Lynn Pettis (12/10/2015)
Welsh Corgi (12/9/2015)
GilaMonster (6/12/2015)
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.
I think that it is stupid to not to have the functionality of the GUI is a major liability.
How many commands do you need to execute to identify the problem?
A non GUI environment is not the best choice.
You should consider it from a security standpoint as well. The smaller the attack surface on the server the harder to breach the server. Using server core to host SQL Server instance(s) actually makes sense from that aspect.

I have considered the Security implications but I do not want it.

Too much of a hassle to administer.

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/

dan-572483 SSCoach Points: 15870 More actions · Answer 7

I have joked before that I can offer perfect security by removing the hard drives and putting them in a vault.

Security is always a balance between making access extremely difficult for people who shouldn't have it while at the same time making it simple and easy for those who should have it.

Eric M Russell SSC Guru Points: 125561 More actions · Answer 8

Welsh Corgi (12/9/2015)
GilaMonster (6/12/2015)
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.
I think that it is stupid to not to have the functionality of the GUI is a major liability.
How many commands do you need to execute to identify the problem?
A non GUI environment is not the best choice.

Regardless of the SQL Server edition, there is no GUI component of the database engine. You can manage Core Edition using SSMS installed on the client. You just can't run or install SSMS directly on the server.

"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 9

Yes, I know that can not install the Client tools on the Server and that you can only install it on a Client.

The problem is that the client would time out so I had to remote in to the Server to find out what was going wrong and fix the problem.

For that reason I'm against installing the core 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/

Mike Hinds SSCarpal Tunnel Points: 4258 More actions · Answer 10

What I haven't seen mentioned is the solution my organization uses:

Have a dedicated (to the DBAs) terminal server where SSMS, Profiler, et al, are installed. Then run SSMS (and other tools) as a Remote App. I do this to manage all (nearly 300) visible instances of SQL. (Invisible includes those in DMZs, and those in our UAT that is accessible through a VPN).

Regards,

- Mike

Mike Hinds Lead Database Administrator1st Source BankMCP, MCTS

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 11

Mike Hinds (12/11/2015)
What I haven't seen mentioned is the solution my organization uses:
Have a dedicated (to the DBAs) terminal server where SSMS, Profiler, et al, are installed. Then run SSMS (and other tools) as a Remote App. I do this to manage all (nearly 300) visible instances of SQL. (Invisible includes those in DMZs, and those in our UAT that is accessible through a VPN).
Regards,
- Mike

That sounds good but the problem is there are times when I can't establish a remote connection and I have to REmote into the Server and log into SSMS to identify and resolve the issue.

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/

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 12

Here is how I look at it. If the people who build, create, and maintain the servers (physical or virtual) have decided to install Windows Server Core on the servers and only add those services that are needed on that server (SQL Server, file share, ftp, web, print server, etc.) then you need to learn to work with them, not against them. They are in the same boat you are when it comes to managing the servers. If they want to use a GUI interface it has to connect remotely. If that doesn't work and they have to connect directly to the server they have to use command line access as well.

They are trying to reduce the surface area of attack on their servers, and reduce the complexity of maintenance (patch management, etc.). Learn the SQL that you need to identify and resolve issues using either SQLCMD or PowerShell.

Also, make sure the DAC connection is enabled. Many times when a SQL Server instance becomes unresponsive to a remote SSMS connection, you can still connect a remote SSMS query window to that server using the DAC connection (that is what it is there for by the way). You'll still need to run queries to identify and resolve the issue(s).

Help yourself, learn more about SQL Server and how to troubleshoot issues without a GUI. You may find yourself working someplace where they don't use Windows Server Core but prohibit installing any client tools on production servers.

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 13

I'm not working against anyone.

I just wanted opinions.

We have already made a compromise so this is a non issue.

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/

Eric M Russell SSC Guru Points: 125561 More actions · Answer 14

Welsh Corgi (12/14/2015)
I'm not working against anyone.
I just wanted options.
We have already made a compromise so this is a non issue.
Thanks.

What is the compromise; are they installing Core Edition?

"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 15

Core edition on the Test Server Enterprise on the Production 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/