Domain Controller and SQL Server 2005

Hi All,
I have a quick question.
Can I have Domain Controller, file server and SQL Server 2005 on the
same machine?
What are the pros and cons? Can I use the same machine as SQL
Mirroring?
I really do appreciate your suggestions.
Thanks a million in advance.
Best regards,
MamunHi
Ideally SQL Server should be on it's own server and not have to compete for
resources with other activities, for instance you would even remove
unnecessary services etc, you would also design your system for high
throughput of I/O and split disc access across as many discs as possible for
instance using mutiple data files and splitting the log and data files onto
different physical discs.
Saying that, if your database access is not high and your budgets do not
stretch to having a dedicated server, there are products like SBS which allo
w
you to purchase most of the systems you would require; although ultimately
you may want to graduate to separate systems the initial cost is reduced.
John
"mamun" wrote:

> Hi All,
> I have a quick question.
> Can I have Domain Controller, file server and SQL Server 2005 on the
> same machine?
> What are the pros and cons? Can I use the same machine as SQL
> Mirroring?
> I really do appreciate your suggestions.
> Thanks a million in advance.
> Best regards,
> Mamun
>

Domain Controller and SQL Server 2005

Hi All,
I have a quick question.
Can I have Domain Controller, file server and SQL Server 2005 on the
same machine?
What are the pros and cons? Can I use the same machine as SQL
Mirroring?
I really do appreciate your suggestions.
Thanks a million in advance.
Best regards,
Mamun
Hi
Ideally SQL Server should be on it's own server and not have to compete for
resources with other activities, for instance you would even remove
unnecessary services etc, you would also design your system for high
throughput of I/O and split disc access across as many discs as possible for
instance using mutiple data files and splitting the log and data files onto
different physical discs.
Saying that, if your database access is not high and your budgets do not
stretch to having a dedicated server, there are products like SBS which allow
you to purchase most of the systems you would require; although ultimately
you may want to graduate to separate systems the initial cost is reduced.
John
"mamun" wrote:

> Hi All,
> I have a quick question.
> Can I have Domain Controller, file server and SQL Server 2005 on the
> same machine?
> What are the pros and cons? Can I use the same machine as SQL
> Mirroring?
> I really do appreciate your suggestions.
> Thanks a million in advance.
> Best regards,
> Mamun
>

Domain Controller and SQL Server 2005

Hi All,
I have a quick question.
Can I have Domain Controller, file server and SQL Server 2005 on the
same machine?
What are the pros and cons? Can I use the same machine as SQL
Mirroring?
I really do appreciate your suggestions.
Thanks a million in advance.
Best regards,
MamunHi
Ideally SQL Server should be on it's own server and not have to compete for
resources with other activities, for instance you would even remove
unnecessary services etc, you would also design your system for high
throughput of I/O and split disc access across as many discs as possible for
instance using mutiple data files and splitting the log and data files onto
different physical discs.
Saying that, if your database access is not high and your budgets do not
stretch to having a dedicated server, there are products like SBS which allow
you to purchase most of the systems you would require; although ultimately
you may want to graduate to separate systems the initial cost is reduced.
John
"mamun" wrote:
> Hi All,
> I have a quick question.
> Can I have Domain Controller, file server and SQL Server 2005 on the
> same machine?
> What are the pros and cons? Can I use the same machine as SQL
> Mirroring?
> I really do appreciate your suggestions.
> Thanks a million in advance.
> Best regards,
> Mamun
>

Domain Auth from Nondomain Computer

Hi,
We have our SQL Server 2000 Ent. Ed. SP3 set up to use Windows
authentication from a Windows Server 2003 domain controller running Active
Directory in Windows 2000 compatibility mode. From the office, everything
is hunky-dory. However, we have many employees that need to connect to the
office network via point-to-point and site-to-site VPN where the remote
computer/network is not a member of our domain.
Is there any way to get a non-domain Windows 2000/XP computer to domain
authenticate against SQL Server with the user's domain credentials? I
really don't want to have to manage a bunch of SQL Server authentication
usernames, passwords and username-by-username permissioning.
Thank you,
Daniel Jameson
SQL Server DBA
Children's Oncology Group
www.childrensoncologygroup.org
Hi
If you map a network drive, using domain credntials, against the SQL Server,
when the SQL Connection is made, those same credentials will be passed if NT
Integrated security is used.
It is a work-around and will not work if you use Active Directory with
Kerberos security enabled.
Regards
Mike
"Daniel Jameson" wrote:

> Hi,
> We have our SQL Server 2000 Ent. Ed. SP3 set up to use Windows
> authentication from a Windows Server 2003 domain controller running Active
> Directory in Windows 2000 compatibility mode. From the office, everything
> is hunky-dory. However, we have many employees that need to connect to the
> office network via point-to-point and site-to-site VPN where the remote
> computer/network is not a member of our domain.
> Is there any way to get a non-domain Windows 2000/XP computer to domain
> authenticate against SQL Server with the user's domain credentials? I
> really don't want to have to manage a bunch of SQL Server authentication
> usernames, passwords and username-by-username permissioning.
> --
> Thank you,
> Daniel Jameson
> SQL Server DBA
> Children's Oncology Group
> www.childrensoncologygroup.org
>
>

Domain Auth from Nondomain Computer

Hi,
We have our SQL Server 2000 Ent. Ed. SP3 set up to use Windows
authentication from a Windows Server 2003 domain controller running Active
Directory in Windows 2000 compatibility mode. From the office, everything
is hunky-dory. However, we have many employees that need to connect to the
office network via point-to-point and site-to-site VPN where the remote
computer/network is not a member of our domain.
Is there any way to get a non-domain Windows 2000/XP computer to domain
authenticate against SQL Server with the user's domain credentials? I
really don't want to have to manage a bunch of SQL Server authentication
usernames, passwords and username-by-username permissioning.
Thank you,
Daniel Jameson
SQL Server DBA
Children's Oncology Group
www.childrensoncologygroup.orgHi
If you map a network drive, using domain credntials, against the SQL Server,
when the SQL Connection is made, those same credentials will be passed if NT
Integrated security is used.
It is a work-around and will not work if you use Active Directory with
Kerberos security enabled.
Regards
Mike
"Daniel Jameson" wrote:

> Hi,
> We have our SQL Server 2000 Ent. Ed. SP3 set up to use Windows
> authentication from a Windows Server 2003 domain controller running Active
> Directory in Windows 2000 compatibility mode. From the office, everything
> is hunky-dory. However, we have many employees that need to connect to th
e
> office network via point-to-point and site-to-site VPN where the remote
> computer/network is not a member of our domain.
> Is there any way to get a non-domain Windows 2000/XP computer to domain
> authenticate against SQL Server with the user's domain credentials? I
> really don't want to have to manage a bunch of SQL Server authentication
> usernames, passwords and username-by-username permissioning.
> --
> Thank you,
> Daniel Jameson
> SQL Server DBA
> Children's Oncology Group
> www.childrensoncologygroup.org
>
>