Do mirrored servers have to be in same domain?

hi,
Can someone tell me if servers participating in SQL 2005 database mirroring
have to be in the same domain or can they just be stand alone servers? I
can't seem to find any documentation about this.
Thanks.No.
In case if the domain account for any of the server is different for example
the domain account for mirror server is different than the domain account of
the principal or the witness server then you can use the following statement
to grant permissions to the endpoint to that domain account: (You will need
to run the below statement on all the three participating servers)
Use Master; Create Login [Domain\Domain_user_account] From Windows; Gran
t
Connect on EndPoint ::Mirroring_Endpoint to [Domain\Domain_user_account]
;
Thanks,
Sree
[Please specify the version of Sql Server as we can save one thread and
time
asking back if its 2000 or 2005]
"Steve" wrote:

> hi,
> Can someone tell me if servers participating in SQL 2005 database mirrorin
g
> have to be in the same domain or can they just be stand alone servers? I
> can't seem to find any documentation about this.
> Thanks.
>

Do mirrored servers have to be in same domain?

hi,
Can someone tell me if servers participating in SQL 2005 database mirroring
have to be in the same domain or can they just be stand alone servers? I
can't seem to find any documentation about this.
Thanks.No.
In case if the domain account for any of the server is different for example
the domain account for mirror server is different than the domain account of
the principal or the witness server then you can use the following statement
to grant permissions to the endpoint to that domain account: (You will need
to run the below statement on all the three participating servers)
Use Master; Create Login [Domain\Domain_user_account] From Windows; Grant
Connect on EndPoint ::Mirroring_Endpoint to [Domain\Domain_user_account];
Thanks,
Sree
[Please specify the version of Sql Server as we can save one thread and time
asking back if its 2000 or 2005]
"Steve" wrote:
> hi,
> Can someone tell me if servers participating in SQL 2005 database mirroring
> have to be in the same domain or can they just be stand alone servers? I
> can't seem to find any documentation about this.
> Thanks.
>

do I need a domain in order to run a cluster?

