I though 2005 was going to have a feature where you could face multiple
instances of a DB towards your customers with all the lock and transaction
bits accomplished in the background? The most common question I get about
Clustering is whether it is HA or really is a scalibility solution as well.
Avokia makes a piece that effectively accomplishes this.Are you referring to database snapshots?
Adam Machanic
SQL Server MVP
http://www.datamanipulation.net
--
"Jeffrey K. Ericson" <JeffreyKEricson@.discussions.microsoft.com> wrote in
message news:2C6CD6C9-2655-4E5F-8DD7-83B21DE43F12@.microsoft.com...
> I though 2005 was going to have a feature where you could face multiple
> instances of a DB towards your customers with all the lock and transaction
> bits accomplished in the background? The most common question I get about
> Clustering is whether it is HA or really is a scalibility solution as
well.
> Avokia makes a piece that effectively accomplishes this.|||Hi
Clustering is HA and no Windows Clustering implantation is intended for
scale out.
SQL server 2005 has never has a scale out feature in it's feature list.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Jeffrey K. Ericson" <JeffreyKEricson@.discussions.microsoft.com> wrote in
message news:2C6CD6C9-2655-4E5F-8DD7-83B21DE43F12@.microsoft.com...
>I though 2005 was going to have a feature where you could face multiple
> instances of a DB towards your customers with all the lock and transaction
> bits accomplished in the background? The most common question I get about
> Clustering is whether it is HA or really is a scalibility solution as
> well.
> Avokia makes a piece that effectively accomplishes this.|||Database mirroring seems to be like what I thought I heard 2005 to have.
This would be more like having a separate server instance to improve
performance.
"Adam Machanic" wrote:
> Are you referring to database snapshots?
>
> --
> Adam Machanic
> SQL Server MVP
> http://www.datamanipulation.net
> --
>
> "Jeffrey K. Ericson" <JeffreyKEricson@.discussions.microsoft.com> wrote in
> message news:2C6CD6C9-2655-4E5F-8DD7-83B21DE43F12@.microsoft.com...
> > I though 2005 was going to have a feature where you could face multiple
> > instances of a DB towards your customers with all the lock and transaction
> > bits accomplished in the background? The most common question I get about
> > Clustering is whether it is HA or really is a scalibility solution as
> well.
> > Avokia makes a piece that effectively accomplishes this.
>
>|||Database mirroring, with a snapshot running against the mirror gives you a
real-time read only copy of the data.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Jeffrey K. Ericson" <JeffreyKEricson@.discussions.microsoft.com> wrote in
message news:D22D9678-ACC0-4A67-B9B0-ECB89990694E@.microsoft.com...
> Database mirroring seems to be like what I thought I heard 2005 to have.
> This would be more like having a separate server instance to improve
> performance.
> "Adam Machanic" wrote:
>> Are you referring to database snapshots?
>>
>> --
>> Adam Machanic
>> SQL Server MVP
>> http://www.datamanipulation.net
>> --
>>
>> "Jeffrey K. Ericson" <JeffreyKEricson@.discussions.microsoft.com> wrote in
>> message news:2C6CD6C9-2655-4E5F-8DD7-83B21DE43F12@.microsoft.com...
>> > I though 2005 was going to have a feature where you could face multiple
>> > instances of a DB towards your customers with all the lock and
>> > transaction
>> > bits accomplished in the background? The most common question I get
>> > about
>> > Clustering is whether it is HA or really is a scalibility solution as
>> well.
>> > Avokia makes a piece that effectively accomplishes this.
>>|||As Mike mentioned, database mirroring really doesn't accomplish that.
Sounds like a merge replication scenario to me...
Adam Machanic
SQL Server MVP
http://www.datamanipulation.net
--
"Jeffrey K. Ericson" <JeffreyKEricson@.discussions.microsoft.com> wrote in
message news:D22D9678-ACC0-4A67-B9B0-ECB89990694E@.microsoft.com...
> Database mirroring seems to be like what I thought I heard 2005 to have.
> This would be more like having a separate server instance to improve
> performance.
> "Adam Machanic" wrote:
> > Are you referring to database snapshots?
> >
> >
> > --
> > Adam Machanic
> > SQL Server MVP
> > http://www.datamanipulation.net
> > --
> >
> >
> > "Jeffrey K. Ericson" <JeffreyKEricson@.discussions.microsoft.com> wrote
in
> > message news:2C6CD6C9-2655-4E5F-8DD7-83B21DE43F12@.microsoft.com...
> > > I though 2005 was going to have a feature where you could face
multiple
> > > instances of a DB towards your customers with all the lock and
transaction
> > > bits accomplished in the background? The most common question I get
about
> > > Clustering is whether it is HA or really is a scalibility solution as
> > well.
> > > Avokia makes a piece that effectively accomplishes this.
> >
> >
> >
Showing posts with label instances. Show all posts
Showing posts with label instances. Show all posts
Friday, February 24, 2012
Thursday, February 16, 2012
2005 Internal Functions
There are several instances where I've seen this sort of thing:
%%ColumnEx(ObjectID = @.object_id, Name =
@.identity_column).SetIdentityNotForRepl(Value = @.value).
Anyone know what the full syntax is, where they are listed, if we can take
advantage of them etc?
TIA
Those are, as you noted, internal functions -- they are undocumented and
available only within the scope of the resource database. I haven't seen
anything yet, but I'm sure at some point someone will figure out how to hack
SQL Server to get a full list of them -- it's only a matter of time
Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
"JB" <JB@.Acme.Com> wrote in message
news:OujsIr2IGHA.3452@.TK2MSFTNGP12.phx.gbl...
> There are several instances where I've seen this sort of thing:
> %%ColumnEx(ObjectID = @.object_id, Name =
> @.identity_column).SetIdentityNotForRepl(Value = @.value).
> Anyone know what the full syntax is, where they are listed, if we can take
> advantage of them etc?
> TIA
>
|||I think that the proc sp_identitycolumnforreplication will do what you are
looking for. These system calls are only executable by system processes. You
may be able to find references to them in the system stored procedures and
functions. I don't know how to call them.
Hilary Cotter
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
"JB" <JB@.Acme.Com> wrote in message
news:OujsIr2IGHA.3452@.TK2MSFTNGP12.phx.gbl...
> There are several instances where I've seen this sort of thing:
> %%ColumnEx(ObjectID = @.object_id, Name =
> @.identity_column).SetIdentityNotForRepl(Value = @.value).
> Anyone know what the full syntax is, where they are listed, if we can take
> advantage of them etc?
> TIA
>
|||And even if someone does, they are undocumented for a reason. There is no
guarantee they will function the same from one hotfix to another let alone
one service pack to another. What are you trying to do?
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:uM7vn42IGHA.1180@.TK2MSFTNGP09.phx.gbl...
> Those are, as you noted, internal functions -- they are undocumented and
> available only within the scope of the resource database. I haven't seen
> anything yet, but I'm sure at some point someone will figure out how to
> hack SQL Server to get a full list of them -- it's only a matter of time
>
>
> --
> Adam Machanic
> Pro SQL Server 2005, available now
> http://www.apress.com/book/bookDisplay.html?bID=457
> --
>
> "JB" <JB@.Acme.Com> wrote in message
> news:OujsIr2IGHA.3452@.TK2MSFTNGP12.phx.gbl...
>
%%ColumnEx(ObjectID = @.object_id, Name =
@.identity_column).SetIdentityNotForRepl(Value = @.value).
Anyone know what the full syntax is, where they are listed, if we can take
advantage of them etc?
TIA
Those are, as you noted, internal functions -- they are undocumented and
available only within the scope of the resource database. I haven't seen
anything yet, but I'm sure at some point someone will figure out how to hack
SQL Server to get a full list of them -- it's only a matter of time

Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
"JB" <JB@.Acme.Com> wrote in message
news:OujsIr2IGHA.3452@.TK2MSFTNGP12.phx.gbl...
> There are several instances where I've seen this sort of thing:
> %%ColumnEx(ObjectID = @.object_id, Name =
> @.identity_column).SetIdentityNotForRepl(Value = @.value).
> Anyone know what the full syntax is, where they are listed, if we can take
> advantage of them etc?
> TIA
>
|||I think that the proc sp_identitycolumnforreplication will do what you are
looking for. These system calls are only executable by system processes. You
may be able to find references to them in the system stored procedures and
functions. I don't know how to call them.
Hilary Cotter
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
"JB" <JB@.Acme.Com> wrote in message
news:OujsIr2IGHA.3452@.TK2MSFTNGP12.phx.gbl...
> There are several instances where I've seen this sort of thing:
> %%ColumnEx(ObjectID = @.object_id, Name =
> @.identity_column).SetIdentityNotForRepl(Value = @.value).
> Anyone know what the full syntax is, where they are listed, if we can take
> advantage of them etc?
> TIA
>
|||And even if someone does, they are undocumented for a reason. There is no
guarantee they will function the same from one hotfix to another let alone
one service pack to another. What are you trying to do?
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:uM7vn42IGHA.1180@.TK2MSFTNGP09.phx.gbl...
> Those are, as you noted, internal functions -- they are undocumented and
> available only within the scope of the resource database. I haven't seen
> anything yet, but I'm sure at some point someone will figure out how to
> hack SQL Server to get a full list of them -- it's only a matter of time
>

