Merge & Snapshot Clarification

Hope to get a lil info on the settings for this scenario...
i got Table A that sits on different branches, and the data it contains
should be merged with Table A in the HQ. So I've set this to use the Merge
replication.
So to ensure all branches have the same data in Table A, do i have to ensure
that the replication is executed on a "cascading" timeline ? Branch A from
12am-1am , Branch B from 2am - 3am , etc ?
and finally
i got Table B that also sits on different branches, but the data is just to
be appended to Table B in the HQ and the individual branches have their
original Table B intact... What replication do i use for this ? I tried
snapshot , but that copies the entire table over overwriting the HQs table..
i want it to append. 1 way flow of data. How do i achieve this ?
Thanks in advance.
Outgoing mail is certified Virus Free. (well i'd like to think it is.. )
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.712 / Virus Database: 468 - Release Date: 27/06/2004
okie im partly there already...
i found a setting for the snapshot to keep the table intact on the
destination , so now on the snapshot replication it doesnt overwrite the
data but appends like i wanted and the original tables on the branches are
left as is...
coming to the next problem, now with 2 publications (one merge TableA , one
snapshot Table B) the merge doesnt seem to be working.. i keep getting this
error :
"The process could not drop one or more tables because the tables are being
used by other publications.
(Source: Merge Replication Provider (Agent); Error number: -2147200976)"
How do you manage more than 1 publication so that this does not occur ? is
there a certain gap (time) to have between them ? i ran them thru the right
click synchronize option.
"Mike Smith" <test@.test.com> wrote in message
news:O9tssKFaEHA.2296@.TK2MSFTNGP10.phx.gbl...
> Hope to get a lil info on the settings for this scenario...
> i got Table A that sits on different branches, and the data it contains
> should be merged with Table A in the HQ. So I've set this to use the Merge
> replication.
> So to ensure all branches have the same data in Table A, do i have to
ensure
> that the replication is executed on a "cascading" timeline ? Branch A from
> 12am-1am , Branch B from 2am - 3am , etc ?
> and finally
> i got Table B that also sits on different branches, but the data is just
to
> be appended to Table B in the HQ and the individual branches have their
> original Table B intact... What replication do i use for this ? I tried
> snapshot , but that copies the entire table over overwriting the HQs
table..
> i want it to append. 1 way flow of data. How do i achieve this ?
> Thanks in advance.
>
> --
> Outgoing mail is certified Virus Free. (well i'd like to think it is.. )
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.712 / Virus Database: 468 - Release Date: 27/06/2004
>
Outgoing mail is certified Virus Free. (well i'd like to think it is.. )
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.712 / Virus Database: 468 - Release Date: 27/06/2004
|||Mike, it sounds like you are bumping into the same problem as what you have
with the first table/publication.
Can you double click on your merge agent in EM, and see what the name of the
problem table is in the Error Details dialog?
It is table a or table b?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Mike Smith" <test@.test.com> wrote in message
news:OmqH3XFaEHA.2516@.TK2MSFTNGP10.phx.gbl...
> okie im partly there already...
> i found a setting for the snapshot to keep the table intact on the
> destination , so now on the snapshot replication it doesnt overwrite the
> data but appends like i wanted and the original tables on the branches are
> left as is...
> coming to the next problem, now with 2 publications (one merge TableA ,
one
> snapshot Table B) the merge doesnt seem to be working.. i keep getting
this
> error :
> "The process could not drop one or more tables because the tables are
being
> used by other publications.
> (Source: Merge Replication Provider (Agent); Error number: -2147200976)"
> How do you manage more than 1 publication so that this does not occur ? is
> there a certain gap (time) to have between them ? i ran them thru the
right[vbcol=seagreen]
> click synchronize option.
>
> "Mike Smith" <test@.test.com> wrote in message
> news:O9tssKFaEHA.2296@.TK2MSFTNGP10.phx.gbl...
Merge[vbcol=seagreen]
> ensure
from
> to
> table..
>
> --
> Outgoing mail is certified Virus Free. (well i'd like to think it is.. )
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.712 / Virus Database: 468 - Release Date: 27/06/2004
>
|||well the error details doesnt say what table , but currently that
publication is set only to 1 table and thats table A itself..
is it a Service pack issue ? saw something somewhere on how this could be a
factor..
This brings me to yet another issue.. im using MSDE to synch with a SQL
SERVER 2000 database on the same machine.
So i installed SP3 for the SQL server 2000 (default instance)
and for the MSDE i installed it via
C:\sql2ksp3MSDE\MSDE\setup.exe /upgradesp sqlrun INSTANCENAME=NETSDK
DISABLENETWORKPROTOCOLS=1 BLANKSAPWD=1
Now my SQL Server Agent wont run .. i get the error "the dependency service
does not exist of marked for deletion" when i try and start the service..
hmmm i got the command line off the readme file in the sp3 cause it was
trying to install it over the default instance... im guessing
DISABLENETWORKPROTOCOLS=1 should not have been there?
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:ufCuuCNaEHA.1152@.TK2MSFTNGP09.phx.gbl...
> Mike, it sounds like you are bumping into the same problem as what you
have
> with the first table/publication.
> Can you double click on your merge agent in EM, and see what the name of
the[vbcol=seagreen]
> problem table is in the Error Details dialog?
> It is table a or table b?
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Mike Smith" <test@.test.com> wrote in message
> news:OmqH3XFaEHA.2516@.TK2MSFTNGP10.phx.gbl...
are[vbcol=seagreen]
> one
> this
> being
is[vbcol=seagreen]
> right
contains[vbcol=seagreen]
> Merge
> from
just[vbcol=seagreen]
their[vbcol=seagreen]
tried[vbcol=seagreen]
is.. )
>
well the error details doesnt say what table , but currently that
publication is set only to 1 table and thats table A itself..
is it a Service pack issue ? saw something somewhere on how this could be a
factor..
This brings me to yet another issue.. im using MSDE to synch with a SQL
SERVER 2000 database on the same machine.
So i installed SP3 for the SQL server 2000 (default instance)
and for the MSDE i installed it via
C:\sql2ksp3MSDE\MSDE\setup.exe /upgradesp sqlrun INSTANCENAME=NETSDK
DISABLENETWORKPROTOCOLS=1 BLANKSAPWD=1
Now my SQL Server Agent wont run .. i get the error "the dependency service
does not exist of marked for deletion" when i try and start the service..
hmmm i got the command line off the readme file in the sp3 cause it was
trying to install it over the default instance... im guessing
DISABLENETWORKPROTOCOLS=1 should not have been there?
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:ufCuuCNaEHA.1152@.TK2MSFTNGP09.phx.gbl...
> Mike, it sounds like you are bumping into the same problem as what you
have
> with the first table/publication.
> Can you double click on your merge agent in EM, and see what the name of
the[vbcol=seagreen]
> problem table is in the Error Details dialog?
> It is table a or table b?
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Mike Smith" <test@.test.com> wrote in message
> news:OmqH3XFaEHA.2516@.TK2MSFTNGP10.phx.gbl...
are[vbcol=seagreen]
> one
> this
> being
is[vbcol=seagreen]
> right
contains[vbcol=seagreen]
> Merge
> from
just[vbcol=seagreen]
their[vbcol=seagreen]
tried[vbcol=seagreen]
is.. )
>