Merge replication and Domain Controller

Hi,
A few questions on merge replication and domain controller. We are using MS
SQL 2005 and Windows Server 2003.
1. Is domain controller a must for merge replication? Does performing
replication using Integrated Windows Authentication essentially has the same
effect as with a domain controller?
2. If merge replication is to be done with a domain controller, which method
of authentication, SQL Server Authentication or Integrated Windows
Authentication, can/should be used for replication? What are the advantages
of one over the other, if any?
3. I understand that MS does not recommend running SQL Server 2005 on a
domain controller. Having said that, this would mean we need to separate the
two. But we have the constraint of having only one machine. Is there any
workaround for this, that is, performing merge replication and achieving the
function of a domain controller but with only one machine?
My apologies if I am not making sense as I am not too familiar with these.
Would appreciate any help on this. Thanks in advance.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"AimlessZombie" <AimlessZombie@.discussions.microsoft.com> wrote in message
news:09DB05F1-288D-4489-BFEF-2CB09FAF7E8B@.microsoft.com...
> Hi,
> A few questions on merge replication and domain controller. We are using
> MS
> SQL 2005 and Windows Server 2003.
> 1. Is domain controller a must for merge replication? Does performing
> replication using Integrated Windows Authentication essentially has the
> same
> effect as with a domain controller?
> 2. If merge replication is to be done with a domain controller, which
> method
> of authentication, SQL Server Authentication or Integrated Windows
> Authentication, can/should be used for replication? What are the
> advantages
> of one over the other, if any?
> 3. I understand that MS does not recommend running SQL Server 2005 on a
> domain controller. Having said that, this would mean we need to separate
> the
> two. But we have the constraint of having only one machine. Is there any
> workaround for this, that is, performing merge replication and achieving
> the
> function of a domain controller but with only one machine?
> My apologies if I am not making sense as I am not too familiar with these.
> Would appreciate any help on this. Thanks in advance.
|||Dear Aimless zombie.
1) No, you can use local machine accounts with pass through authentication
or use sql authentication.
2) you can use either sql authentication or integrated authentication. SQL
Authentication is intended for replicating between untrusted domains or
heterogeneous applications. Integrated authentication is more secure.
3) You don't need a domain controller.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"AimlessZombie" <AimlessZombie@.discussions.microsoft.com> wrote in message
news:09DB05F1-288D-4489-BFEF-2CB09FAF7E8B@.microsoft.com...
> Hi,
> A few questions on merge replication and domain controller. We are using
> MS
> SQL 2005 and Windows Server 2003.
> 1. Is domain controller a must for merge replication? Does performing
> replication using Integrated Windows Authentication essentially has the
> same
> effect as with a domain controller?
> 2. If merge replication is to be done with a domain controller, which
> method
> of authentication, SQL Server Authentication or Integrated Windows
> Authentication, can/should be used for replication? What are the
> advantages
> of one over the other, if any?
> 3. I understand that MS does not recommend running SQL Server 2005 on a
> domain controller. Having said that, this would mean we need to separate
> the
> two. But we have the constraint of having only one machine. Is there any
> workaround for this, that is, performing merge replication and achieving
> the
> function of a domain controller but with only one machine?
> My apologies if I am not making sense as I am not too familiar with these.
> Would appreciate any help on this. Thanks in advance.
|||Hi Hilary,
Thanks for the prompt help. Just a couple more questions with respect to
your replies.
1) Can either pass through authentication or use sql authentication achieve
the role of a domain controller? Or is there no basis for comparison at all
in the first place?
3) What if I must have a domain controller (part of requirement) but yet
only one machine available? Is there no workaround to my constraint to have
both domain controller and replication?
Thanks.
"Hilary Cotter" wrote:

> Dear Aimless zombie.
> 1) No, you can use local machine accounts with pass through authentication
> or use sql authentication.
> 2) you can use either sql authentication or integrated authentication. SQL
> Authentication is intended for replicating between untrusted domains or
> heterogeneous applications. Integrated authentication is more secure.
> 3) You don't need a domain controller.
>
> --
> http://www.zetainteractive.com - Shift Happens!
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "AimlessZombie" <AimlessZombie@.discussions.microsoft.com> wrote in message
> news:09DB05F1-288D-4489-BFEF-2CB09FAF7E8B@.microsoft.com...
>
>
|||Dear Aimless Zombie
1) Can either pass through authentication or use sql authentication achieve
the role of a domain controller? Or is there no basis for comparison at all
in the first place?
No a domain controller is primarily used to authenticate users. You will not
be able to add local machine accounts to a domain controller, so you will
need to add domain accounts. You can still use pass through authentication
as long as the subscriber has a local machine account with the same name and
password. It is not recommended that you install SQL Server on a domain
controller as if SQL Server is compromised your entire domain will be.
3) What if I must have a domain controller (part of requirement) but yet
only one machine available? Is there no workaround to my constraint to have
both domain controller and replication?
You can install SQL Server on your domain controller but it is considered to
be a security risk.
I am not sure what you are doing, but I think you will make life simpler for
yourself if you use push subscriptions.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"AimlessZombie" <AimlessZombie@.discussions.microsoft.com> wrote in message
news:76DC30CD-7E60-4EEC-8736-3661788DDCDC@.microsoft.com...[vbcol=seagreen]
> Hi Hilary,
> Thanks for the prompt help. Just a couple more questions with respect to
> your replies.
> 1) Can either pass through authentication or use sql authentication
> achieve
> the role of a domain controller? Or is there no basis for comparison at
> all
> in the first place?
> 3) What if I must have a domain controller (part of requirement) but yet
> only one machine available? Is there no workaround to my constraint to
> have
> both domain controller and replication?
> Thanks.
> "Hilary Cotter" wrote: