Sunday, March 25, 2012
DownloadGenerationsPerBatch and SQLMerge
Publisher is Sql Server 2000 SP4, subscribers are laptops using MSDE SP4.
Using anonymous subscribers that use the SQLMerge object to invoke
replication. We've run into issues where the publisher has deleted subscriber
records so we are changing all of our FKs for NFR and want to set
DownloadGenerationsPerBatch to 2000.
However, all documentation and newsgroups just talk about a command line
argument. How do I set DownloadGenerationsPerBatch on the SQLMerge object.
create a profile for this, and use the profile name option in the activeX
merge object - ie ProfileName
But I think you could solve your problem by using
compensate_for_errors=false in sp_addmergearticle
Consult this kb for more info
http://support.microsoft.com/kb/828637
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
"Buzz" <buzz@.online.nospam> wrote in message
news:C26C42E3-906B-4CFA-ADBE-81183E43C890@.microsoft.com...
> Using Merge replication.
> Publisher is Sql Server 2000 SP4, subscribers are laptops using MSDE SP4.
> Using anonymous subscribers that use the SQLMerge object to invoke
> replication. We've run into issues where the publisher has deleted
subscriber
> records so we are changing all of our FKs for NFR and want to set
> DownloadGenerationsPerBatch to 2000.
> However, all documentation and newsgroups just talk about a command line
> argument. How do I set DownloadGenerationsPerBatch on the SQLMerge object.
>
|||Thanks for pointing me in the right direction! Both with profiles and the new
article option!
"Hilary Cotter" wrote:
> create a profile for this, and use the profile name option in the activeX
> merge object - ie ProfileName
> But I think you could solve your problem by using
> compensate_for_errors=false in sp_addmergearticle
> Consult this kb for more info
> http://support.microsoft.com/kb/828637
> --
> 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
> "Buzz" <buzz@.online.nospam> wrote in message
> news:C26C42E3-906B-4CFA-ADBE-81183E43C890@.microsoft.com...
> subscriber
>
>
sql
Tuesday, February 14, 2012
Does the transaction log on a publisher SQL server get truncated when the database is back
The setting is SQL server 7, on Windows NT.
If the distributor can not access the log on the publisher database ( but
subscribers are not deleted yet), will the full backup of the publisher
database truncate the transaction log? My guess is, it will not truncate the
log.
Can any one confirm please?
Thanks,
MoklesFull backups don't truncate the log; the log is truncated by BACKUP log.
From the Books Online:
<Excerpt href="http://links.10026.com/?link=\tsqlref.chm::/ts_ba-bz_35ww.htm">
Once the log is backed up, the space may be truncated when no longer
required by replication or active transactions.
</Excerpt
I believe the data is considered required for replication until retrieved by
the distributor
--
Hope this helps.
Dan Guzman
SQL Server MVP
"mokles" <mokles@.rogers.com> wrote in message
news:ncWdnd5XiKzAojvfRVn-sA@.rogers.com...
> Hello All,
> The setting is SQL server 7, on Windows NT.
> If the distributor can not access the log on the publisher database ( but
> subscribers are not deleted yet), will the full backup of the publisher
> database truncate the transaction log? My guess is, it will not truncate
> the
> log.
> Can any one confirm please?
> Thanks,
> Mokles|||Dan Guzman,
Thanks for your confirmation and explanation.
Mokles
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:ZSspe.1864$751.1493@.newssvr30.news.prodigy.co m...
> Full backups don't truncate the log; the log is truncated by BACKUP log.
> From the Books Online:
> <Excerpt href="http://links.10026.com/?link=\tsqlref.chm::/ts_ba-bz_35ww.htm">
> Once the log is backed up, the space may be truncated when no longer
> required by replication or active transactions.
> </Excerpt>
> I believe the data is considered required for replication until retrieved
by
> the distributor
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "mokles" <mokles@.rogers.com> wrote in message
> news:ncWdnd5XiKzAojvfRVn-sA@.rogers.com...
> > Hello All,
> > The setting is SQL server 7, on Windows NT.
> > If the distributor can not access the log on the publisher database (
but
> > subscribers are not deleted yet), will the full backup of the publisher
> > database truncate the transaction log? My guess is, it will not truncate
> > the
> > log.
> > Can any one confirm please?
> > Thanks,
> > Mokles