MSrepl_tran_version - needed or not?

Hi
Can someone please tell me, when i setup a publication for
transaction replication (push only), sometimes it says:
"SQL Server requires that all articles in a publication
allowing updatable subscriptions contain a
uniqueidentifier column named 'MSrepl_tran_version' used
for tracking changes to the replicated data. SQL Server
will add such a column to published tables that do not
have one"
But other times it does not ask to do this, and i have
successfully had a replication running without the
requirements is says. Do i need it or not?
Hi
If you want the changes to be replicated from the subscriber to publisher,
using immediate updating or queed updating, it becomes a requirement that
uniqueidentifier column is needed. If you dont want the reverse update, then
you may not need that column. Hope it helps
shrini
"gravity" <anonymous@.discussions.microsoft.com> wrote in message
news:1be901c42700$200f1880$a301280a@.phx.gbl...
> Hi
> Can someone please tell me, when i setup a publication for
> transaction replication (push only), sometimes it says:
> "SQL Server requires that all articles in a publication
> allowing updatable subscriptions contain a
> uniqueidentifier column named 'MSrepl_tran_version' used
> for tracking changes to the replicated data. SQL Server
> will add such a column to published tables that do not
> have one"
>
> But other times it does not ask to do this, and i have
> successfully had a replication running without the
> requirements is says. Do i need it or not?

MSDTC fails on Windows 2000 Advanced Server SP4

I have a VB6 application that uses MTS in a COM+ package for
transaction based processing over MSDTC. This application was working
fine when run from the SQL Server machine on Windows 2000 Advanced
Server until the latest security updates were installed. Now the
application fails to connect to SQL Server when the call is made inside
a transaction context within MTS/COM+
I have verified that MSDTC is started
The DTCTester tool runs successfully
RPC port 135 is open
This application runs fine on a Windows 2000 Server machine with SP4.
What is different about Windows 2000 Advanced Server such that it no
longer works after applying security updates (SP4)?
?s your SQL server and application server are in same domain, do you have
firewall etc between SQL Server and appl. server?
We had problems after we install Windows 2003 SP1 with MSDTC, we select No
Authantication Required and the problem is gone. Maybe because of you have
applied security patches you are having the same problem.
Check out:
http://support.microsoft.com/?id=883960
Hope this helps.
"dhalb@.comcast.net" wrote:

> I have a VB6 application that uses MTS in a COM+ package for
> transaction based processing over MSDTC. This application was working
> fine when run from the SQL Server machine on Windows 2000 Advanced
> Server until the latest security updates were installed. Now the
> application fails to connect to SQL Server when the call is made inside
> a transaction context within MTS/COM+
> I have verified that MSDTC is started
> The DTCTester tool runs successfully
> RPC port 135 is open
> This application runs fine on a Windows 2000 Server machine with SP4.
> What is different about Windows 2000 Advanced Server such that it no
> longer works after applying security updates (SP4)?
>

MSDTC fails on Windows 2000 Advanced Server SP4

I have a VB6 application that uses MTS in a COM+ package for
transaction based processing over MSDTC. This application was working
fine when run from the SQL Server machine on Windows 2000 Advanced
Server until the latest security updates were installed. Now the
application fails to connect to SQL Server when the call is made inside
a transaction context within MTS/COM+
I have verified that MSDTC is started
The DTCTester tool runs successfully
RPC port 135 is open
This application runs fine on a Windows 2000 Server machine with SP4.
What is different about Windows 2000 Advanced Server such that it no
longer works after applying security updates (SP4)'?s your SQL server and application server are in same domain, do you have
firewall etc between SQL Server and appl. server?
We had problems after we install Windows 2003 SP1 with MSDTC, we select No
Authantication Required and the problem is gone. Maybe because of you have
applied security patches you are having the same problem.
Check out:
http://support.microsoft.com/?id=883960
Hope this helps.
"dhalb@.comcast.net" wrote:

> I have a VB6 application that uses MTS in a COM+ package for
> transaction based processing over MSDTC. This application was working
> fine when run from the SQL Server machine on Windows 2000 Advanced
> Server until the latest security updates were installed. Now the
> application fails to connect to SQL Server when the call is made inside
> a transaction context within MTS/COM+
> I have verified that MSDTC is started
> The DTCTester tool runs successfully
> RPC port 135 is open
> This application runs fine on a Windows 2000 Server machine with SP4.
> What is different about Windows 2000 Advanced Server such that it no
> longer works after applying security updates (SP4)'
>