IS it OK to promote an SQL Server to a Domain Controller?

I'm running a Windows 2000 stand alone server with SQL Server 2000 on it. I
need to promote this Server to a Domain Controller for a new domain. I
won't be renaming the server as I know this can cause problems with the SQL
Server (unless it can be easily done).
What kind of problems would I run into? Any steps that need to be followed?
Running DCPromo to create a new Domain should copy the local User database
into the new Domain correct?
ThanksMichael,
From SQL 7.0, this article describes some consequences:
http://msdn.microsoft.com/library/en-us/dnsql7/html/sql7security.asp?frame=true
However, this article suggest that you not do that if you have a choice.
http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/dnnetsec/html/thcmch18.asp
Russell Fields
"Michael" <no@.no.com> wrote in message
news:OeEOCu4rDHA.2392@.TK2MSFTNGP10.phx.gbl...
> I'm running a Windows 2000 stand alone server with SQL Server 2000 on it.
I
> need to promote this Server to a Domain Controller for a new domain. I
> won't be renaming the server as I know this can cause problems with the
SQL
> Server (unless it can be easily done).
> What kind of problems would I run into? Any steps that need to be
followed?
> Running DCPromo to create a new Domain should copy the local User database
> into the new Domain correct?
> Thanks
>|||Hi Michael,
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with your issue.
From your description, I understand that you would like to promote you SQL 2000 Server to a
Domain Controller for a new domain. However, you didn't point out the target of this promotion.
Based on my experience, if you promote a SQL Server to a new domain, the most common
problem you will face is orphan logins and some login permission problems. You can use
sp_grantlogin to manually add the logins into the new domain, and use sp_grantdbaccess to
associate the group members with a user identifier (ID) in each database they need to
access.
Here I provide you with a simple example:
============================USE master
GO
-- Authorize all members of NETDOMAIN\Managers to connect
-- using Windows Authentication.
sp_grantlogin 'NETDOMAIN\Managers'
GO
-- Make pubs the default database for Michael and Northwind the default database for Billy.
sp_defaultdb 'NETDOMAIN\Michael', 'pubs'
sp_defaultdb 'NETDOMAIN\Billy', 'Northwind'
USE pubs
GO
-- Grant a specific member Michael of the group access to
-- pubs with a specific user.
sp_grantdbaccess 'NETDOMAIN\Michael', 'Michael'
USE Northwind
GO
-- Grant a specific member Billy of the group access to
-- Northwind with a specific user.
sp_grantdbaccess 'NETDOMAIN\Billy', 'Billy'
=============================
As to renaming the server, there is also an easy way to perform like that:
-- For a default instance:
sp_dropserver <old_servername>
go
sp_addserver <new_servername> , local
go
-- For a named instance:
sp_dropserver <old_servername\instancename>
go
sp_addserver <new_servername\instancename> , local
go
Michael, does this answer your question? Please apply my suggestion above and let me
know if it helps you resolve your problem.
For more information, you can reference the following articles:
240872 HOW TO: Resolve Permission Issues When You Move a Database Between
http://support.microsoft.com/?id=240872
246133 HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
http://support.microsoft.com/?id=246133
Best regards,
Billy Yao
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.