Sql Server Core vs Full blown version of SQL Server

Question

Sql Server Core vs Full blown version of SQL Server

Viewing 15 posts - 16 through 30 (of 50 total)

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

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

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

There isn't anything called SQL Server Core. There is Windows Server Core which doesn't install the GUI interface for Windows Server and allows you to install only the services you require for each specific server.

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

Lynn,

Thanks for the feedback.

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

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

I was not referring to local SSMS. Sometimes SSMS Times out on the client and no one can connect from their.

I remote into the Server, launch SSMS and can easily detect and correct the problem. Running command line command take a lot longer and is not intuitive.

You can't install any windows application on Server Core.

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 4

I got my way. Server Core is out.

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 5

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

Thank you Jeff. Sounds like you can relate to what my situation would be would be like. You understand.

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 6

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/

DeWayne_McCallie Hall of Fame Points: 3617 More actions · Answer 7

Lynn Pettis (6/12/2015)
Welsh Corgi (6/12/2015)
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.
There isn't anything called SQL Server Core. There is Windows Server Core which doesn't install the GUI interface for Windows Server and allows you to install only the services you require for each specific server.

Sure there is: SQL Server 2014 Enterprise Core Edition

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

DeWayne_McCallie (6/16/2015)
Lynn Pettis (6/12/2015)
Welsh Corgi (6/12/2015)
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.
There isn't anything called SQL Server Core. There is Windows Server Core which doesn't install the GUI interface for Windows Server and allows you to install only the services you require for each specific server.
Sure there is: SQL Server 2014 Enterprise Core Edition

Nope, there is Core Licensing, but there is no SQL Server Enterprise Core Edition.

DeWayne_McCallie Hall of Fame Points: 3617 More actions · Answer 9

Wow I'm on the MSDN download site and there is a download with that name (I have already downloaded it). I must be tripping!

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

DeWayne_McCallie (6/16/2015)
Wow I'm on the MSDN download site and there is a download with that name (I have already downloaded it). I must be tripping!

I'll ask it this way. Why would you need a Core Edition when you basically get that by not installing the client tools (SSMS for one)?

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 11

DeWayne_McCallie (6/16/2015)
Wow I'm on the MSDN download site and there is a download with that name (I have already downloaded it). I must be tripping!

You're right, there is.

It's Core-licensing (as opposed to server + CAL). Not the same as Server Core, which is the GUI-less version of Windows.

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

DeWayne_McCallie Hall of Fame Points: 3617 More actions · Answer 12

Thanks for clearing that up Gail and no disrespect meant Lynn!

Here is the actual current DL Name on MSDN: "SQL Server 2014 Enterprise Core Edition with Service Pack 1 (x64) - DVD (English)"

Also, to install on CORE since there is no GUI it's parm command line time:

https://msdn.microsoft.com/en-us/library/hh231669.aspx

Eric M Russell SSC Guru Points: 125563 More actions · Answer 13

Welsh Corgi (6/12/2015)
I got my way. Server Core is out.

Maybe installing SQL Server on a Windows Core server is a good idea. Like you said, it reduces the surface area for attack. I'm not sure if there are performance benefits, but Windows Core does consume less memory, there are less windows services competing for CPU, and there is less opportunity for App and BI team to install their own fluff and stuff on it.

Thomas LaRock wrote an article on administering SQL Server on a Windows Core Server using SSMS.

http://thomaslarock.com/2013/03/administering-sql-server-running-on-server-core/

As for remote administration using SSMS, you can keep admin accounts to a minimum, disable mssql browser service, allow only connections via IP address, and nail down the firewall, etc.

"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 14

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

Thank you.

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 to power shell.

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 15

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.