Promoting SQL Server to a Domain Controller?

Does anyone have any thoughts or have tried to promote a Win2k Server running SQL Standard to a Domain controller using dcpromo? Should this be done? have you done or tried this? What are the issues? Thank you for your response in advance.
Ric
I think this is a really bad idea. (Performance, security, etc)
WHY do you want to do this out of curiuosity?
Greg Jackson
PDX, Oregon
|||Why would you want to? Is the server underutilized in your opinion? Do you
not have enough hardware? What do you have for a DHCP, DNS, and WINS server?
Generally it is better to keep application servers (which SQL Server is) and
domain servers separate due to resource issues associated with the two
different usages.
Andrew C. Madsen
Information Architect
Harley-Davidson Motor Company
"Ric" <Ric@.discussions.microsoft.com> wrote in message
news:68217993-6559-4F7F-9B12-54AA0443F315@.microsoft.com...
> Does anyone have any thoughts or have tried to promote a Win2k Server
running SQL Standard to a Domain controller using dcpromo? Should this be
done? have you done or tried this? What are the issues? Thank you for
your response in advance.
> Ric
|||We would be using this as the secondary domain controller. (Backup to our main domain controller in case of it failing. No other reason)
"Jaxon" wrote:

> I think this is a really bad idea. (Performance, security, etc)
> WHY do you want to do this out of curiuosity?
>
> Greg Jackson
> PDX, Oregon
>
>
|||We would be using this as the secondary domain controller. (Backup to our main domain controller in case of it failing. No other reason)
"Andrew Madsen" wrote:

> Why would you want to? Is the server underutilized in your opinion? Do you
> not have enough hardware? What do you have for a DHCP, DNS, and WINS server?
> Generally it is better to keep application servers (which SQL Server is) and
> domain servers separate due to resource issues associated with the two
> different usages.
> --
> Andrew C. Madsen
> Information Architect
> Harley-Davidson Motor Company
> "Ric" <Ric@.discussions.microsoft.com> wrote in message
> news:68217993-6559-4F7F-9B12-54AA0443F315@.microsoft.com...
> running SQL Standard to a Domain controller using dcpromo? Should this be
> done? have you done or tried this? What are the issues? Thank you for
> your response in advance.
>
>
|||There is no longer a "Backup Domain" controller concept in AD anymore. They
are all peers and therefore do the same amount of work. Unless you don't
transfer the global catalog. So I would advise against it because you would
potentially have the same issues accessing domain resources if SQL server
was doing some heavy processing and acting as a DC.
Andrew C. Madsen
Information Architect
Harley-Davidson Motor Company
"Ric" <Ric@.discussions.microsoft.com> wrote in message
news:681154C6-23E2-43E7-9EC6-BA5F3CCAA2D3@.microsoft.com...
> We would be using this as the secondary domain controller. (Backup to our
main domain controller in case of it failing. No other reason)[vbcol=seagreen]
> "Andrew Madsen" wrote:
you[vbcol=seagreen]
server?[vbcol=seagreen]
and[vbcol=seagreen]
be[vbcol=seagreen]

Promoting SQL Server to a Domain Controller?

Does anyone have any thoughts or have tried to promote a Win2k Server runnin
g SQL Standard to a Domain controller using dcpromo? Should this be done?
have you done or tried this? What are the issues? Thank you for your respo
nse in advance.
RicI think this is a really bad idea. (Performance, security, etc)
WHY do you want to do this out of curiuosity?
Greg Jackson
PDX, Oregon|||Why would you want to? Is the server underutilized in your opinion? Do you
not have enough hardware? What do you have for a DHCP, DNS, and WINS server?
Generally it is better to keep application servers (which SQL Server is) and
domain servers separate due to resource issues associated with the two
different usages.
Andrew C. Madsen
Information Architect
Harley-Davidson Motor Company
"Ric" <Ric@.discussions.microsoft.com> wrote in message
news:68217993-6559-4F7F-9B12-54AA0443F315@.microsoft.com...
> Does anyone have any thoughts or have tried to promote a Win2k Server
running SQL Standard to a Domain controller using dcpromo? Should this be
done? have you done or tried this? What are the issues? Thank you for
your response in advance.
> Ric|||We would be using this as the secondary domain controller. (Backup to our ma
in domain controller in case of it failing. No other reason)
"Jaxon" wrote:

> I think this is a really bad idea. (Performance, security, etc)
> WHY do you want to do this out of curiuosity?
>
> Greg Jackson
> PDX, Oregon
>
>|||We would be using this as the secondary domain controller. (Backup to our ma
in domain controller in case of it failing. No other reason)
"Andrew Madsen" wrote:

> Why would you want to? Is the server underutilized in your opinion? Do you
> not have enough hardware? What do you have for a DHCP, DNS, and WINS serve
r?
> Generally it is better to keep application servers (which SQL Server is) a
nd
> domain servers separate due to resource issues associated with the two
> different usages.
> --
> Andrew C. Madsen
> Information Architect
> Harley-Davidson Motor Company
> "Ric" <Ric@.discussions.microsoft.com> wrote in message
> news:68217993-6559-4F7F-9B12-54AA0443F315@.microsoft.com...
> running SQL Standard to a Domain controller using dcpromo? Should this be
> done? have you done or tried this? What are the issues? Thank you for
> your response in advance.
>
>|||There is no longer a "Backup Domain" controller concept in AD anymore. They
are all peers and therefore do the same amount of work. Unless you don't
transfer the global catalog. So I would advise against it because you would
potentially have the same issues accessing domain resources if SQL server
was doing some heavy processing and acting as a DC.
Andrew C. Madsen
Information Architect
Harley-Davidson Motor Company
"Ric" <Ric@.discussions.microsoft.com> wrote in message
news:681154C6-23E2-43E7-9EC6-BA5F3CCAA2D3@.microsoft.com...
> We would be using this as the secondary domain controller. (Backup to our
main domain controller in case of it failing. No other reason)[vbcol=seagreen]
> "Andrew Madsen" wrote:
>
you[vbcol=seagreen]
server?[vbcol=seagreen]
and[vbcol=seagreen]
be[vbcol=seagreen]

Promoting DTS pacakages

Environment: SQL Server 2000

I have made a few DTS packages (in testing environment). Now I have to promote them to production environment. Whats the best way to do this? One of the ways I can think of is save the DTS packages in visual basic format and go through the VB code and check for any dependent variables etc. But once a DTS packages is saved as VB code it cant be saved back as a package. So how would you use the DTS package (in VB code) on SQL Server 2000.Open the package in Design.

Click Package, Save As...

Select the server you would like to save the package to.

Open it on the new server and check for dependencies.

That's all there is to it.|||Hi!

For transferring a DTS-Package from one Server to another or for Backup purposes I use a little free tool called "DTSBackup 2000". You can find the description and the download link on the following page (http://www.sqldts.com/?242).

Hope that makes it easier!
Greetings,
Carsten|||Originally posted by CarstenK
Hi!

For transferring a DTS-Package from one Server to another or for Backup purposes I use a little free tool called "DTSBackup 2000". You can find the description and the download link on the following page (http://www.sqldts.com/?242).

Hope that makes it easier!
Greetings,
Carsten

Thanks, the software helped me out.