Hi,
In my distribution data base, the system tables creation date is showing Dec
2002, but i replicated the database on feb 2006,
I want to know why the table creation date is in year 2002.
Please clarify me.
rgds,
Soura
Soura,
this is the date that the distribution database was created using
sp_adddistributiondb.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Showing posts with label creation. Show all posts
Showing posts with label creation. Show all posts
Saturday, February 25, 2012
Sunday, February 19, 2012
Distributed transactions and replication creation: which is the link?
Hi all,
I'm getting a strange error after reinstalling and recovering a database
server on a new hardware. It was posted on
http://groups.google.com/group/micro...f6213ef6965f41
My new questions are:
-Is replication (or at least replication creation proccess) related to
distributed transaction coordinator (MSDTC)?
-How can I get assured the MSDTC is working properly? Is it possible to
activate a detailed, (I mean verbose) log of activity? In the Event
Viewer/Application Log the only event related to MSDTC is informative: 4156
"Session idle timeout over, tearing down the session" once or twice a day
-In the case the distributor and the publishers are located in separate
servers, if there is involved a distributed transaction, is it the
distributor who initiates the distributed transaction towards the publisher?
-In the Enterprise Manager, in the properties of the server, Connections
tab, "Enforce distributed transactions (MTS)" checkbox has any influence in
the replication configuration? In the previous configuration we tested
distributed transaction between these two servers and moved this checkbox
and other related configuration parameters but had no problems with the
working replication, even we recreated the publication many times without
any problems.
I have no clear clues. Any hint is welcomed.
Thanks in advance
Sammy
The problem was solved the following way:
The publisher server had "Enforce distributed transaction (MTS)" checked. We
unchecked this and restarted all the services, including MSDTC. After that
the problem disappeared.
Hope it helps anybody else
Sammy
I'm getting a strange error after reinstalling and recovering a database
server on a new hardware. It was posted on
http://groups.google.com/group/micro...f6213ef6965f41
My new questions are:
-Is replication (or at least replication creation proccess) related to
distributed transaction coordinator (MSDTC)?
-How can I get assured the MSDTC is working properly? Is it possible to
activate a detailed, (I mean verbose) log of activity? In the Event
Viewer/Application Log the only event related to MSDTC is informative: 4156
"Session idle timeout over, tearing down the session" once or twice a day
-In the case the distributor and the publishers are located in separate
servers, if there is involved a distributed transaction, is it the
distributor who initiates the distributed transaction towards the publisher?
-In the Enterprise Manager, in the properties of the server, Connections
tab, "Enforce distributed transactions (MTS)" checkbox has any influence in
the replication configuration? In the previous configuration we tested
distributed transaction between these two servers and moved this checkbox
and other related configuration parameters but had no problems with the
working replication, even we recreated the publication many times without
any problems.
I have no clear clues. Any hint is welcomed.
Thanks in advance
Sammy
The problem was solved the following way:
The publisher server had "Enforce distributed transaction (MTS)" checked. We
unchecked this and restarted all the services, including MSDTC. After that
the problem disappeared.
Hope it helps anybody else
Sammy
Subscribe to:
Posts (Atom)