>
> --
> Adam Machanic
> Pro SQL Server 2005, available now
> http://www.apress.com/book/bookDisplay.html?bID=457
> --
>
> "JB" <JB@.Acme.Com> wrote in message
> news:OujsIr2IGHA.3452@.TK2MSFTNGP12.phx.gbl...
>
2005 Internal Functions
There are several instances where I've seen this sort of thing:
%%ColumnEx(ObjectID = @.object_id, Name = @.identity_column).SetIdentityNotForRepl(Value = @.value).
Anyone know what the full syntax is, where they are listed, if we can take
advantage of them etc?
TIAThose are, as you noted, internal functions -- they are undocumented and
available only within the scope of the resource database. I haven't seen
anything yet, but I'm sure at some point someone will figure out how to hack
SQL Server to get a full list of them -- it's only a matter of time :)
Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
--
"JB" <JB@.Acme.Com> wrote in message
news:OujsIr2IGHA.3452@.TK2MSFTNGP12.phx.gbl...
> There are several instances where I've seen this sort of thing:
> %%ColumnEx(ObjectID = @.object_id, Name => @.identity_column).SetIdentityNotForRepl(Value = @.value).
> Anyone know what the full syntax is, where they are listed, if we can take
> advantage of them etc?
> TIA
>|||I think that the proc sp_identitycolumnforreplication will do what you are
looking for. These system calls are only executable by system processes. You
may be able to find references to them in the system stored procedures and
functions. I don't know how to call them.
Hilary Cotter
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
"JB" <JB@.Acme.Com> wrote in message
news:OujsIr2IGHA.3452@.TK2MSFTNGP12.phx.gbl...
> There are several instances where I've seen this sort of thing:
> %%ColumnEx(ObjectID = @.object_id, Name => @.identity_column).SetIdentityNotForRepl(Value = @.value).
> Anyone know what the full syntax is, where they are listed, if we can take
> advantage of them etc?
> TIA
>|||And even if someone does, they are undocumented for a reason. There is no
guarantee they will function the same from one hotfix to another let alone
one service pack to another. What are you trying to do?
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:uM7vn42IGHA.1180@.TK2MSFTNGP09.phx.gbl...
> Those are, as you noted, internal functions -- they are undocumented and
> available only within the scope of the resource database. I haven't seen
> anything yet, but I'm sure at some point someone will figure out how to
> hack SQL Server to get a full list of them -- it's only a matter of time
> :)
>
> --
> Adam Machanic
> Pro SQL Server 2005, available now
> http://www.apress.com/book/bookDisplay.html?bID=457
> --
>
> "JB" <JB@.Acme.Com> wrote in message
> news:OujsIr2IGHA.3452@.TK2MSFTNGP12.phx.gbl...
>> There are several instances where I've seen this sort of thing:
>> %%ColumnEx(ObjectID = @.object_id, Name =>> @.identity_column).SetIdentityNotForRepl(Value = @.value).
>> Anyone know what the full syntax is, where they are listed, if we can
>> take advantage of them etc?
>> TIA
>>
>
%%ColumnEx(ObjectID = @.object_id, Name = @.identity_column).SetIdentityNotForRepl(Value = @.value).
Anyone know what the full syntax is, where they are listed, if we can take
advantage of them etc?
TIAThose are, as you noted, internal functions -- they are undocumented and
available only within the scope of the resource database. I haven't seen
anything yet, but I'm sure at some point someone will figure out how to hack
SQL Server to get a full list of them -- it's only a matter of time :)
Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
--
"JB" <JB@.Acme.Com> wrote in message
news:OujsIr2IGHA.3452@.TK2MSFTNGP12.phx.gbl...
> There are several instances where I've seen this sort of thing:
> %%ColumnEx(ObjectID = @.object_id, Name => @.identity_column).SetIdentityNotForRepl(Value = @.value).
> Anyone know what the full syntax is, where they are listed, if we can take
> advantage of them etc?
> TIA
>|||I think that the proc sp_identitycolumnforreplication will do what you are
looking for. These system calls are only executable by system processes. You
may be able to find references to them in the system stored procedures and
functions. I don't know how to call them.
Hilary Cotter
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
"JB" <JB@.Acme.Com> wrote in message
news:OujsIr2IGHA.3452@.TK2MSFTNGP12.phx.gbl...
> There are several instances where I've seen this sort of thing:
> %%ColumnEx(ObjectID = @.object_id, Name => @.identity_column).SetIdentityNotForRepl(Value = @.value).
> Anyone know what the full syntax is, where they are listed, if we can take
> advantage of them etc?
> TIA
>|||And even if someone does, they are undocumented for a reason. There is no
guarantee they will function the same from one hotfix to another let alone
one service pack to another. What are you trying to do?
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:uM7vn42IGHA.1180@.TK2MSFTNGP09.phx.gbl...
> Those are, as you noted, internal functions -- they are undocumented and
> available only within the scope of the resource database. I haven't seen
> anything yet, but I'm sure at some point someone will figure out how to
> hack SQL Server to get a full list of them -- it's only a matter of time
> :)
>
> --
> Adam Machanic
> Pro SQL Server 2005, available now
> http://www.apress.com/book/bookDisplay.html?bID=457
> --
>
> "JB" <JB@.Acme.Com> wrote in message
> news:OujsIr2IGHA.3452@.TK2MSFTNGP12.phx.gbl...
>> There are several instances where I've seen this sort of thing:
>> %%ColumnEx(ObjectID = @.object_id, Name =>> @.identity_column).SetIdentityNotForRepl(Value = @.value).
>> Anyone know what the full syntax is, where they are listed, if we can
>> take advantage of them etc?
>> TIA
>>
>
2005 Internal Functions
There are several instances where I've seen this sort of thing:
%%ColumnEx(ObjectID = @.object_id, Name =
@.identity_column).SetIdentityNotForRepl(Value = @.value).
Anyone know what the full syntax is, where they are listed, if we can take
advantage of them etc?
TIAThose are, as you noted, internal functions -- they are undocumented and
available only within the scope of the resource database. I haven't seen
anything yet, but I'm sure at some point someone will figure out how to hack
SQL Server to get a full list of them -- it's only a matter of time
Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
--
"JB" <JB@.Acme.Com> wrote in message
news:OujsIr2IGHA.3452@.TK2MSFTNGP12.phx.gbl...
> There are several instances where I've seen this sort of thing:
> %%ColumnEx(ObjectID = @.object_id, Name =
> @.identity_column).SetIdentityNotForRepl(Value = @.value).
> Anyone know what the full syntax is, where they are listed, if we can take
> advantage of them etc?
> TIA
>|||I think that the proc sp_identitycolumnforreplication will do what you are
looking for. These system calls are only executable by system processes. You
may be able to find references to them in the system stored procedures and
functions. I don't know how to call them.
Hilary Cotter
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
"JB" <JB@.Acme.Com> wrote in message
news:OujsIr2IGHA.3452@.TK2MSFTNGP12.phx.gbl...
> There are several instances where I've seen this sort of thing:
> %%ColumnEx(ObjectID = @.object_id, Name =
> @.identity_column).SetIdentityNotForRepl(Value = @.value).
> Anyone know what the full syntax is, where they are listed, if we can take
> advantage of them etc?
> TIA
>|||And even if someone does, they are undocumented for a reason. There is no
guarantee they will function the same from one hotfix to another let alone
one service pack to another. What are you trying to do?
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:uM7vn42IGHA.1180@.TK2MSFTNGP09.phx.gbl...
> Those are, as you noted, internal functions -- they are undocumented and
> available only within the scope of the resource database. I haven't seen
> anything yet, but I'm sure at some point someone will figure out how to
> hack SQL Server to get a full list of them -- it's only a matter of time
>
>
> --
> Adam Machanic
> Pro SQL Server 2005, available now
> http://www.apress.com/book/bookDisplay.html?bID=457
> --
>
> "JB" <JB@.Acme.Com> wrote in message
> news:OujsIr2IGHA.3452@.TK2MSFTNGP12.phx.gbl...
>
%%ColumnEx(ObjectID = @.object_id, Name =
@.identity_column).SetIdentityNotForRepl(Value = @.value).
Anyone know what the full syntax is, where they are listed, if we can take
advantage of them etc?
TIAThose are, as you noted, internal functions -- they are undocumented and
available only within the scope of the resource database. I haven't seen
anything yet, but I'm sure at some point someone will figure out how to hack
SQL Server to get a full list of them -- it's only a matter of time

Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
--
"JB" <JB@.Acme.Com> wrote in message
news:OujsIr2IGHA.3452@.TK2MSFTNGP12.phx.gbl...
> There are several instances where I've seen this sort of thing:
> %%ColumnEx(ObjectID = @.object_id, Name =
> @.identity_column).SetIdentityNotForRepl(Value = @.value).
> Anyone know what the full syntax is, where they are listed, if we can take
> advantage of them etc?
> TIA
>|||I think that the proc sp_identitycolumnforreplication will do what you are
looking for. These system calls are only executable by system processes. You
may be able to find references to them in the system stored procedures and
functions. I don't know how to call them.
Hilary Cotter
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
"JB" <JB@.Acme.Com> wrote in message
news:OujsIr2IGHA.3452@.TK2MSFTNGP12.phx.gbl...
> There are several instances where I've seen this sort of thing:
> %%ColumnEx(ObjectID = @.object_id, Name =
> @.identity_column).SetIdentityNotForRepl(Value = @.value).
> Anyone know what the full syntax is, where they are listed, if we can take
> advantage of them etc?
> TIA
>|||And even if someone does, they are undocumented for a reason. There is no
guarantee they will function the same from one hotfix to another let alone
one service pack to another. What are you trying to do?
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:uM7vn42IGHA.1180@.TK2MSFTNGP09.phx.gbl...
> Those are, as you noted, internal functions -- they are undocumented and
> available only within the scope of the resource database. I haven't seen
> anything yet, but I'm sure at some point someone will figure out how to
> hack SQL Server to get a full list of them -- it's only a matter of time
>

