May 21, 2008 at 7:45 pm
We have an environment running SQL 2005 Std SP2 (9.0.3042) with Reporting and Analysis services which is currently on a workgroup server (O/S Win 2003 R2 SP2).
We need to join this server to a Window 2003 Active directory domain?
What (if any) elements are likely to cause problems for SQL2005 as a result of this join process ? What might break and what can we do to work around those issues?
As a roll back strategy, is it possible to "disjoin" this server from the domain and what would the impact be on SQL 2005.
May 21, 2008 at 10:05 pm
I haven't tried it myself, but you shouldn't have any problems. SQL only logins will be unaffected (not dependent on Windows at all), SQL logins from local Windows accounts will be unaffected.
Be aware of any group memberships that may grant people rights to SQL Server you don't want them to have. Domain Admins gets added to the local Administrators group, for example, so if you have BUILTIN\Administrators in your SQL logins, any domain administrator will end up with rights to SQL Server (sysadmin by default, depends how you have done your security). Domain Users may get added to the Users group as well, will pay to check.
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
May 21, 2008 at 10:14 pm
That's what I thought as well but according to Microsoft advisories if we move a server from WorkGroup to AD Member server will break the SQL 2005.
I am still dubious about Microsoft remarks.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply