Re: Trasactional Replication problems
- From: petery@xxxxxxxxxxxxxxxxxxxx (Peter Yang [MSFT])
- Date: Wed, 23 Nov 2005 03:29:16 GMT
Hello,
>I mean during a replication, one of the tables had one line.This table
>should have 13000 lines after a snapshot.
>Is possible that a snapshot may have errors and not reporting it? Like
>not send all lines from the server.
It seems that the snapshot is not replicate to the subscriber properly. You
may want to check the snapshot folder and enable logging of distrubution
agent to see if there is any error when apply snapshot to subscriber.
312292 HOW TO: Enable Replication Agents for Logging to Output Files in SQL
Server
<http://support.microsoft.com/default.aspx?scid=kb;EN-US;312292>
> The subscriptions are send from the server. They aren't anonymous
subscribers.
> Some of the machines are in local network and have problems too.
> If I configure "MaxDeliveredTransactions" to a number that is not zero,
>all data will be transfer to the subscribers in this transactions?
The default is 0, which means that all available transactions are
delivered. Other values can be used to control the number of transactions
downloaded during a Run operation of
> The "sp_expired_subscription_cleanup" will erase the data from the
>server even this data aren't delivered to the subscribers?
> How much time the subscribers will be active?
Periodically checks the status of all the subscriptions of every
publication and identifies those that have expired. This stored procedure
is executed at the Publisher on any database.
By default, replicated data is maintained in the distribution database for
72 hours. Subscriptions that have not retrieved the image within the
maximum time are disabled and must be resynchronized.This is controled by
MaxDistributionRetention value.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
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.
--------------------
| Thread-Topic: Trasactional Replication problems
| thread-index: AcXvZr9MX27uVBWjTWq0rtjraq6ioQ==
| X-WBNR-Posting-Host: 200.142.104.78
| From: =?Utf-8?B?TVNHIFNlcnZpY29zIGRlIEluZm9ybWF0aWNh?=
<message@xxxxxxxxxxxxxxxx>
| References: <C3ED2015-3E91-45C1-AB6E-4336ED0E005C@xxxxxxxxxxxxx>
<e0WOxet7FHA.4036@xxxxxxxxxxxxxxxxxxxx>
| Subject: Re: Trasactional Replication problems
| Date: Tue, 22 Nov 2005 05:15:02 -0800
| Lines: 91
| Message-ID: <D891B917-671F-4010-87F4-956E60ED6670@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.replication
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.replication:66864
| X-Tomcat-NG: microsoft.public.sqlserver.replication
|
| Sorry.
|
| I mean during a replication, one of the tables had one line.This table
| should have 13000 lines after a snapshot.
| Is possible that a snapshot may have errors and not reporting it? Like
| not send all lines from the server.
|
| The subscriptions are send from the server. They aren't anonymous
| subscribers.
| Some of the machines are in local network and have problems too.
|
| If I configure "MaxDeliveredTransactions" to a number that is not
zero,
| all data will be transfer to the subscribers in this transactions?
|
| The "sp_expired_subscription_cleanup" will erase the data from the
| server even this data aren't delivered to the subscribers?
| How much time the subscribers will be active?
|
| Thanks,
|
| --
| MSG Servicos de Informatica
| Rio de Janeiro / Brazil
|
|
| "Hilary Cotter" wrote:
|
| > 1) They will be high if subscribers are offline or if you are not using
| > named subscribers. Basically the transactions and commands have to
remain in
| > the distribution database until they are applied on all subscribers.
With
| > anonymous subscribers replication doesn't track which subscribers have
got
| > the transactions so it keeps the transactions the length of the
retention
| > period.
| >
| > 2) Subscription need to expire if they have been offline too long. What
| > typically happens is the if a subscriber is offline too long the
| > distribution database gets huge and performance degrades for the log
reader
| > agents writing to it. Also the length of time to sync the commands when
a
| > subscriber comes back online is longer than the time that would be take
to
| > apply a new snapshot.
| >
| > I am having a hard time understanding this statement
| >
| > > The transactional replication delete data from subscriptions to copy
| > > all data again?
| > > In a test, I see one table with one row in the middle of de
| > > replication, when this table should have 13000 rows.
| > >
| >
| > Transactional replication will delete all the data on the subscriber by
| > default when a new subscription is deployed. What I don't understand is
the
| > next statement about a row in the middle. Could you please clarify what
you
| > mean.
| >
| > --
| > 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
| >
| > "MSG Servicos de Informatica" <message@xxxxxxxxxxxxxxxx> wrote in
message
| > news:C3ED2015-3E91-45C1-AB6E-4336ED0E005C@xxxxxxxxxxxxxxxx
| > > Hi,
| > > I am using a transactional replication in a database and I don't
need to
| > > transfer data from subscriptions.
| > > The subscriptions are only for read locally.
| > >
| > > I have some questions about replication:
| > >
| > > - Why the number of transaction is so high? Reach 743952
transactions
| > > and
| > > 2559136 commands in one of subscriptions.
| > >
| > > - Why the subscriptions expire and need to reinitialize? I don't
know
| > > how
| > > to avoid expire de subscriptions.
| > >
| > > - The transactional replication delete data from subscriptions to
copy
| > > all data again?
| > > In a test, I see one table with one row in the middle of de
| > > replication, when this table should have 13000 rows.
| > >
| > > Thanks and so long,
| > > --
| > > MSG Servicos de Informatica
| > > Rio de Janeiro / Brazil
| >
| >
| >
|
.
- References:
- Re: Trasactional Replication problems
- From: Hilary Cotter
- Re: Trasactional Replication problems
- From: MSG Servicos de Informatica
- Re: Trasactional Replication problems
- Prev by Date: Re: Replication with Locked tables
- Next by Date: Re: Which replication topology?
- Previous by thread: Re: Trasactional Replication problems
- Next by thread: Merge Replication fails on deadlocked
- Index(es):
Relevant Pages
|