>
> --
> Adam Machanic
> Pro SQL Server 2005, available now
> http://www.apress.com/book/bookDisplay.html?bID=457
> --
>
> "JB" <JB@.Acme.Com> wrote in message
> news:OujsIr2IGHA.3452@.TK2MSFTNGP12.phx.gbl...
>
Monday, February 13, 2012
2005 Failover Cluster SAN drives best practices
I have a MS SQL 2005 default installation on a Windows 2003 cluster. I
currently have two nodes and I am planning on adding more instances to
run on the other node.
First, I am not sure I have setup my existing default instance the best
way for my cluster. I currently only have one 'Physical Disk' in the
cluster group which is a LUN on our SAN. Both the data files and log
files are stored there. What is the best practice to move the logs onto
another spindle? Do I have to just create another LUN?
I am about to add a few more instances. Does each one need to have it's
own LUN?
There is a limited amount of drive letters that I can create. Is there
a way to share a LUN between instances? I seem to remember reading a
feature of 2005 that was related to this but, for the life of me, I
cannot find it again.
Any help would be appreciated!
Thank you
Karl> What is the best practice to move the logs onto
> another spindle? Do I have to just create another LUN?
You should at least put yout transaction log files on a separate LUN from
your data LUN. This doesn't guarantee that your data and log would be placed
on separate spindles inside SAN because both LUNs can be carved from the same
set of disks, but at least it gives you some separation.
> I am about to add a few more instances.
> Does each one need to have it's own LUN?
Each clustered instance will be implemented a separate cluster resource
group with its own disk resource(s). Since you can't have the same read/write
disk as two separate disk resources in different resource groups, each
clustered instance needs its own LUN.
> There is a limited amount of drive letters that I can create. Is there
> a way to share a LUN between instances?
You can't really share drive letters. But SQL2005 fully supports mounted
volumes in a cluster. These volumes don't have to be assigned separate drive
letters. As long as they are made disk resources, and are mounted under a
root drive letter, you can have multiple volumes in a resource group (or an
instance) with as few as one drive letter per instance.
Linchi
"Karl" wrote:
> I have a MS SQL 2005 default installation on a Windows 2003 cluster. I
> currently have two nodes and I am planning on adding more instances to
> run on the other node.
> First, I am not sure I have setup my existing default instance the best
> way for my cluster. I currently only have one 'Physical Disk' in the
> cluster group which is a LUN on our SAN. Both the data files and log
> files are stored there. What is the best practice to move the logs onto
> another spindle? Do I have to just create another LUN?
> I am about to add a few more instances. Does each one need to have it's
> own LUN?
> There is a limited amount of drive letters that I can create. Is there
> a way to share a LUN between instances? I seem to remember reading a
> feature of 2005 that was related to this but, for the life of me, I
> cannot find it again.
> Any help would be appreciated!
> Thank you
> Karl
>
currently have two nodes and I am planning on adding more instances to
run on the other node.
First, I am not sure I have setup my existing default instance the best
way for my cluster. I currently only have one 'Physical Disk' in the
cluster group which is a LUN on our SAN. Both the data files and log
files are stored there. What is the best practice to move the logs onto
another spindle? Do I have to just create another LUN?
I am about to add a few more instances. Does each one need to have it's
own LUN?
There is a limited amount of drive letters that I can create. Is there
a way to share a LUN between instances? I seem to remember reading a
feature of 2005 that was related to this but, for the life of me, I
cannot find it again.
Any help would be appreciated!
Thank you
Karl> What is the best practice to move the logs onto
> another spindle? Do I have to just create another LUN?
You should at least put yout transaction log files on a separate LUN from
your data LUN. This doesn't guarantee that your data and log would be placed
on separate spindles inside SAN because both LUNs can be carved from the same
set of disks, but at least it gives you some separation.
> I am about to add a few more instances.
> Does each one need to have it's own LUN?
Each clustered instance will be implemented a separate cluster resource
group with its own disk resource(s). Since you can't have the same read/write
disk as two separate disk resources in different resource groups, each
clustered instance needs its own LUN.
> There is a limited amount of drive letters that I can create. Is there
> a way to share a LUN between instances?
You can't really share drive letters. But SQL2005 fully supports mounted
volumes in a cluster. These volumes don't have to be assigned separate drive
letters. As long as they are made disk resources, and are mounted under a
root drive letter, you can have multiple volumes in a resource group (or an
instance) with as few as one drive letter per instance.
Linchi
"Karl" wrote:
> I have a MS SQL 2005 default installation on a Windows 2003 cluster. I
> currently have two nodes and I am planning on adding more instances to
> run on the other node.
> First, I am not sure I have setup my existing default instance the best
> way for my cluster. I currently only have one 'Physical Disk' in the
> cluster group which is a LUN on our SAN. Both the data files and log
> files are stored there. What is the best practice to move the logs onto
> another spindle? Do I have to just create another LUN?
> I am about to add a few more instances. Does each one need to have it's
> own LUN?
> There is a limited amount of drive letters that I can create. Is there
> a way to share a LUN between instances? I seem to remember reading a
> feature of 2005 that was related to this but, for the life of me, I
> cannot find it again.
> Any help would be appreciated!
> Thank you
> Karl
>
2005 Express Sync
Hi,
Is there any way to keep 2 SQL 2005 Express instances in Synch. I know that
SQL 2005 Express doesn't support Replication between them. What other
options do I have without upgrading to SQL 2005 Server. Any 3rd party
application or options with in 2005.
One of the SQL 2005 Express will be the "Master" and I will like to sych or
send the new that two the seconds instance. There is not update or deletes
to this database it will only have new inserts.
Thanks
Julio D
I expect that the new ADO.NET Synchronization Services API might be of some
use. It can be used between SQL Express instances (as well as other data
sources) to keep database tables in sync.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
Between now and Nov. 6th 2006 you can sign up for a substantial discount.
Look for the "Early Bird" discount checkbox on the registration form...
------
Microsoft MVP, Author, Mentor
Microsoft MVP
"Julio Delgado" <jdelgado89@.hotmail.com> wrote in message
news:OeKG$SDgHHA.1216@.TK2MSFTNGP03.phx.gbl...
> Hi,
> Is there any way to keep 2 SQL 2005 Express instances in Synch. I know
> that SQL 2005 Express doesn't support Replication between them. What other
> options do I have without upgrading to SQL 2005 Server. Any 3rd party
> application or options with in 2005.
> One of the SQL 2005 Express will be the "Master" and I will like to sych
> or send the new that two the seconds instance. There is not update or
> deletes to this database it will only have new inserts.
> Thanks
> Julio D
>
|||Bill, thanks for the info, do you know of another tool since I need it for a
current application that we have.
Thanks
Julio
"William (Bill) Vaughn" <billva@.NoSpamAtAll_betav.com> wrote in message
news:O$RHGRGgHHA.1244@.TK2MSFTNGP04.phx.gbl...
>I expect that the new ADO.NET Synchronization Services API might be of some
>use. It can be used between SQL Express instances (as well as other data
>sources) to keep database tables in sync.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> Between now and Nov. 6th 2006 you can sign up for a substantial discount.
> Look for the "Early Bird" discount checkbox on the registration form...
> ------
>
> Microsoft MVP, Author, Mentor
> Microsoft MVP
> "Julio Delgado" <jdelgado89@.hotmail.com> wrote in message
> news:OeKG$SDgHHA.1216@.TK2MSFTNGP03.phx.gbl...
>
|||I think it would be a waste of time to reinvent the wheel being created with
Synchronization Services. It's available now in CTP form. Yes, it's likely
to change between now and when it ships this fall, but it should solve your
problem.
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest books:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition) and
Hitchhiker's Guide to SQL Server 2005 Compact Edition
------
"Julio Delgado" <jdelgado89@.hotmail.com> wrote in message
news:uoHXfnTgHHA.4916@.TK2MSFTNGP06.phx.gbl...
> Bill, thanks for the info, do you know of another tool since I need it for
> a current application that we have.
> Thanks
> Julio
> "William (Bill) Vaughn" <billva@.NoSpamAtAll_betav.com> wrote in message
> news:O$RHGRGgHHA.1244@.TK2MSFTNGP04.phx.gbl...
>
|||friggin fabulous info, thanks!
I really really hate how they crippled MSDE 3.0
lol
"William (Bill) Vaughn" <billva@.NoSpamAtAll_betav.com> wrote in message
news:O$RHGRGgHHA.1244@.TK2MSFTNGP04.phx.gbl...
> I expect that the new ADO.NET Synchronization Services API might be of
some
> use. It can be used between SQL Express instances (as well as other data
> sources) to keep database tables in sync.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> Between now and Nov. 6th 2006 you can sign up for a substantial discount.
> Look for the "Early Bird" discount checkbox on the registration form...
> ----
---[vbcol=seagreen]
>
> Microsoft MVP, Author, Mentor
> Microsoft MVP
> "Julio Delgado" <jdelgado89@.hotmail.com> wrote in message
> news:OeKG$SDgHHA.1216@.TK2MSFTNGP03.phx.gbl...
other
>
|||So use SQL Server Express Edition. Frankly, I've never (as in never) seen a
documented case where the governor was the root cause of a performance
problem with MSDE.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Aaron Kempf" <akempf@.dol.wa.gov> wrote in message
news:uMyRgCCjHHA.3928@.TK2MSFTNGP03.phx.gbl...
> friggin fabulous info, thanks!
> I really really hate how they crippled MSDE 3.0
>
> lol
>
> "William (Bill) Vaughn" <billva@.NoSpamAtAll_betav.com> wrote in message
> news:O$RHGRGgHHA.1244@.TK2MSFTNGP04.phx.gbl...
> some
> rights.
> other
>
Is there any way to keep 2 SQL 2005 Express instances in Synch. I know that
SQL 2005 Express doesn't support Replication between them. What other
options do I have without upgrading to SQL 2005 Server. Any 3rd party
application or options with in 2005.
One of the SQL 2005 Express will be the "Master" and I will like to sych or
send the new that two the seconds instance. There is not update or deletes
to this database it will only have new inserts.
Thanks
Julio D
I expect that the new ADO.NET Synchronization Services API might be of some
use. It can be used between SQL Express instances (as well as other data
sources) to keep database tables in sync.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
Between now and Nov. 6th 2006 you can sign up for a substantial discount.
Look for the "Early Bird" discount checkbox on the registration form...
------
Microsoft MVP, Author, Mentor
Microsoft MVP
"Julio Delgado" <jdelgado89@.hotmail.com> wrote in message
news:OeKG$SDgHHA.1216@.TK2MSFTNGP03.phx.gbl...
> Hi,
> Is there any way to keep 2 SQL 2005 Express instances in Synch. I know
> that SQL 2005 Express doesn't support Replication between them. What other
> options do I have without upgrading to SQL 2005 Server. Any 3rd party
> application or options with in 2005.
> One of the SQL 2005 Express will be the "Master" and I will like to sych
> or send the new that two the seconds instance. There is not update or
> deletes to this database it will only have new inserts.
> Thanks
> Julio D
>
|||Bill, thanks for the info, do you know of another tool since I need it for a
current application that we have.
Thanks
Julio
"William (Bill) Vaughn" <billva@.NoSpamAtAll_betav.com> wrote in message
news:O$RHGRGgHHA.1244@.TK2MSFTNGP04.phx.gbl...
>I expect that the new ADO.NET Synchronization Services API might be of some
>use. It can be used between SQL Express instances (as well as other data
>sources) to keep database tables in sync.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> Between now and Nov. 6th 2006 you can sign up for a substantial discount.
> Look for the "Early Bird" discount checkbox on the registration form...
> ------
>
> Microsoft MVP, Author, Mentor
> Microsoft MVP
> "Julio Delgado" <jdelgado89@.hotmail.com> wrote in message
> news:OeKG$SDgHHA.1216@.TK2MSFTNGP03.phx.gbl...
>
|||I think it would be a waste of time to reinvent the wheel being created with
Synchronization Services. It's available now in CTP form. Yes, it's likely
to change between now and when it ships this fall, but it should solve your
problem.
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest books:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition) and
Hitchhiker's Guide to SQL Server 2005 Compact Edition
------
"Julio Delgado" <jdelgado89@.hotmail.com> wrote in message
news:uoHXfnTgHHA.4916@.TK2MSFTNGP06.phx.gbl...
> Bill, thanks for the info, do you know of another tool since I need it for
> a current application that we have.
> Thanks
> Julio
> "William (Bill) Vaughn" <billva@.NoSpamAtAll_betav.com> wrote in message
> news:O$RHGRGgHHA.1244@.TK2MSFTNGP04.phx.gbl...
>
|||friggin fabulous info, thanks!
I really really hate how they crippled MSDE 3.0
lol
"William (Bill) Vaughn" <billva@.NoSpamAtAll_betav.com> wrote in message
news:O$RHGRGgHHA.1244@.TK2MSFTNGP04.phx.gbl...
> I expect that the new ADO.NET Synchronization Services API might be of
some
> use. It can be used between SQL Express instances (as well as other data
> sources) to keep database tables in sync.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> Between now and Nov. 6th 2006 you can sign up for a substantial discount.
> Look for the "Early Bird" discount checkbox on the registration form...
> ----
---[vbcol=seagreen]
>
> Microsoft MVP, Author, Mentor
> Microsoft MVP
> "Julio Delgado" <jdelgado89@.hotmail.com> wrote in message
> news:OeKG$SDgHHA.1216@.TK2MSFTNGP03.phx.gbl...
other
>
|||So use SQL Server Express Edition. Frankly, I've never (as in never) seen a
documented case where the governor was the root cause of a performance
problem with MSDE.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Aaron Kempf" <akempf@.dol.wa.gov> wrote in message
news:uMyRgCCjHHA.3928@.TK2MSFTNGP03.phx.gbl...
> friggin fabulous info, thanks!
> I really really hate how they crippled MSDE 3.0
>
> lol
>
> "William (Bill) Vaughn" <billva@.NoSpamAtAll_betav.com> wrote in message
> news:O$RHGRGgHHA.1244@.TK2MSFTNGP04.phx.gbl...
> some
> rights.
> other
>
Saturday, February 11, 2012
2005 Cluster linked server issue
We have a two node cluster with two SQL 2005 instances installed. For the
most part things work. This morning we had Instance1 on Node1 & Instance2 on
Node2. When I created a linked server on Instance1 pointed at Instance2
(under the aforementioned node conditions) & set the security context to use
the current login's security context, it didn't do that. Instead when linked
server commands were issued, it tried to connect to Instance2 using NT
AUTHORITY\ANONYMOUS LOGON.
When we put both Instance1 & Instance2 on Node1, everything works. When we
put both Instance1 & Instance2 on Node2, everything works. But when the
instances are on different nodes, the linked server stuff gets screwy.
Anyone have any ideas? Another thing I'll throw in is that I only get
the error when connecting to Instance1 from another machine (my
workstation, app server, etc.) & running a linked server query. When I
connect to Instance1 locally on that box, the linked server query
performs fine. It's almost as if when my windows credentials travel
from my workstation to Node1 and then to Node2, things get messed
up...
CB wrote:
> We have a two node cluster with two SQL 2005 instances installed. For the
> most part things work. This morning we had Instance1 on Node1 & Instance2 on
> Node2. When I created a linked server on Instance1 pointed at Instance2
> (under the aforementioned node conditions) & set the security context to use
> the current login's security context, it didn't do that. Instead when linked
> server commands were issued, it tried to connect to Instance2 using NT
> AUTHORITY\ANONYMOUS LOGON.
> When we put both Instance1 & Instance2 on Node1, everything works. When we
> put both Instance1 & Instance2 on Node2, everything works. But when the
> instances are on different nodes, the linked server stuff gets screwy.
most part things work. This morning we had Instance1 on Node1 & Instance2 on
Node2. When I created a linked server on Instance1 pointed at Instance2
(under the aforementioned node conditions) & set the security context to use
the current login's security context, it didn't do that. Instead when linked
server commands were issued, it tried to connect to Instance2 using NT
AUTHORITY\ANONYMOUS LOGON.
When we put both Instance1 & Instance2 on Node1, everything works. When we
put both Instance1 & Instance2 on Node2, everything works. But when the
instances are on different nodes, the linked server stuff gets screwy.
Anyone have any ideas? Another thing I'll throw in is that I only get
the error when connecting to Instance1 from another machine (my
workstation, app server, etc.) & running a linked server query. When I
connect to Instance1 locally on that box, the linked server query
performs fine. It's almost as if when my windows credentials travel
from my workstation to Node1 and then to Node2, things get messed
up...
CB wrote:
> We have a two node cluster with two SQL 2005 instances installed. For the
> most part things work. This morning we had Instance1 on Node1 & Instance2 on
> Node2. When I created a linked server on Instance1 pointed at Instance2
> (under the aforementioned node conditions) & set the security context to use
> the current login's security context, it didn't do that. Instead when linked
> server commands were issued, it tried to connect to Instance2 using NT
> AUTHORITY\ANONYMOUS LOGON.
> When we put both Instance1 & Instance2 on Node1, everything works. When we
> put both Instance1 & Instance2 on Node2, everything works. But when the
> instances are on different nodes, the linked server stuff gets screwy.
2005 Cluster linked server issue
We have a two node cluster with two SQL 2005 instances installed. For the
most part things work. This morning we had Instance1 on Node1 & Instance2 o
n
Node2. When I created a linked server on Instance1 pointed at Instance2
(under the aforementioned node conditions) & set the security context to use
the current login's security context, it didn't do that. Instead when linke
d
server commands were issued, it tried to connect to Instance2 using NT
AUTHORITY\ANONYMOUS LOGON.
When we put both Instance1 & Instance2 on Node1, everything works. When we
put both Instance1 & Instance2 on Node2, everything works. But when the
instances are on different nodes, the linked server stuff gets screwy.Anyone have any ideas? Another thing I'll throw in is that I only get
the error when connecting to Instance1 from another machine (my
workstation, app server, etc.) & running a linked server query. When I
connect to Instance1 locally on that box, the linked server query
performs fine. It's almost as if when my windows credentials travel
from my workstation to Node1 and then to Node2, things get messed
up...
CB wrote:
> We have a two node cluster with two SQL 2005 instances installed. For the
> most part things work. This morning we had Instance1 on Node1 & Instance2
on
> Node2. When I created a linked server on Instance1 pointed at Instance2
> (under the aforementioned node conditions) & set the security context to u
se
> the current login's security context, it didn't do that. Instead when lin
ked
> server commands were issued, it tried to connect to Instance2 using NT
> AUTHORITY\ANONYMOUS LOGON.
> When we put both Instance1 & Instance2 on Node1, everything works. When w
e
> put both Instance1 & Instance2 on Node2, everything works. But when the
> instances are on different nodes, the linked server stuff gets screwy.
most part things work. This morning we had Instance1 on Node1 & Instance2 o
n
Node2. When I created a linked server on Instance1 pointed at Instance2
(under the aforementioned node conditions) & set the security context to use
the current login's security context, it didn't do that. Instead when linke
d
server commands were issued, it tried to connect to Instance2 using NT
AUTHORITY\ANONYMOUS LOGON.
When we put both Instance1 & Instance2 on Node1, everything works. When we
put both Instance1 & Instance2 on Node2, everything works. But when the
instances are on different nodes, the linked server stuff gets screwy.Anyone have any ideas? Another thing I'll throw in is that I only get
the error when connecting to Instance1 from another machine (my
workstation, app server, etc.) & running a linked server query. When I
connect to Instance1 locally on that box, the linked server query
performs fine. It's almost as if when my windows credentials travel
from my workstation to Node1 and then to Node2, things get messed
up...
CB wrote:
> We have a two node cluster with two SQL 2005 instances installed. For the
> most part things work. This morning we had Instance1 on Node1 & Instance2
on
> Node2. When I created a linked server on Instance1 pointed at Instance2
> (under the aforementioned node conditions) & set the security context to u
se
> the current login's security context, it didn't do that. Instead when lin
ked
> server commands were issued, it tried to connect to Instance2 using NT
> AUTHORITY\ANONYMOUS LOGON.
> When we put both Instance1 & Instance2 on Node1, everything works. When w
e
> put both Instance1 & Instance2 on Node2, everything works. But when the
> instances are on different nodes, the linked server stuff gets screwy.
2005 Cluster linked server issue
We have a two node cluster with two SQL 2005 instances installed. For the
most part things work. This morning we had Instance1 on Node1 & Instance2 on
Node2. When I created a linked server on Instance1 pointed at Instance2
(under the aforementioned node conditions) & set the security context to use
the current login's security context, it didn't do that. Instead when linked
server commands were issued, it tried to connect to Instance2 using NT
AUTHORITY\ANONYMOUS LOGON.
When we put both Instance1 & Instance2 on Node1, everything works. When we
put both Instance1 & Instance2 on Node2, everything works. But when the
instances are on different nodes, the linked server stuff gets screwy.Anyone have any ideas? Another thing I'll throw in is that I only get
the error when connecting to Instance1 from another machine (my
workstation, app server, etc.) & running a linked server query. When I
connect to Instance1 locally on that box, the linked server query
performs fine. It's almost as if when my windows credentials travel
from my workstation to Node1 and then to Node2, things get messed
up...
CB wrote:
> We have a two node cluster with two SQL 2005 instances installed. For the
> most part things work. This morning we had Instance1 on Node1 & Instance2 on
> Node2. When I created a linked server on Instance1 pointed at Instance2
> (under the aforementioned node conditions) & set the security context to use
> the current login's security context, it didn't do that. Instead when linked
> server commands were issued, it tried to connect to Instance2 using NT
> AUTHORITY\ANONYMOUS LOGON.
> When we put both Instance1 & Instance2 on Node1, everything works. When we
> put both Instance1 & Instance2 on Node2, everything works. But when the
> instances are on different nodes, the linked server stuff gets screwy.
most part things work. This morning we had Instance1 on Node1 & Instance2 on
Node2. When I created a linked server on Instance1 pointed at Instance2
(under the aforementioned node conditions) & set the security context to use
the current login's security context, it didn't do that. Instead when linked
server commands were issued, it tried to connect to Instance2 using NT
AUTHORITY\ANONYMOUS LOGON.
When we put both Instance1 & Instance2 on Node1, everything works. When we
put both Instance1 & Instance2 on Node2, everything works. But when the
instances are on different nodes, the linked server stuff gets screwy.Anyone have any ideas? Another thing I'll throw in is that I only get
the error when connecting to Instance1 from another machine (my
workstation, app server, etc.) & running a linked server query. When I
connect to Instance1 locally on that box, the linked server query
performs fine. It's almost as if when my windows credentials travel
from my workstation to Node1 and then to Node2, things get messed
up...
CB wrote:
> We have a two node cluster with two SQL 2005 instances installed. For the
> most part things work. This morning we had Instance1 on Node1 & Instance2 on
> Node2. When I created a linked server on Instance1 pointed at Instance2
> (under the aforementioned node conditions) & set the security context to use
> the current login's security context, it didn't do that. Instead when linked
> server commands were issued, it tried to connect to Instance2 using NT
> AUTHORITY\ANONYMOUS LOGON.
> When we put both Instance1 & Instance2 on Node1, everything works. When we
> put both Instance1 & Instance2 on Node2, everything works. But when the
> instances are on different nodes, the linked server stuff gets screwy.
Thursday, February 9, 2012
2005 Agent - MSX enlist failed
I have a server that is running two SQL Server 2005 instances. The MSSQL
and AGENT services for both instances are both running with a local domain
account on the server. When setting up one instance as a master and the
target ("DBSVR2003\inst1") as the other instance on the server I get the
following message on the last step of the Master wizard:
MSX enlist failed for JobServer "DBSVR2003\inst1"
Additional Information:
An exception occurred wihile executing a Transact-SQL statement or
batch.
[Microsoft.SQLServer.ConnectionInfo]
The enlist operation failed9reason: SQLServerAgent Error: Una ble to
connect to MSX 'DBSVR2003'.0 (Microsoft SQL Server, Error: 22026)
"DBSVR2003" is the default instance on the server that I want to make the
master.
Any assistance that you can provide would be greatly appreciated.
Thanks!
Hi Cgal,
Have you created the Master Server before you create the Target Server?
Would you please let me know the detailed steps you are taking?
For more information about HOW-TO, check the list below
Creating a Multiserver Environment
http://msdn2.microsoft.com/library/ms191305.aspx
Please use T-SQL statement to create this multiserver environment directly,
we would trace to see which statement goes wrong.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||The instructions in the link you provided indicate that the the _msx_enlist
stored procedure should be used to add a master server with TSQL. The
master server that I wanted to add is on a machine named DBSVR2003 so I ran
the following command:
EXEC msdb.dbo.sp_msx_enlist N'DBSVR2003',
N'some location' ;
The result returns was:
Msg 14297, Level 16, State 1, Procedure sp_msx_enlist, Line 86
Cannot enlist into the local machine.
The other approach that I was using utilizes the master server wizard. When
I use the wizard the first three steps succeed but the last step fails. The
output from the report is as follows:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'DBSVR2003' is running (Success)
The service 'SQLSERVERAGENT' is running.
- Ensure the agent startup account for 'DBSVR2003\inst1' has rights to login
as a target server (Success)
Checking to see if the starup account for 'DBSVR2003\inst1' already exists.
Login exists on server.
Checking to see if login has rights to msdb.
Login has rights to msdb.
Checking to see if user is a member of the TargetServersRole.
User is a member of the TargetServersRole.
- Enlist 'DBSVR2003\inst1' into 'DBSVR2003' (Error)
Enlisting target server 'DBSVR2003\inst1' with master server 'DBSVR2003'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'DBSVR2003\inst1'.
(Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?ProdN...r&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect
to MSX 'DBSVR2003'.) (Microsoft SQL Server, Error: 22026)
For help, click:
http://go.microsoft.com/fwlink?ProdN...6&LinkId=20476
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:SsdHCjFCGHA.832@.TK2MSFTNGXA02.phx.gbl...
> Hi Cgal,
> Have you created the Master Server before you create the Target Server?
> Would you please let me know the detailed steps you are taking?
> For more information about HOW-TO, check the list below
> Creating a Multiserver Environment
> http://msdn2.microsoft.com/library/ms191305.aspx
> Please use T-SQL statement to create this multiserver environment
> directly,
> we would trace to see which statement goes wrong.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||Hi Cgal,
Thanks for your patience.
In the SQL Server Configuration Manager, please make sure TCP/IP and Named
pipes are enabled for master instance. Also, please manually add "NT
Authority/SYSTEM" account to master instance and assign it to sysadmin role
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Michael,
Thanks for staying with me on this one.
I checked the TCP/IP and Named Pipes settings on the master instance and
target instance and they were both enabled. I also checked "NT
Authority/System" and it was a valid login on the master instance and was a
member of the sysadmin role.
I tried to add the master server again with TSQL and the wizard and both of
these approaches fail. The same error messages are displayed for each
method that I sent before.
Please let me know what we can try next.
Thanks!
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:xXDRRM5CGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> Hi Cgal,
> Thanks for your patience.
> In the SQL Server Configuration Manager, please make sure TCP/IP and Named
> pipes are enabled for master instance. Also, please manually add "NT
> Authority/SYSTEM" account to master instance and assign it to sysadmin
> role
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||Hi Cgal,
You are welcome.
For now, to find out the root cause of this issue I am afriad we may need
to analyze SQL Server internal, this work has to be done by contacting
Microsoft Customer Service and Support. Therefore, we probably will not be
able to resolve the issue through the newsgroups. I recommend that you open
a Support incident with Microsoft Customer Service and Support so that a
dedicated Support Professional can assist with this case. If you need any
help in this regard, please let me know.
For a complete list of Microsoft Customer Service and Support phone
numbers, please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Thanks again for your help.
I will open up an incident. Do you know whether the incident will be
counted against my MSDN quota if this turns out to be a bug?
Thanks!
Chris
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:h5EHZtDDGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> Hi Cgal,
> You are welcome.
> For now, to find out the root cause of this issue I am afriad we may need
> to analyze SQL Server internal, this work has to be done by contacting
> Microsoft Customer Service and Support. Therefore, we probably will not be
> able to resolve the issue through the newsgroups. I recommend that you
> open
> a Support incident with Microsoft Customer Service and Support so that a
> dedicated Support Professional can assist with this case. If you need any
> help in this regard, please let me know.
> For a complete list of Microsoft Customer Service and Support phone
> numbers, please go to the following address on the World Wide Web:
> http://support.microsoft.com/directory/overview.asp
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||Hi Cgal,
Thanks so much for your understanding.
Yes, if this turned out to be a problem in the product, you will be
refunded.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
and AGENT services for both instances are both running with a local domain
account on the server. When setting up one instance as a master and the
target ("DBSVR2003\inst1") as the other instance on the server I get the
following message on the last step of the Master wizard:
MSX enlist failed for JobServer "DBSVR2003\inst1"
Additional Information:
An exception occurred wihile executing a Transact-SQL statement or
batch.
[Microsoft.SQLServer.ConnectionInfo]
The enlist operation failed9reason: SQLServerAgent Error: Una ble to
connect to MSX 'DBSVR2003'.0 (Microsoft SQL Server, Error: 22026)
"DBSVR2003" is the default instance on the server that I want to make the
master.
Any assistance that you can provide would be greatly appreciated.
Thanks!
Hi Cgal,
Have you created the Master Server before you create the Target Server?
Would you please let me know the detailed steps you are taking?
For more information about HOW-TO, check the list below
Creating a Multiserver Environment
http://msdn2.microsoft.com/library/ms191305.aspx
Please use T-SQL statement to create this multiserver environment directly,
we would trace to see which statement goes wrong.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||The instructions in the link you provided indicate that the the _msx_enlist
stored procedure should be used to add a master server with TSQL. The
master server that I wanted to add is on a machine named DBSVR2003 so I ran
the following command:
EXEC msdb.dbo.sp_msx_enlist N'DBSVR2003',
N'some location' ;
The result returns was:
Msg 14297, Level 16, State 1, Procedure sp_msx_enlist, Line 86
Cannot enlist into the local machine.
The other approach that I was using utilizes the master server wizard. When
I use the wizard the first three steps succeed but the last step fails. The
output from the report is as follows:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'DBSVR2003' is running (Success)
The service 'SQLSERVERAGENT' is running.
- Ensure the agent startup account for 'DBSVR2003\inst1' has rights to login
as a target server (Success)
Checking to see if the starup account for 'DBSVR2003\inst1' already exists.
Login exists on server.
Checking to see if login has rights to msdb.
Login has rights to msdb.
Checking to see if user is a member of the TargetServersRole.
User is a member of the TargetServersRole.
- Enlist 'DBSVR2003\inst1' into 'DBSVR2003' (Error)
Enlisting target server 'DBSVR2003\inst1' with master server 'DBSVR2003'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'DBSVR2003\inst1'.
(Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?ProdN...r&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect
to MSX 'DBSVR2003'.) (Microsoft SQL Server, Error: 22026)
For help, click:
http://go.microsoft.com/fwlink?ProdN...6&LinkId=20476
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:SsdHCjFCGHA.832@.TK2MSFTNGXA02.phx.gbl...
> Hi Cgal,
> Have you created the Master Server before you create the Target Server?
> Would you please let me know the detailed steps you are taking?
> For more information about HOW-TO, check the list below
> Creating a Multiserver Environment
> http://msdn2.microsoft.com/library/ms191305.aspx
> Please use T-SQL statement to create this multiserver environment
> directly,
> we would trace to see which statement goes wrong.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||Hi Cgal,
Thanks for your patience.
In the SQL Server Configuration Manager, please make sure TCP/IP and Named
pipes are enabled for master instance. Also, please manually add "NT
Authority/SYSTEM" account to master instance and assign it to sysadmin role
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Michael,
Thanks for staying with me on this one.
I checked the TCP/IP and Named Pipes settings on the master instance and
target instance and they were both enabled. I also checked "NT
Authority/System" and it was a valid login on the master instance and was a
member of the sysadmin role.
I tried to add the master server again with TSQL and the wizard and both of
these approaches fail. The same error messages are displayed for each
method that I sent before.
Please let me know what we can try next.
Thanks!
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:xXDRRM5CGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> Hi Cgal,
> Thanks for your patience.
> In the SQL Server Configuration Manager, please make sure TCP/IP and Named
> pipes are enabled for master instance. Also, please manually add "NT
> Authority/SYSTEM" account to master instance and assign it to sysadmin
> role
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||Hi Cgal,
You are welcome.
For now, to find out the root cause of this issue I am afriad we may need
to analyze SQL Server internal, this work has to be done by contacting
Microsoft Customer Service and Support. Therefore, we probably will not be
able to resolve the issue through the newsgroups. I recommend that you open
a Support incident with Microsoft Customer Service and Support so that a
dedicated Support Professional can assist with this case. If you need any
help in this regard, please let me know.
For a complete list of Microsoft Customer Service and Support phone
numbers, please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Thanks again for your help.
I will open up an incident. Do you know whether the incident will be
counted against my MSDN quota if this turns out to be a bug?
Thanks!
Chris
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:h5EHZtDDGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> Hi Cgal,
> You are welcome.
> For now, to find out the root cause of this issue I am afriad we may need
> to analyze SQL Server internal, this work has to be done by contacting
> Microsoft Customer Service and Support. Therefore, we probably will not be
> able to resolve the issue through the newsgroups. I recommend that you
> open
> a Support incident with Microsoft Customer Service and Support so that a
> dedicated Support Professional can assist with this case. If you need any
> help in this regard, please let me know.
> For a complete list of Microsoft Customer Service and Support phone
> numbers, please go to the following address on the World Wide Web:
> http://support.microsoft.com/directory/overview.asp
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||Hi Cgal,
Thanks so much for your understanding.
Yes, if this turned out to be a problem in the product, you will be
refunded.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
2005 Agent - MSX enlist failed
I have a server that is running two SQL Server 2005 instances. The MSSQL
and AGENT services for both instances are both running with a local domain
account on the server. When setting up one instance as a master and the
target ("DBSVR2003\inst1") as the other instance on the server I get the
following message on the last step of the Master wizard:
MSX enlist failed for JobServer "DBSVR2003\inst1"
Additional Information:
An exception occurred wihile executing a Transact-SQL statement or
batch.
[Microsoft.SQLServer.ConnectionInfo]
The enlist operation failed9reason: SQLServerAgent Error: Una ble to
connect to MSX 'DBSVR2003'.0 (Microsoft SQL Server, Error: 22026)
"DBSVR2003" is the default instance on the server that I want to make the
master.
Any assistance that you can provide would be greatly appreciated.
Thanks!Hi Cgal,
Have you created the Master Server before you create the Target Server?
Would you please let me know the detailed steps you are taking?
For more information about HOW-TO, check the list below
Creating a Multiserver Environment
http://msdn2.microsoft.com/library/ms191305.aspx
Please use T-SQL statement to create this multiserver environment directly,
we would trace to see which statement goes wrong.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||The instructions in the link you provided indicate that the the _msx_enlist
stored procedure should be used to add a master server with TSQL. The
master server that I wanted to add is on a machine named DBSVR2003 so I ran
the following command:
EXEC msdb.dbo.sp_msx_enlist N'DBSVR2003',
N'some location' ;
The result returns was:
Msg 14297, Level 16, State 1, Procedure sp_msx_enlist, Line 86
Cannot enlist into the local machine.
The other approach that I was using utilizes the master server wizard. When
I use the wizard the first three steps succeed but the last step fails. The
output from the report is as follows:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'DBSVR2003' is running (Success)
The service 'SQLSERVERAGENT' is running.
- Ensure the agent startup account for 'DBSVR2003\inst1' has rights to login
as a target server (Success)
Checking to see if the starup account for 'DBSVR2003\inst1' already exists.
Login exists on server.
Checking to see if login has rights to msdb.
Login has rights to msdb.
Checking to see if user is a member of the TargetServersRole.
User is a member of the TargetServersRole.
- Enlist 'DBSVR2003\inst1' into 'DBSVR2003' (Error)
Enlisting target server 'DBSVR2003\inst1' with master server 'DBSVR2003'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'DBSVR2003\inst1'.
(Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=20476
--
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect
to MSX 'DBSVR2003'.) (Microsoft SQL Server, Error: 22026)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:SsdHCjFCGHA.832@.TK2MSFTNGXA02.phx.gbl...
> Hi Cgal,
> Have you created the Master Server before you create the Target Server?
> Would you please let me know the detailed steps you are taking?
> For more information about HOW-TO, check the list below
> Creating a Multiserver Environment
> http://msdn2.microsoft.com/library/ms191305.aspx
> Please use T-SQL statement to create this multiserver environment
> directly,
> we would trace to see which statement goes wrong.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Cgal,
Thanks for your patience.
In the SQL Server Configuration Manager, please make sure TCP/IP and Named
pipes are enabled for master instance. Also, please manually add "NT
Authority/SYSTEM" account to master instance and assign it to sysadmin role
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael,
Thanks for staying with me on this one.
I checked the TCP/IP and Named Pipes settings on the master instance and
target instance and they were both enabled. I also checked "NT
Authority/System" and it was a valid login on the master instance and was a
member of the sysadmin role.
I tried to add the master server again with TSQL and the wizard and both of
these approaches fail. The same error messages are displayed for each
method that I sent before.
Please let me know what we can try next.
Thanks!
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:xXDRRM5CGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> Hi Cgal,
> Thanks for your patience.
> In the SQL Server Configuration Manager, please make sure TCP/IP and Named
> pipes are enabled for master instance. Also, please manually add "NT
> Authority/SYSTEM" account to master instance and assign it to sysadmin
> role
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Cgal,
You are welcome.
For now, to find out the root cause of this issue I am afriad we may need
to analyze SQL Server internal, this work has to be done by contacting
Microsoft Customer Service and Support. Therefore, we probably will not be
able to resolve the issue through the newsgroups. I recommend that you open
a Support incident with Microsoft Customer Service and Support so that a
dedicated Support Professional can assist with this case. If you need any
help in this regard, please let me know.
For a complete list of Microsoft Customer Service and Support phone
numbers, please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks again for your help.
I will open up an incident. Do you know whether the incident will be
counted against my MSDN quota if this turns out to be a bug?
Thanks!
Chris
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:h5EHZtDDGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> Hi Cgal,
> You are welcome.
> For now, to find out the root cause of this issue I am afriad we may need
> to analyze SQL Server internal, this work has to be done by contacting
> Microsoft Customer Service and Support. Therefore, we probably will not be
> able to resolve the issue through the newsgroups. I recommend that you
> open
> a Support incident with Microsoft Customer Service and Support so that a
> dedicated Support Professional can assist with this case. If you need any
> help in this regard, please let me know.
> For a complete list of Microsoft Customer Service and Support phone
> numbers, please go to the following address on the World Wide Web:
> http://support.microsoft.com/directory/overview.asp
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Cgal,
Thanks so much for your understanding.
Yes, if this turned out to be a problem in the product, you will be
refunded.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
and AGENT services for both instances are both running with a local domain
account on the server. When setting up one instance as a master and the
target ("DBSVR2003\inst1") as the other instance on the server I get the
following message on the last step of the Master wizard:
MSX enlist failed for JobServer "DBSVR2003\inst1"
Additional Information:
An exception occurred wihile executing a Transact-SQL statement or
batch.
[Microsoft.SQLServer.ConnectionInfo]
The enlist operation failed9reason: SQLServerAgent Error: Una ble to
connect to MSX 'DBSVR2003'.0 (Microsoft SQL Server, Error: 22026)
"DBSVR2003" is the default instance on the server that I want to make the
master.
Any assistance that you can provide would be greatly appreciated.
Thanks!Hi Cgal,
Have you created the Master Server before you create the Target Server?
Would you please let me know the detailed steps you are taking?
For more information about HOW-TO, check the list below
Creating a Multiserver Environment
http://msdn2.microsoft.com/library/ms191305.aspx
Please use T-SQL statement to create this multiserver environment directly,
we would trace to see which statement goes wrong.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||The instructions in the link you provided indicate that the the _msx_enlist
stored procedure should be used to add a master server with TSQL. The
master server that I wanted to add is on a machine named DBSVR2003 so I ran
the following command:
EXEC msdb.dbo.sp_msx_enlist N'DBSVR2003',
N'some location' ;
The result returns was:
Msg 14297, Level 16, State 1, Procedure sp_msx_enlist, Line 86
Cannot enlist into the local machine.
The other approach that I was using utilizes the master server wizard. When
I use the wizard the first three steps succeed but the last step fails. The
output from the report is as follows:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'DBSVR2003' is running (Success)
The service 'SQLSERVERAGENT' is running.
- Ensure the agent startup account for 'DBSVR2003\inst1' has rights to login
as a target server (Success)
Checking to see if the starup account for 'DBSVR2003\inst1' already exists.
Login exists on server.
Checking to see if login has rights to msdb.
Login has rights to msdb.
Checking to see if user is a member of the TargetServersRole.
User is a member of the TargetServersRole.
- Enlist 'DBSVR2003\inst1' into 'DBSVR2003' (Error)
Enlisting target server 'DBSVR2003\inst1' with master server 'DBSVR2003'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'DBSVR2003\inst1'.
(Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=20476
--
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect
to MSX 'DBSVR2003'.) (Microsoft SQL Server, Error: 22026)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:SsdHCjFCGHA.832@.TK2MSFTNGXA02.phx.gbl...
> Hi Cgal,
> Have you created the Master Server before you create the Target Server?
> Would you please let me know the detailed steps you are taking?
> For more information about HOW-TO, check the list below
> Creating a Multiserver Environment
> http://msdn2.microsoft.com/library/ms191305.aspx
> Please use T-SQL statement to create this multiserver environment
> directly,
> we would trace to see which statement goes wrong.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Cgal,
Thanks for your patience.
In the SQL Server Configuration Manager, please make sure TCP/IP and Named
pipes are enabled for master instance. Also, please manually add "NT
Authority/SYSTEM" account to master instance and assign it to sysadmin role
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael,
Thanks for staying with me on this one.
I checked the TCP/IP and Named Pipes settings on the master instance and
target instance and they were both enabled. I also checked "NT
Authority/System" and it was a valid login on the master instance and was a
member of the sysadmin role.
I tried to add the master server again with TSQL and the wizard and both of
these approaches fail. The same error messages are displayed for each
method that I sent before.
Please let me know what we can try next.
Thanks!
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:xXDRRM5CGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> Hi Cgal,
> Thanks for your patience.
> In the SQL Server Configuration Manager, please make sure TCP/IP and Named
> pipes are enabled for master instance. Also, please manually add "NT
> Authority/SYSTEM" account to master instance and assign it to sysadmin
> role
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Cgal,
You are welcome.
For now, to find out the root cause of this issue I am afriad we may need
to analyze SQL Server internal, this work has to be done by contacting
Microsoft Customer Service and Support. Therefore, we probably will not be
able to resolve the issue through the newsgroups. I recommend that you open
a Support incident with Microsoft Customer Service and Support so that a
dedicated Support Professional can assist with this case. If you need any
help in this regard, please let me know.
For a complete list of Microsoft Customer Service and Support phone
numbers, please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks again for your help.
I will open up an incident. Do you know whether the incident will be
counted against my MSDN quota if this turns out to be a bug?
Thanks!
Chris
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:h5EHZtDDGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> Hi Cgal,
> You are welcome.
> For now, to find out the root cause of this issue I am afriad we may need
> to analyze SQL Server internal, this work has to be done by contacting
> Microsoft Customer Service and Support. Therefore, we probably will not be
> able to resolve the issue through the newsgroups. I recommend that you
> open
> a Support incident with Microsoft Customer Service and Support so that a
> dedicated Support Professional can assist with this case. If you need any
> help in this regard, please let me know.
> For a complete list of Microsoft Customer Service and Support phone
> numbers, please go to the following address on the World Wide Web:
> http://support.microsoft.com/directory/overview.asp
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Cgal,
Thanks so much for your understanding.
Yes, if this turned out to be a problem in the product, you will be
refunded.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
2005 Agent - MSX enlist failed
I have a server that is running two SQL Server 2005 instances. The MSSQL
and AGENT services for both instances are both running with a local domain
account on the server. When setting up one instance as a master and the
target ("DBSVR2003\inst1") as the other instance on the server I get the
following message on the last step of the Master wizard:
MSX enlist failed for JobServer "DBSVR2003\inst1"
Additional Information:
An exception occurred wihile executing a Transact-SQL statement or
batch.
[Microsoft.SQLServer.ConnectionInfo]
The enlist operation failed9reason: SQLServerAgent Error: Una ble to
connect to MSX 'DBSVR2003'.0 (Microsoft SQL Server, Error: 22026)
"DBSVR2003" is the default instance on the server that I want to make the
master.
Any assistance that you can provide would be greatly appreciated.
Thanks!Hi Cgal,
Have you created the Master Server before you create the Target Server?
Would you please let me know the detailed steps you are taking?
For more information about HOW-TO, check the list below
Creating a Multiserver Environment
http://msdn2.microsoft.com/library/ms191305.aspx
Please use T-SQL statement to create this multiserver environment directly,
we would trace to see which statement goes wrong.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||The instructions in the link you provided indicate that the the _msx_enlist
stored procedure should be used to add a master server with TSQL. The
master server that I wanted to add is on a machine named DBSVR2003 so I ran
the following command:
EXEC msdb.dbo.sp_msx_enlist N'DBSVR2003',
N'some location' ;
The result returns was:
Msg 14297, Level 16, State 1, Procedure sp_msx_enlist, Line 86
Cannot enlist into the local machine.
The other approach that I was using utilizes the master server wizard. When
I use the wizard the first three steps succeed but the last step fails. The
output from the report is as follows:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'DBSVR2003' is running (Success)
The service 'SQLSERVERAGENT' is running.
- Ensure the agent startup account for 'DBSVR2003\inst1' has rights to login
as a target server (Success)
Checking to see if the starup account for 'DBSVR2003\inst1' already exists.
Login exists on server.
Checking to see if login has rights to msdb.
Login has rights to msdb.
Checking to see if user is a member of the TargetServersRole.
User is a member of the TargetServersRole.
- Enlist 'DBSVR2003\inst1' into 'DBSVR2003' (Error)
Enlisting target server 'DBSVR2003\inst1' with master server 'DBSVR2003'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'DBSVR2003\inst1'.
(Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect
to MSX 'DBSVR2003'.) (Microsoft SQL Server, Error: 22026)
For help, click:
http://go.microsoft.com/fwlink?Prod...26&LinkId=20476
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:SsdHCjFCGHA.832@.TK2MSFTNGXA02.phx.gbl...
> Hi Cgal,
> Have you created the Master Server before you create the Target Server?
> Would you please let me know the detailed steps you are taking?
> For more information about HOW-TO, check the list below
> Creating a Multiserver Environment
> http://msdn2.microsoft.com/library/ms191305.aspx
> Please use T-SQL statement to create this multiserver environment
> directly,
> we would trace to see which statement goes wrong.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Cgal,
Thanks for your patience.
In the SQL Server Configuration Manager, please make sure TCP/IP and Named
pipes are enabled for master instance. Also, please manually add "NT
Authority/SYSTEM" account to master instance and assign it to sysadmin role
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael,
Thanks for staying with me on this one.
I checked the TCP/IP and Named Pipes settings on the master instance and
target instance and they were both enabled. I also checked "NT
Authority/System" and it was a valid login on the master instance and was a
member of the sysadmin role.
I tried to add the master server again with TSQL and the wizard and both of
these approaches fail. The same error messages are displayed for each
method that I sent before.
Please let me know what we can try next.
Thanks!
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:xXDRRM5CGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> Hi Cgal,
> Thanks for your patience.
> In the SQL Server Configuration Manager, please make sure TCP/IP and Named
> pipes are enabled for master instance. Also, please manually add "NT
> Authority/SYSTEM" account to master instance and assign it to sysadmin
> role
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Cgal,
You are welcome.
For now, to find out the root cause of this issue I am afriad we may need
to analyze SQL Server internal, this work has to be done by contacting
Microsoft Customer Service and Support. Therefore, we probably will not be
able to resolve the issue through the newsgroups. I recommend that you open
a Support incident with Microsoft Customer Service and Support so that a
dedicated Support Professional can assist with this case. If you need any
help in this regard, please let me know.
For a complete list of Microsoft Customer Service and Support phone
numbers, please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks again for your help.
I will open up an incident. Do you know whether the incident will be
counted against my MSDN quota if this turns out to be a bug?
Thanks!
Chris
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:h5EHZtDDGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> Hi Cgal,
> You are welcome.
> For now, to find out the root cause of this issue I am afriad we may need
> to analyze SQL Server internal, this work has to be done by contacting
> Microsoft Customer Service and Support. Therefore, we probably will not be
> able to resolve the issue through the newsgroups. I recommend that you
> open
> a Support incident with Microsoft Customer Service and Support so that a
> dedicated Support Professional can assist with this case. If you need any
> help in this regard, please let me know.
> For a complete list of Microsoft Customer Service and Support phone
> numbers, please go to the following address on the World Wide Web:
> http://support.microsoft.com/directory/overview.asp
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Cgal,
Thanks so much for your understanding.
Yes, if this turned out to be a problem in the product, you will be
refunded.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
and AGENT services for both instances are both running with a local domain
account on the server. When setting up one instance as a master and the
target ("DBSVR2003\inst1") as the other instance on the server I get the
following message on the last step of the Master wizard:
MSX enlist failed for JobServer "DBSVR2003\inst1"
Additional Information:
An exception occurred wihile executing a Transact-SQL statement or
batch.
[Microsoft.SQLServer.ConnectionInfo]
The enlist operation failed9reason: SQLServerAgent Error: Una ble to
connect to MSX 'DBSVR2003'.0 (Microsoft SQL Server, Error: 22026)
"DBSVR2003" is the default instance on the server that I want to make the
master.
Any assistance that you can provide would be greatly appreciated.
Thanks!Hi Cgal,
Have you created the Master Server before you create the Target Server?
Would you please let me know the detailed steps you are taking?
For more information about HOW-TO, check the list below
Creating a Multiserver Environment
http://msdn2.microsoft.com/library/ms191305.aspx
Please use T-SQL statement to create this multiserver environment directly,
we would trace to see which statement goes wrong.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||The instructions in the link you provided indicate that the the _msx_enlist
stored procedure should be used to add a master server with TSQL. The
master server that I wanted to add is on a machine named DBSVR2003 so I ran
the following command:
EXEC msdb.dbo.sp_msx_enlist N'DBSVR2003',
N'some location' ;
The result returns was:
Msg 14297, Level 16, State 1, Procedure sp_msx_enlist, Line 86
Cannot enlist into the local machine.
The other approach that I was using utilizes the master server wizard. When
I use the wizard the first three steps succeed but the last step fails. The
output from the report is as follows:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'DBSVR2003' is running (Success)
The service 'SQLSERVERAGENT' is running.
- Ensure the agent startup account for 'DBSVR2003\inst1' has rights to login
as a target server (Success)
Checking to see if the starup account for 'DBSVR2003\inst1' already exists.
Login exists on server.
Checking to see if login has rights to msdb.
Login has rights to msdb.
Checking to see if user is a member of the TargetServersRole.
User is a member of the TargetServersRole.
- Enlist 'DBSVR2003\inst1' into 'DBSVR2003' (Error)
Enlisting target server 'DBSVR2003\inst1' with master server 'DBSVR2003'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'DBSVR2003\inst1'.
(Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect
to MSX 'DBSVR2003'.) (Microsoft SQL Server, Error: 22026)
For help, click:
http://go.microsoft.com/fwlink?Prod...26&LinkId=20476
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:SsdHCjFCGHA.832@.TK2MSFTNGXA02.phx.gbl...
> Hi Cgal,
> Have you created the Master Server before you create the Target Server?
> Would you please let me know the detailed steps you are taking?
> For more information about HOW-TO, check the list below
> Creating a Multiserver Environment
> http://msdn2.microsoft.com/library/ms191305.aspx
> Please use T-SQL statement to create this multiserver environment
> directly,
> we would trace to see which statement goes wrong.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Cgal,
Thanks for your patience.
In the SQL Server Configuration Manager, please make sure TCP/IP and Named
pipes are enabled for master instance. Also, please manually add "NT
Authority/SYSTEM" account to master instance and assign it to sysadmin role
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael,
Thanks for staying with me on this one.
I checked the TCP/IP and Named Pipes settings on the master instance and
target instance and they were both enabled. I also checked "NT
Authority/System" and it was a valid login on the master instance and was a
member of the sysadmin role.
I tried to add the master server again with TSQL and the wizard and both of
these approaches fail. The same error messages are displayed for each
method that I sent before.
Please let me know what we can try next.
Thanks!
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:xXDRRM5CGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> Hi Cgal,
> Thanks for your patience.
> In the SQL Server Configuration Manager, please make sure TCP/IP and Named
> pipes are enabled for master instance. Also, please manually add "NT
> Authority/SYSTEM" account to master instance and assign it to sysadmin
> role
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Cgal,
You are welcome.
For now, to find out the root cause of this issue I am afriad we may need
to analyze SQL Server internal, this work has to be done by contacting
Microsoft Customer Service and Support. Therefore, we probably will not be
able to resolve the issue through the newsgroups. I recommend that you open
a Support incident with Microsoft Customer Service and Support so that a
dedicated Support Professional can assist with this case. If you need any
help in this regard, please let me know.
For a complete list of Microsoft Customer Service and Support phone
numbers, please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks again for your help.
I will open up an incident. Do you know whether the incident will be
counted against my MSDN quota if this turns out to be a bug?
Thanks!
Chris
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:h5EHZtDDGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> Hi Cgal,
> You are welcome.
> For now, to find out the root cause of this issue I am afriad we may need
> to analyze SQL Server internal, this work has to be done by contacting
> Microsoft Customer Service and Support. Therefore, we probably will not be
> able to resolve the issue through the newsgroups. I recommend that you
> open
> a Support incident with Microsoft Customer Service and Support so that a
> dedicated Support Professional can assist with this case. If you need any
> help in this regard, please let me know.
> For a complete list of Microsoft Customer Service and Support phone
> numbers, please go to the following address on the World Wide Web:
> http://support.microsoft.com/directory/overview.asp
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Cgal,
Thanks so much for your understanding.
Yes, if this turned out to be a problem in the product, you will be
refunded.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to:
Posts (Atom)