Hi, I am a complete newbie with windows clustering -
still reading the white papers etc. From what I have read
it seems that I need a Windows Domain in order to run
clustering. Is this true? Is there any way I can cluster
SQL server without having to setup a domain?
thanks
christos
Yes. You must have a domain to run a cluster. No, you can't get around
having a domain.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Christos Kritikos" <anonymous@.discussions.microsoft.com> wrote in message
news:030001c49b56$400d9060$a301280a@.phx.gbl...
> Hi, I am a complete newbie with windows clustering -
> still reading the white papers etc. From what I have read
> it seems that I need a Windows Domain in order to run
> clustering. Is this true? Is there any way I can cluster
> SQL server without having to setup a domain?
> thanks
> christos
>
|||Hi Geoff,
I too have the same doubt. What are some Technical
reasons forcing cluster to run in a domain?
Thanks
Chip.
>--Original Message--
>Yes. You must have a domain to run a cluster. No, you
can't get around
>having a domain.
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>I support the Professional Association for SQL Server
>www.sqlpass.org
>"Christos Kritikos"
<anonymous@.discussions.microsoft.com> wrote in message[vbcol=seagreen]
>news:030001c49b56$400d9060$a301280a@.phx.gbl...
read[vbcol=seagreen]
cluster
>
>.
>
|||You have to have a common security context for the cluster service to manage
resources on multiple machines. Parallel usernames and paswords will not
work. You have to have a domain (NT4 or AD) to provide cluster-wide access
to resources.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Chip" <anonymous@.discussions.microsoft.com> wrote in message
news:150e01c49c9d$f0cd9560$a301280a@.phx.gbl...[vbcol=seagreen]
> Hi Geoff,
> I too have the same doubt. What are some Technical
> reasons forcing cluster to run in a domain?
> Thanks
> Chip.
> can't get around
> <anonymous@.discussions.microsoft.com> wrote in message
> read
> cluster
|||There is some good information in
281662 Windows 2000 and Windows Server 2003 Cluster Nodes As Domain Controllers
http://support.microsoft.com/?id=281662
Here is a section from the same.
To have Windows Clustering function properly (where the Cluster service starts on each node) the node that forms the cluster must be able to validate the Cluster service domain account, which is the account that you
configure during the Windows Clustering installation. To accomplish this, each node must be able to establish a secure channel with a domain controller to validate this account. If the node cannot validate the
account, the Cluster service does not start. This is also true for other clustered programs that must have account validation for services to start, such as Microsoft SQL Server and Microsoft Exchange.
If you have a cluster deployment in which there is no link with either a Windows NT 4.0 domain, a Windows 2000 domain, or a Windows Server 2003 domain, you must configure the cluster nodes as domain
controllers so that the Cluster service account can always be validated to allow for proper cluster functionality.
If the connectivity between cluster nodes and domain controllers is such that the link is either slow or unreliable, consider having a domain controller co-located with the cluster, or configuring the cluster nodes as
domain controllers.
Consider the following important points when you are deploying Windows Clustering nodes as domain controllers:
--> See the above KB (http://support.microsoft.com/?id=281662)
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Thanks Geoff & Uttam.
Chip
>--Original Message--
>There is some good information in
>281662 Windows 2000 and Windows Server 2003 Cluster Nodes
As Domain Controllers
>http://support.microsoft.com/?id=281662
>Here is a section from the same.
>To have Windows Clustering function properly (where the
Cluster service starts on each node) the node that forms
the cluster must be able to validate the Cluster service
domain account, which is the account that you
>configure during the Windows Clustering installation. To
accomplish this, each node must be able to establish a
secure channel with a domain controller to validate this
account. If the node cannot validate the
>account, the Cluster service does not start. This is also
true for other clustered programs that must have account
validation for services to start, such as Microsoft SQL
Server and Microsoft Exchange.
>If you have a cluster deployment in which there is no
link with either a Windows NT 4.0 domain, a Windows 2000
domain, or a Windows Server 2003 domain, you must
configure the cluster nodes as domain
>controllers so that the Cluster service account can
always be validated to allow for proper cluster
functionality.
>If the connectivity between cluster nodes and domain
controllers is such that the link is either slow or
unreliable, consider having a domain controller co-located
with the cluster, or configuring the cluster nodes as
>domain controllers.
>Consider the following important points when you are
deploying Windows Clustering nodes as domain controllers:
> --> See the above KB
(http://support.microsoft.com/?id=281662)
>Best Regards,
>Uttam Parui
>Microsoft Corporation
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>Are you secure? For information about the Strategic
Technology Protection Program and to order your FREE
Security Tool Kit, please visit
http://www.microsoft.com/security.
>Microsoft highly recommends that users with Internet
access update their Microsoft software to better protect
against viruses and security vulnerabilities. The easiest
way to do this is to visit the following websites:
>http://www.microsoft.com/protect
>http://www.microsoft.com/security/guidance/default.mspx
>
>.
>

Distrubuting ODBC DSN record to domain computers

How Can i distrubute my ODBC DSN record to my domain computers?DSN definitions are kept in registry, so you can distribute related registry
entries and push them to clients
Google points to lots of examples (search for DSN registry)
<volkans80@.gmail.com> wrote in message
news:1181386496.822173.150260@.h2g2000hsg.googlegroups.com...
> How Can i distrubute my ODBC DSN record to my domain computers?
>|||Thanks

Distrubuting ODBC DSN record to domain computers

How Can i distrubute my ODBC DSN record to my domain computers?
DSN definitions are kept in registry, so you can distribute related registry
entries and push them to clients
Google points to lots of examples (search for DSN registry)
<volkans80@.gmail.com> wrote in message
news:1181386496.822173.150260@.h2g2000hsg.googlegro ups.com...
> How Can i distrubute my ODBC DSN record to my domain computers?
>
|||Thanks

Distributed transaction

We had 3 SQL servers (S1, S2, S3). S1 and S3 are in the same domain. both S2
and S3 have views that link to S1. Recently we replaced S1 with S11. Now, we
can run views in S2 and S3 however we cannot modify the views in S2 or add
new views linked to S11.
Actually, we can modify the views and run them but when we tried to save the
changes, this error message will show up:
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The operation
could not be performed because the OLE DB provider 'SQLOLEDB' was unable to
begin a distributed transaction.
[Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB provider returned
message: New transaction cannot enlist in the specific transaction
coordinator.]
[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace [OLE/DB
Provider 'SQLOLEDB' ITransactionJoinTransaction returned 0x8004d00a].
What should we do to fix this?
All servers run Windows 2000 and SQL 2000.
Thanks.
Hello lwidjaya,
sounds like your using the EM tool for these changes, I would suggest using
query analyzer for this.
there are a number of things that might cause this issue, so you need to
know what is different configuration wise from s1 and s11, so do an inventor
of security and setup.
John Vandervliet...
"lwidjaya" wrote:

> We had 3 SQL servers (S1, S2, S3). S1 and S3 are in the same domain. both S2
> and S3 have views that link to S1. Recently we replaced S1 with S11. Now, we
> can run views in S2 and S3 however we cannot modify the views in S2 or add
> new views linked to S11.
> Actually, we can modify the views and run them but when we tried to save the
> changes, this error message will show up:
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The operation
> could not be performed because the OLE DB provider 'SQLOLEDB' was unable to
> begin a distributed transaction.
> [Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB provider returned
> message: New transaction cannot enlist in the specific transaction
> coordinator.]
> [Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace [OLE/DB
> Provider 'SQLOLEDB' ITransactionJoinTransaction returned 0x8004d00a].
> What should we do to fix this?
> All servers run Windows 2000 and SQL 2000.
> Thanks.
|||Hi John,
thanks for your reply.
Our IT guy just found out what happened. He needs to add the server name and
ip address in the hosts file in winnt folder.
Lisa
"John Vandervliet" wrote:
[vbcol=seagreen]
> Hello lwidjaya,
> sounds like your using the EM tool for these changes, I would suggest using
> query analyzer for this.
> there are a number of things that might cause this issue, so you need to
> know what is different configuration wise from s1 and s11, so do an inventor
> of security and setup.
> John Vandervliet...
> "lwidjaya" wrote:

Distributed transaction

We had 3 SQL servers (S1, S2, S3). S1 and S3 are in the same domain. both S2
and S3 have views that link to S1. Recently we replaced S1 with S11. Now, we
can run views in S2 and S3 however we cannot modify the views in S2 or add
new views linked to S11.
Actually, we can modify the views and run them but when we tried to save the
changes, this error message will show up:
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The o
peration
could not be performed because the OLE DB provider 'SQLOLEDB' was unable to
begin a distributed transaction.
[Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB provi
der returned
message: New transaction cannot enlist in the specific transaction
coordinator.]
[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trac
e [OLE/DB
Provider 'SQLOLEDB' ITransactionJoinTransaction returned 0x8004d00a].
What should we do to fix this?
All servers run Windows 2000 and SQL 2000.
Thanks.Hello lwidjaya,
sounds like your using the EM tool for these changes, I would suggest using
query analyzer for this.
there are a number of things that might cause this issue, so you need to
know what is different configuration wise from s1 and s11, so do an inventor
of security and setup.
John Vandervliet...
"lwidjaya" wrote:

> We had 3 SQL servers (S1, S2, S3). S1 and S3 are in the same domain. both
S2
> and S3 have views that link to S1. Recently we replaced S1 with S11. Now,
we
> can run views in S2 and S3 however we cannot modify the views in S2 or add
> new views linked to S11.
> Actually, we can modify the views and run them but when we tried to save t
he
> changes, this error message will show up:
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The
operation
> could not be performed because the OLE DB provider 'SQLOLEDB' was unable t
o
> begin a distributed transaction.
> [Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB pro
vider returned
> message: New transaction cannot enlist in the specific transaction
> coordinator.]
> [Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error tr
ace [OLE/DB
> Provider 'SQLOLEDB' ITransactionJoinTransaction returned 0x8004d00a].
> What should we do to fix this?
> All servers run Windows 2000 and SQL 2000.
> Thanks.|||Hi John,
thanks for your reply.
Our IT guy just found out what happened. He needs to add the server name and
ip address in the hosts file in winnt folder.
Lisa
"John Vandervliet" wrote:
[vbcol=seagreen]
> Hello lwidjaya,
> sounds like your using the EM tool for these changes, I would suggest usin
g
> query analyzer for this.
> there are a number of things that might cause this issue, so you need to
> know what is different configuration wise from s1 and s11, so do an invent
or
> of security and setup.
> John Vandervliet...
> "lwidjaya" wrote:
>

Distributed transaction

We had 3 SQL servers (S1, S2, S3). S1 and S3 are in the same domain. both S2
and S3 have views that link to S1. Recently we replaced S1 with S11. Now, we
can run views in S2 and S3 however we cannot modify the views in S2 or add
new views linked to S11.
Actually, we can modify the views and run them but when we tried to save the
changes, this error message will show up:
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The operation
could not be performed because the OLE DB provider 'SQLOLEDB' was unable to
begin a distributed transaction.
[Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB provider returned
message: New transaction cannot enlist in the specific transaction
coordinator.]
[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace [OLE/DB
Provider 'SQLOLEDB' ITransactionJoinTransaction returned 0x8004d00a].
What should we do to fix this?
All servers run Windows 2000 and SQL 2000.
Thanks.Hello lwidjaya,
sounds like your using the EM tool for these changes, I would suggest using
query analyzer for this.
there are a number of things that might cause this issue, so you need to
know what is different configuration wise from s1 and s11, so do an inventor
of security and setup.
John Vandervliet...
"lwidjaya" wrote:
> We had 3 SQL servers (S1, S2, S3). S1 and S3 are in the same domain. both S2
> and S3 have views that link to S1. Recently we replaced S1 with S11. Now, we
> can run views in S2 and S3 however we cannot modify the views in S2 or add
> new views linked to S11.
> Actually, we can modify the views and run them but when we tried to save the
> changes, this error message will show up:
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The operation
> could not be performed because the OLE DB provider 'SQLOLEDB' was unable to
> begin a distributed transaction.
> [Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB provider returned
> message: New transaction cannot enlist in the specific transaction
> coordinator.]
> [Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace [OLE/DB
> Provider 'SQLOLEDB' ITransactionJoinTransaction returned 0x8004d00a].
> What should we do to fix this?
> All servers run Windows 2000 and SQL 2000.
> Thanks.|||Hi John,
thanks for your reply.
Our IT guy just found out what happened. He needs to add the server name and
ip address in the hosts file in winnt folder.
Lisa
"John Vandervliet" wrote:
> Hello lwidjaya,
> sounds like your using the EM tool for these changes, I would suggest using
> query analyzer for this.
> there are a number of things that might cause this issue, so you need to
> know what is different configuration wise from s1 and s11, so do an inventor
> of security and setup.
> John Vandervliet...
> "lwidjaya" wrote:
> > We had 3 SQL servers (S1, S2, S3). S1 and S3 are in the same domain. both S2
> > and S3 have views that link to S1. Recently we replaced S1 with S11. Now, we
> > can run views in S2 and S3 however we cannot modify the views in S2 or add
> > new views linked to S11.
> > Actually, we can modify the views and run them but when we tried to save the
> > changes, this error message will show up:
> > ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The operation
> > could not be performed because the OLE DB provider 'SQLOLEDB' was unable to
> > begin a distributed transaction.
> > [Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB provider returned
> > message: New transaction cannot enlist in the specific transaction
> > coordinator.]
> > [Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace [OLE/DB
> > Provider 'SQLOLEDB' ITransactionJoinTransaction returned 0x8004d00a].
> >
> > What should we do to fix this?
> >
> > All servers run Windows 2000 and SQL 2000.
> >
> > Thanks.