April 5, 2014 at 6:50 am
Hi Friends,
I have very limited knowledge on this topic. I have worked and working on SQL servers on the machines that are on domain. e.g. 100 servers we have and they are on xyz domain.
So please help me to understand if the windows boxes are on workgroup instead of domain. SQL Server will work like it was working on a machine on domain or will there be any problem.
What are the limitations if we move the servers from domain to workgroup?
thanks,
DKG
April 6, 2014 at 11:44 pm
From the security and connectivity perspective it would be good to keep sql servers on domain. If it's on work group connectivity will be an issue.
Why you are keen to move 100 servers to workgroup? Have you collected the info why 100 servers are on this domain? Contact your AD admin who will clarify your doubts better.
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
April 8, 2014 at 5:24 am
free_mascot (4/6/2014)
From the security and connectivity perspective it would be good to keep sql servers on domain.
Not necessarily, security can still be implemented effectively on workgroup computers, it's just harder to manage.
free_mascot (4/6/2014)
If it's on work group connectivity will be an issue.
Again, harder to manage in a workgroup, but not an issue as such.
See this thread for more on this duplicate post.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 8, 2014 at 10:39 pm
Perry Whittle (4/8/2014)
free_mascot (4/6/2014)
From the security and connectivity perspective it would be good to keep sql servers on domain.Not necessarily, security can still be implemented effectively on workgroup computers, it's just harder to manage.
free_mascot (4/6/2014)
If it's on work group connectivity will be an issue.Again, harder to manage in a workgroup, but not an issue as such.
See this thread for more on this duplicate post.
Yes, I mean by ease of management and managibility. In industry if 99% are using domain and 1% are using workgroup for production environment (hypothetical data) than there are some logic behind it.
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
April 11, 2014 at 2:55 am
SQL Server in a Workgroup has some advantages if it is used in an automatic scale-out scenario, such as in a cloud environment.
Connecting a Windows box to a Domain takes a certain amount of time to complete, and has a requirement that all servers use unique names. If you are trying to do automatic scale-out then setting up the domain connection is a bottleneck.
If the server is just a Workgroup server then all scale-out servers can use the same base image and have the same name. All that is needed is that they get their own IP address, which is relatively easy to manage. There is a knock-on impact that SQL Authentication is the easiest way to manage security in this situation, but if you want fast scale-out and scale-back then Workgroup servers may be the right way to go.
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
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply