January 4, 2012 at 4:56 am
Hi,
Right now server is ready with operating system - windows 2008 32 bit, Disk configuration etc..
currently server is work-group, N/W has been configured and server is not member of domain.
After few days server is comes to production environment that time these are parameter have to be changed for server name, added the domain, New IP address etc..
I want to know, Could anyone suggestion me for the best practice for SQL 2K8 Enterprise Edition before work-group stage or after production environment and configured complete once new server name, domain, IP address etc..
If installed SQL2K8 in work-group stage, after that I have to change the server name, change the IP address and all...
thanks
ananda
January 4, 2012 at 5:44 am
I would not suggest installing SQL Server if you're going to be changing the server name, etc. Get the server set up and configured, then install SQL Server. You'll have a lot fewer headaches that way.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2012 at 9:02 am
ananda.murugesan (1/4/2012)
Hi,Right now server is ready with operating system - windows 2008 32 bit, Disk configuration etc..
currently server is work-group, N/W has been configured and server is not member of domain.
After few days server is comes to production environment that time these are parameter have to be changed for server name, added the domain, New IP address etc..
I want to know, Could anyone suggestion me for the best practice for SQL 2K8 Enterprise Edition before work-group stage or after production environment and configured complete once new server name, domain, IP address etc..
If installed SQL2K8 in work-group stage, after that I have to change the server name, change the IP address and all...
thanks
ananda
If all you're doing is joining the server to a domain then it won't make any difference whether you install SQL Server before or after. The same is true for the IP address, if you install SQL Server and then change the IP address it won't make to much difference. However, you may want to get the machine on the domain and set up\patched appropriately before attempting to install\configure SQL Server.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 4, 2012 at 2:53 pm
Perry Whittle (1/4/2012)
If all you're doing is joining the server to a domain then it won't make any difference whether you install SQL Server before or after. The same is true for the IP address, if you install SQL Server and then change the IP address it won't make to much difference. However, you may want to get the machine on the domain and set up\patched appropriately before attempting to install\configure SQL Server.
I will disagree here - just with installing SQL Server before joining to the domain. If you do that, then you won't be able to use a domain service account and will have to modify the service account after the installation. Although that can be done fairly easily, you will definitely end up with an orphaned SPN record that could cause problems with windows authentication to SQL Server.
Also, if you change the server name - you have to remember to change the server name in SQL Server also.
Just easier if you wait until after joining the server to the domain. Less hassles...
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
January 4, 2012 at 3:15 pm
Jeffrey Williams 3188 (1/4/2012)
Perry Whittle (1/4/2012)
If all you're doing is joining the server to a domain then it won't make any difference whether you install SQL Server before or after. The same is true for the IP address, if you install SQL Server and then change the IP address it won't make to much difference. However, you may want to get the machine on the domain and set up\patched appropriately before attempting to install\configure SQL Server.I will disagree here - just with installing SQL Server before joining to the domain. If you do that, then you won't be able to use a domain service account and will have to modify the service account after the installation. Although that can be done fairly easily, you will definitely end up with an orphaned SPN record that could cause problems with windows authentication to SQL Server.
Also, if you change the server name - you have to remember to change the server name in SQL Server also.
Just easier if you wait until after joining the server to the domain. Less hassles...
Hmm it's pretty trivial though, it's no great shakes changing the service account. At the end of the day there's a small amount of config work, nothing to major though, nothing that would require you to uninstall and then reinstall SQL Server 😉
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 8, 2012 at 4:21 am
@jeffrey, Although that can be done fairly easily, you will definitely end up with an orphaned SPN record that could cause problems with windows authentication to SQL Server.
Shouldn't manually re registiring SPN fix it up? It is a fairly quick task as well.
Regards,
Raj
January 9, 2012 at 3:35 am
You can definitely install SQL Server while your server is in Workgroup mode and then make the necessary changes after it is put into Domain mode. You can also bang your head against a wall for 10 minutes. Both these things are possible, but not advisable.
If you want to get the quickest and most robust SQL Server installation, wait until your server is joined to te domain and has its correct name, IP address and access to domain-level accounts.
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
January 9, 2012 at 5:45 am
Perry Whittle (1/4/2012)
Jeffrey Williams 3188 (1/4/2012)
Perry Whittle (1/4/2012)
If all you're doing is joining the server to a domain then it won't make any difference whether you install SQL Server before or after. The same is true for the IP address, if you install SQL Server and then change the IP address it won't make to much difference. However, you may want to get the machine on the domain and set up\patched appropriately before attempting to install\configure SQL Server.I will disagree here - just with installing SQL Server before joining to the domain. If you do that, then you won't be able to use a domain service account and will have to modify the service account after the installation. Although that can be done fairly easily, you will definitely end up with an orphaned SPN record that could cause problems with windows authentication to SQL Server.
Also, if you change the server name - you have to remember to change the server name in SQL Server also.
Just easier if you wait until after joining the server to the domain. Less hassles...
Hmm it's pretty trivial though, it's no great shakes changing the service account. At the end of the day there's a small amount of config work, nothing to major though, nothing that would require you to uninstall and then reinstall SQL Server 😉
I agree that it's not hard work, but I'm a lazy SOB and don't see any reason to do the work twice, easy or not. That's my main argument for getting everything configured first, then doing the install. Less pain, less rework, more laziness.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply