number of records is larger in subscriber

Hi!
Anyone knows howcome i end up with more records in the subscriber than in
the publisher? I'm using transactional replication, and the subscriber is a
standby server, no inserts are done in this server.
Any suggestions?
Thx!
Has the data been fully synchronized? Run the command sp_browsereplcmds
after running the cleanup agent to ensure nothing is in the pipeline. What
I'm thinking is that you have some deletes that haven't yet been replicated.
If all commands have indeed been sent down, then chack that the log reader
agent hasn't been turned off. if this is still not the issue, then you'll
have to synchronize the data by hand (I use sql data compare from RedGate
for this).Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi!
Thks for the hint, i'll check on that, but now i've got a worse case to
solve.... the distribution server (which is also my subscriber) began to
mark all databases as suspect, starting with distribution db and continue to
mark every other db. So far we think this behavior was a consequence of the
replication, no other job o anything else is running in this server. Any
suggestions on this? (we've already recovered the db's, but cannot afford
this to happen on my production server)
Thx a lot!
"Paul Ibison" wrote:

> Has the data been fully synchronized? Run the command sp_browsereplcmds
> after running the cleanup agent to ensure nothing is in the pipeline. What
> I'm thinking is that you have some deletes that haven't yet been replicated.
> If all commands have indeed been sent down, then chack that the log reader
> agent hasn't been turned off. if this is still not the issue, then you'll
> have to synchronize the data by hand (I use sql data compare from RedGate
> for this).Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>

Number limit of table columns in transactional replication

I was setting up transactional replication for a big table and got the
following error message:
The article cannot be created on table 'TEST' because it has more than 255
columns
Is that the limit of replication in SQL Server 2000? If yes, Is there any
way to increase the limit, or it can be configured?
Thanks!
This is the limit and it isn't configurable . One possible solution is to
partition the table into smaller tables and replicate each one separately.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)