Hi everyone
has anyone come across / developed a way of transforming the commands
in MSRepl_Commands so that, for instance, and Update becomes a Delete
or Insert?
thanks in adveance for abny assists!
Are you requiring an explanation of how this occurs in replication?
If so, this is referred to as a deferred update - see
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q302/3/41.ASP&NoWebContent=1
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||MS_replcommands is a queue. You can modify this queue to delete commands.
Modifying them is difficult as they are in binary. Your best bet is to
ensure that your updates are not replaced by an insert delete pair.
Please refer to the following kb articles for more information.
http://support.microsoft.com/default.aspx/kb/302341
and
http://support.microsoft.com/kb/238254
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
"RedCamel" <RichardJGilbert@.hotmail.com> wrote in message
news:1163426512.098950.159840@.m73g2000cwd.googlegr oups.com...
> Hi everyone
> has anyone come across / developed a way of transforming the commands
> in MSRepl_Commands so that, for instance, and Update becomes a Delete
> or Insert?
> thanks in adveance for abny assists!
>
Showing posts with label across. Show all posts
Showing posts with label across. Show all posts
Monday, March 26, 2012
Friday, March 23, 2012
MsQuery
I've heard when using MSQuery on the client side, the where statement
gets processes at the client side, thus many records come across that
are not necessary. Is that true?
If so, would Query Analyzer be a better choice? We are trying to run
queries against our server (we are not in IT) and we have been getting
CBSIO errors.
ThanksCBSIO?
It does seem fine. I ran it from the OFFICE11 folder for Office 2003 and it
sent the where clause to the server. It might do it on the client if you
have disparate sources, but I would doubt it on the same server.
Query Analyzer would be better, but it does not have the joining tools that
MSQuery does. As long as you get the performance you desire, it should be
fine.
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"Arguments are to be avoided: they are always vulgar and often convincing."
(Oscar Wilde)
<bdaoust@.yahoo.com> wrote in message
news:1126273874.851824.292530@.g47g2000cwa.googlegroups.com...
> I've heard when using MSQuery on the client side, the where statement
> gets processes at the client side, thus many records come across that
> are not necessary. Is that true?
> If so, would Query Analyzer be a better choice? We are trying to run
> queries against our server (we are not in IT) and we have been getting
> CBSIO errors.
> Thanks
>|||Louis,
Thank you for the reply. When you say joining tools, what are you
referring to?
I guess I wouldnt miss them much since I dont even know what they are!
:)
Also, how can you confirm that the where clause was sent to the server?
Thank you.|||> Thank you for the reply. When you say joining tools, what are you
> referring to?
The query by example stuff that MSQuery has where you can pick the tables,
and it joins them for you, etc. If you don't need this and you are writing
SQL Statements in text, then query analyzer is the way to go anyhow.
> Also, how can you confirm that the where clause was sent to the server?
I used profiler and watched the statements being sent to the server.
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"Arguments are to be avoided: they are always vulgar and often convincing."
(Oscar Wilde)
"BerkshireGuy" <bdaoust@.yahoo.com> wrote in message
news:1126281216.691598.305900@.g47g2000cwa.googlegroups.com...
> Louis,
> Thank you for the reply. When you say joining tools, what are you
> referring to?
> I guess I wouldnt miss them much since I dont even know what they are!
> :)
> Also, how can you confirm that the where clause was sent to the server?
>
> Thank you.
>|||Aww I see, there is no design grid.
I am use to writing the SQL, so it will work for me. Hopefully IT is
willing to install it on my machine.
Thanks for the help.sql
gets processes at the client side, thus many records come across that
are not necessary. Is that true?
If so, would Query Analyzer be a better choice? We are trying to run
queries against our server (we are not in IT) and we have been getting
CBSIO errors.
ThanksCBSIO?
It does seem fine. I ran it from the OFFICE11 folder for Office 2003 and it
sent the where clause to the server. It might do it on the client if you
have disparate sources, but I would doubt it on the same server.
Query Analyzer would be better, but it does not have the joining tools that
MSQuery does. As long as you get the performance you desire, it should be
fine.
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"Arguments are to be avoided: they are always vulgar and often convincing."
(Oscar Wilde)
<bdaoust@.yahoo.com> wrote in message
news:1126273874.851824.292530@.g47g2000cwa.googlegroups.com...
> I've heard when using MSQuery on the client side, the where statement
> gets processes at the client side, thus many records come across that
> are not necessary. Is that true?
> If so, would Query Analyzer be a better choice? We are trying to run
> queries against our server (we are not in IT) and we have been getting
> CBSIO errors.
> Thanks
>|||Louis,
Thank you for the reply. When you say joining tools, what are you
referring to?
I guess I wouldnt miss them much since I dont even know what they are!
:)
Also, how can you confirm that the where clause was sent to the server?
Thank you.|||> Thank you for the reply. When you say joining tools, what are you
> referring to?
The query by example stuff that MSQuery has where you can pick the tables,
and it joins them for you, etc. If you don't need this and you are writing
SQL Statements in text, then query analyzer is the way to go anyhow.
> Also, how can you confirm that the where clause was sent to the server?
I used profiler and watched the statements being sent to the server.
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"Arguments are to be avoided: they are always vulgar and often convincing."
(Oscar Wilde)
"BerkshireGuy" <bdaoust@.yahoo.com> wrote in message
news:1126281216.691598.305900@.g47g2000cwa.googlegroups.com...
> Louis,
> Thank you for the reply. When you say joining tools, what are you
> referring to?
> I guess I wouldnt miss them much since I dont even know what they are!
> :)
> Also, how can you confirm that the where clause was sent to the server?
>
> Thank you.
>|||Aww I see, there is no design grid.
I am use to writing the SQL, so it will work for me. Hopefully IT is
willing to install it on my machine.
Thanks for the help.sql
Monday, March 19, 2012
Msg 7314 while querying across linked servers
Hello
I am beginning to think that linked server are more trouble than they are wo
rth and MS will need to work harder to get these to work properly. Here is t
he latest problem.
From srv1, when I do
select * from srv2.db1.information_schema.tables
I get
Server: Msg 7314, Level 16, State 1, Line 1
OLE DB provider 'srv2' does not contain table '"db1"."information_schema"."t
ables"'. The table either does not exist or the current user does not have
permissions on that table.
OLE DB error trace [Non-interface error: OLE DB provider does not conta
in the table: ProviderName='srv2', TableName='"db1"."information_schema"."ta
bles"'].
It works if I connect to srv2 with the login being used to link the 2 server
s and do
use db1
go
select * from information_schema.tables
go
Also if I do <<<select * from srv2.db1.dbo.someothertable>>> it works.
Trying this on SQL Server 2000 enterprise hotfix 837.
Any clues?
Thanks for reading and appreciate your help
ArunArun,
Try this:
exec srv2.db1.dbo.sp_executesql N'select * from information_schema.tables'
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Arun wrote:
> Hello
> I am beginning to think that linked server are more trouble than they are
worth and MS will need to work harder to get these to work properly. Here is
the latest problem.
>
> From srv1, when I do
> select * from srv2.db1.information_schema.tables
> I get
> Server: Msg 7314, Level 16, State 1, Line 1
> OLE DB provider 'srv2' does not contain table '"db1"."information_schema".
"tables"'. The table either does not exist or the current user does not hav
e permissions on that table.
> OLE DB error trace [Non-interface error: OLE DB provider does not con
tain the table: ProviderName='srv2', TableName='"db1"."information_schema"."
tables"'].
> It works if I connect to srv2 with the login being used to link the 2 serv
ers and do
> use db1
> go
> select * from information_schema.tables
> go
> Also if I do <<<select * from srv2.db1.dbo.someothertable>>> it works.
> Trying this on SQL Server 2000 enterprise hotfix 837.
> Any clues?
> Thanks for reading and appreciate your help
> Arun
>|||It works. Thanks Mark
Arun
"Mark Allison" wrote:
> Arun,
> Try this:
> exec srv2.db1.dbo.sp_executesql N'select * from information_schema.tables'
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Arun wrote:
>
I am beginning to think that linked server are more trouble than they are wo
rth and MS will need to work harder to get these to work properly. Here is t
he latest problem.
From srv1, when I do
select * from srv2.db1.information_schema.tables
I get
Server: Msg 7314, Level 16, State 1, Line 1
OLE DB provider 'srv2' does not contain table '"db1"."information_schema"."t
ables"'. The table either does not exist or the current user does not have
permissions on that table.
OLE DB error trace [Non-interface error: OLE DB provider does not conta
in the table: ProviderName='srv2', TableName='"db1"."information_schema"."ta
bles"'].
It works if I connect to srv2 with the login being used to link the 2 server
s and do
use db1
go
select * from information_schema.tables
go
Also if I do <<<select * from srv2.db1.dbo.someothertable>>> it works.
Trying this on SQL Server 2000 enterprise hotfix 837.
Any clues?
Thanks for reading and appreciate your help
ArunArun,
Try this:
exec srv2.db1.dbo.sp_executesql N'select * from information_schema.tables'
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Arun wrote:
> Hello
> I am beginning to think that linked server are more trouble than they are
worth and MS will need to work harder to get these to work properly. Here is
the latest problem.
>
> From srv1, when I do
> select * from srv2.db1.information_schema.tables
> I get
> Server: Msg 7314, Level 16, State 1, Line 1
> OLE DB provider 'srv2' does not contain table '"db1"."information_schema".
"tables"'. The table either does not exist or the current user does not hav
e permissions on that table.
> OLE DB error trace [Non-interface error: OLE DB provider does not con
tain the table: ProviderName='srv2', TableName='"db1"."information_schema"."
tables"'].
> It works if I connect to srv2 with the login being used to link the 2 serv
ers and do
> use db1
> go
> select * from information_schema.tables
> go
> Also if I do <<<select * from srv2.db1.dbo.someothertable>>> it works.
> Trying this on SQL Server 2000 enterprise hotfix 837.
> Any clues?
> Thanks for reading and appreciate your help
> Arun
>|||It works. Thanks Mark
Arun
"Mark Allison" wrote:
> Arun,
> Try this:
> exec srv2.db1.dbo.sp_executesql N'select * from information_schema.tables'
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Arun wrote:
>
Msg 7314 while querying across linked servers
Hello
I am beginning to think that linked server are more trouble than they are worth and MS will need to work harder to get these to work properly. Here is the latest problem.
From srv1, when I do
select * from srv2.db1.information_schema.tables
I get
Server: Msg 7314, Level 16, State 1, Line 1
OLE DB provider 'srv2' does not contain table '"db1"."information_schema"."tables"'. The table either does not exist or the current user does not have permissions on that table.
OLE DB error trace [Non-interface error: OLE DB provider does not contain the table: ProviderName='srv2', TableName='"db1"."information_schema"."tables"'].
It works if I connect to srv2 with the login being used to link the 2 servers and do
use db1
go
select * from information_schema.tables
go
Also if I do <<<select * from srv2.db1.dbo.someothertable>>> it works.
Trying this on SQL Server 2000 enterprise hotfix 837.
Any clues?
Thanks for reading and appreciate your help
Arun
Arun,
Try this:
exec srv2.db1.dbo.sp_executesql N'select * from information_schema.tables'
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Arun wrote:
> Hello
> I am beginning to think that linked server are more trouble than they are worth and MS will need to work harder to get these to work properly. Here is the latest problem.
>
> From srv1, when I do
> select * from srv2.db1.information_schema.tables
> I get
> Server: Msg 7314, Level 16, State 1, Line 1
> OLE DB provider 'srv2' does not contain table '"db1"."information_schema"."tables"'. The table either does not exist or the current user does not have permissions on that table.
> OLE DB error trace [Non-interface error: OLE DB provider does not contain the table: ProviderName='srv2', TableName='"db1"."information_schema"."tables"'].
> It works if I connect to srv2 with the login being used to link the 2 servers and do
> use db1
> go
> select * from information_schema.tables
> go
> Also if I do <<<select * from srv2.db1.dbo.someothertable>>> it works.
> Trying this on SQL Server 2000 enterprise hotfix 837.
> Any clues?
> Thanks for reading and appreciate your help
> Arun
>
|||It works. Thanks Mark
Arun
"Mark Allison" wrote:
> Arun,
> Try this:
> exec srv2.db1.dbo.sp_executesql N'select * from information_schema.tables'
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Arun wrote:
>
I am beginning to think that linked server are more trouble than they are worth and MS will need to work harder to get these to work properly. Here is the latest problem.
From srv1, when I do
select * from srv2.db1.information_schema.tables
I get
Server: Msg 7314, Level 16, State 1, Line 1
OLE DB provider 'srv2' does not contain table '"db1"."information_schema"."tables"'. The table either does not exist or the current user does not have permissions on that table.
OLE DB error trace [Non-interface error: OLE DB provider does not contain the table: ProviderName='srv2', TableName='"db1"."information_schema"."tables"'].
It works if I connect to srv2 with the login being used to link the 2 servers and do
use db1
go
select * from information_schema.tables
go
Also if I do <<<select * from srv2.db1.dbo.someothertable>>> it works.
Trying this on SQL Server 2000 enterprise hotfix 837.
Any clues?
Thanks for reading and appreciate your help
Arun
Arun,
Try this:
exec srv2.db1.dbo.sp_executesql N'select * from information_schema.tables'
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Arun wrote:
> Hello
> I am beginning to think that linked server are more trouble than they are worth and MS will need to work harder to get these to work properly. Here is the latest problem.
>
> From srv1, when I do
> select * from srv2.db1.information_schema.tables
> I get
> Server: Msg 7314, Level 16, State 1, Line 1
> OLE DB provider 'srv2' does not contain table '"db1"."information_schema"."tables"'. The table either does not exist or the current user does not have permissions on that table.
> OLE DB error trace [Non-interface error: OLE DB provider does not contain the table: ProviderName='srv2', TableName='"db1"."information_schema"."tables"'].
> It works if I connect to srv2 with the login being used to link the 2 servers and do
> use db1
> go
> select * from information_schema.tables
> go
> Also if I do <<<select * from srv2.db1.dbo.someothertable>>> it works.
> Trying this on SQL Server 2000 enterprise hotfix 837.
> Any clues?
> Thanks for reading and appreciate your help
> Arun
>
|||It works. Thanks Mark
Arun
"Mark Allison" wrote:
> Arun,
> Try this:
> exec srv2.db1.dbo.sp_executesql N'select * from information_schema.tables'
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Arun wrote:
>
Msg 7314 while querying across linked servers
Hello
I am beginning to think that linked server are more trouble than they are worth and MS will need to work harder to get these to work properly. Here is the latest problem.
From srv1, when I do
select * from srv2.db1.information_schema.tables
I get
Server: Msg 7314, Level 16, State 1, Line 1
OLE DB provider 'srv2' does not contain table '"db1"."information_schema"."tables"'. The table either does not exist or the current user does not have permissions on that table.
OLE DB error trace [Non-interface error: OLE DB provider does not contain the table: ProviderName='srv2', TableName='"db1"."information_schema"."tables"'].
It works if I connect to srv2 with the login being used to link the 2 servers and do
use db1
go
select * from information_schema.tables
go
Also if I do <<<select * from srv2.db1.dbo.someothertable>> it works.
Trying this on SQL Server 2000 enterprise hotfix 837.
Any clues?
Thanks for reading and appreciate your help
ArunArun,
Try this:
exec srv2.db1.dbo.sp_executesql N'select * from information_schema.tables'
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Arun wrote:
> Hello
> I am beginning to think that linked server are more trouble than they are worth and MS will need to work harder to get these to work properly. Here is the latest problem.
>
> From srv1, when I do
> select * from srv2.db1.information_schema.tables
> I get
> Server: Msg 7314, Level 16, State 1, Line 1
> OLE DB provider 'srv2' does not contain table '"db1"."information_schema"."tables"'. The table either does not exist or the current user does not have permissions on that table.
> OLE DB error trace [Non-interface error: OLE DB provider does not contain the table: ProviderName='srv2', TableName='"db1"."information_schema"."tables"'].
> It works if I connect to srv2 with the login being used to link the 2 servers and do
> use db1
> go
> select * from information_schema.tables
> go
> Also if I do <<<select * from srv2.db1.dbo.someothertable>> it works.
> Trying this on SQL Server 2000 enterprise hotfix 837.
> Any clues?
> Thanks for reading and appreciate your help
> Arun
>
I am beginning to think that linked server are more trouble than they are worth and MS will need to work harder to get these to work properly. Here is the latest problem.
From srv1, when I do
select * from srv2.db1.information_schema.tables
I get
Server: Msg 7314, Level 16, State 1, Line 1
OLE DB provider 'srv2' does not contain table '"db1"."information_schema"."tables"'. The table either does not exist or the current user does not have permissions on that table.
OLE DB error trace [Non-interface error: OLE DB provider does not contain the table: ProviderName='srv2', TableName='"db1"."information_schema"."tables"'].
It works if I connect to srv2 with the login being used to link the 2 servers and do
use db1
go
select * from information_schema.tables
go
Also if I do <<<select * from srv2.db1.dbo.someothertable>> it works.
Trying this on SQL Server 2000 enterprise hotfix 837.
Any clues?
Thanks for reading and appreciate your help
ArunArun,
Try this:
exec srv2.db1.dbo.sp_executesql N'select * from information_schema.tables'
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Arun wrote:
> Hello
> I am beginning to think that linked server are more trouble than they are worth and MS will need to work harder to get these to work properly. Here is the latest problem.
>
> From srv1, when I do
> select * from srv2.db1.information_schema.tables
> I get
> Server: Msg 7314, Level 16, State 1, Line 1
> OLE DB provider 'srv2' does not contain table '"db1"."information_schema"."tables"'. The table either does not exist or the current user does not have permissions on that table.
> OLE DB error trace [Non-interface error: OLE DB provider does not contain the table: ProviderName='srv2', TableName='"db1"."information_schema"."tables"'].
> It works if I connect to srv2 with the login being used to link the 2 servers and do
> use db1
> go
> select * from information_schema.tables
> go
> Also if I do <<<select * from srv2.db1.dbo.someothertable>> it works.
> Trying this on SQL Server 2000 enterprise hotfix 837.
> Any clues?
> Thanks for reading and appreciate your help
> Arun
>
Monday, March 12, 2012
msg 1936, can't find in documentation
Hi,
One of our team has come across the following message, I can't find
reference
to it anywhere, any suggestions?:
"Server: Msg 1936, Level 16, State 1, Line 1
Cannot index the view 'Albert_Heijn_LOAD.dbo.v_Supplier'. It contains one or
more disallowed constructs."Seems like you try to create an index on a view, where the view contain some construct which is
disallowed, quite simply.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Stressed" <k@.c.co.uk> wrote in message news:OMJgF0wlDHA.1740@.TK2MSFTNGP12.phx.gbl...
> Hi,
> One of our team has come across the following message, I can't find
> reference
> to it anywhere, any suggestions?:
> "Server: Msg 1936, Level 16, State 1, Line 1
> Cannot index the view 'Albert_Heijn_LOAD.dbo.v_Supplier'. It contains one or
> more disallowed constructs."
>|||I'd gathered that something was not allowed, just that there was no further
reference to it in BOL or on the web.
Turns out that the user was trying to use a computed column, which was
non-deterministic.
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:OwMDw4wlDHA.2068@.TK2MSFTNGP09.phx.gbl...
> Seems like you try to create an index on a view, where the view contain
some construct which is
> disallowed, quite simply.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
> "Stressed" <k@.c.co.uk> wrote in message
news:OMJgF0wlDHA.1740@.TK2MSFTNGP12.phx.gbl...
> > Hi,
> >
> > One of our team has come across the following message, I can't find
> > reference
> >
> > to it anywhere, any suggestions?:
> >
> > "Server: Msg 1936, Level 16, State 1, Line 1
> >
> > Cannot index the view 'Albert_Heijn_LOAD.dbo.v_Supplier'. It contains
one or
> > more disallowed constructs."
> >
> >
>
One of our team has come across the following message, I can't find
reference
to it anywhere, any suggestions?:
"Server: Msg 1936, Level 16, State 1, Line 1
Cannot index the view 'Albert_Heijn_LOAD.dbo.v_Supplier'. It contains one or
more disallowed constructs."Seems like you try to create an index on a view, where the view contain some construct which is
disallowed, quite simply.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Stressed" <k@.c.co.uk> wrote in message news:OMJgF0wlDHA.1740@.TK2MSFTNGP12.phx.gbl...
> Hi,
> One of our team has come across the following message, I can't find
> reference
> to it anywhere, any suggestions?:
> "Server: Msg 1936, Level 16, State 1, Line 1
> Cannot index the view 'Albert_Heijn_LOAD.dbo.v_Supplier'. It contains one or
> more disallowed constructs."
>|||I'd gathered that something was not allowed, just that there was no further
reference to it in BOL or on the web.
Turns out that the user was trying to use a computed column, which was
non-deterministic.
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:OwMDw4wlDHA.2068@.TK2MSFTNGP09.phx.gbl...
> Seems like you try to create an index on a view, where the view contain
some construct which is
> disallowed, quite simply.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
> "Stressed" <k@.c.co.uk> wrote in message
news:OMJgF0wlDHA.1740@.TK2MSFTNGP12.phx.gbl...
> > Hi,
> >
> > One of our team has come across the following message, I can't find
> > reference
> >
> > to it anywhere, any suggestions?:
> >
> > "Server: Msg 1936, Level 16, State 1, Line 1
> >
> > Cannot index the view 'Albert_Heijn_LOAD.dbo.v_Supplier'. It contains
one or
> > more disallowed constructs."
> >
> >
>
Monday, February 20, 2012
MSDTC across different Windows versions
Hi there.
I have a MS Distributed Transaction Coordinator qestion which doesnt involve
a clustered setup at all. I know this may not technically be the correct
forum but I've solved other MSDTC issues here before so I was hoping...!
Do you know whether any problems should be anticipated with distributed
transactions if a series of linked or remote servers were set up on machines
with different operating systems? I'm about to set up a system with 2
machines on Winows2003 and one on Windows NT => I just want to know whether
it's possible to get a distributed transaction to run ok across all 3
servers...
Any info would be appreciated!
The same protocols are used; however, technically, DTC did not come around
until Win2K. For NT 4, it was Option Pack and MTS. So, there could be some
compatibility issues there.
However, the SQL Server BEGIN DISTRIBUTED TRANSACTION is the same.
Best I can say is Test, Test, Test.
Sincerely,
Anthony Thomas
"len" <len@.discussions.microsoft.com> wrote in message
news:E31BBA8A-F9CA-4BB2-B286-29B1062030B6@.microsoft.com...
> Hi there.
> I have a MS Distributed Transaction Coordinator qestion which doesnt
involve
> a clustered setup at all. I know this may not technically be the correct
> forum but I've solved other MSDTC issues here before so I was hoping...!
> Do you know whether any problems should be anticipated with distributed
> transactions if a series of linked or remote servers were set up on
machines
> with different operating systems? I'm about to set up a system with 2
> machines on Winows2003 and one on Windows NT => I just want to know
whether
> it's possible to get a distributed transaction to run ok across all 3
> servers...
> Any info would be appreciated!
>
I have a MS Distributed Transaction Coordinator qestion which doesnt involve
a clustered setup at all. I know this may not technically be the correct
forum but I've solved other MSDTC issues here before so I was hoping...!
Do you know whether any problems should be anticipated with distributed
transactions if a series of linked or remote servers were set up on machines
with different operating systems? I'm about to set up a system with 2
machines on Winows2003 and one on Windows NT => I just want to know whether
it's possible to get a distributed transaction to run ok across all 3
servers...
Any info would be appreciated!
The same protocols are used; however, technically, DTC did not come around
until Win2K. For NT 4, it was Option Pack and MTS. So, there could be some
compatibility issues there.
However, the SQL Server BEGIN DISTRIBUTED TRANSACTION is the same.
Best I can say is Test, Test, Test.
Sincerely,
Anthony Thomas
"len" <len@.discussions.microsoft.com> wrote in message
news:E31BBA8A-F9CA-4BB2-B286-29B1062030B6@.microsoft.com...
> Hi there.
> I have a MS Distributed Transaction Coordinator qestion which doesnt
involve
> a clustered setup at all. I know this may not technically be the correct
> forum but I've solved other MSDTC issues here before so I was hoping...!
> Do you know whether any problems should be anticipated with distributed
> transactions if a series of linked or remote servers were set up on
machines
> with different operating systems? I'm about to set up a system with 2
> machines on Winows2003 and one on Windows NT => I just want to know
whether
> it's possible to get a distributed transaction to run ok across all 3
> servers...
> Any info would be appreciated!
>
Subscribe to:
Posts (Atom)