No COLLATE definition

Hi,
during the initialization of the subscriber from a mergepublication the
COLLATE definitions were not defined in the created tables of the subscribers.
In the snapshot directory I searched the right schema script and I saw that
the collate definition in the create table command was not defined.
Is this a bug or is it a result of a wrong setting of the publisher or
subscriber ?
How can I solve the problem ?
Best regards
Axel Lanser
On the article properties, snapshot tab there is a checkbox for Collation -
by default it is not taken from the publisher to the subscriber.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi,
my snapshot has more then 200 articles. Is there a way to set the collation
for all articles automaticaly.
Best regards
Axel Lanser
"Paul Ibison" wrote:

> On the article properties, snapshot tab there is a checkbox for Collation -
> by default it is not taken from the publisher to the subscriber.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>

NFR with merge in em shows weird seed

I've set identity columns to automatic ranges with merge. The publisher
ranges is for a million and the subscriber side is for a million. Now, when I
go to the EM, and go to the Desgin Table in EM for a table, I see the
identity seed to 1. Is this normal? But when I ran the script and everything
and also when I go to the article properties, it shows the correct identity
ranges. Please let me know. thank you very much...
On the publisher this is correct. On the subscriber it should be at
1,000,001.
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
"Tejas Parikh" <TejasParikh@.discussions.microsoft.com> wrote in message
news:6B8E4284-B565-4D0C-90E5-5948AA21E136@.microsoft.com...
> I've set identity columns to automatic ranges with merge. The publisher
> ranges is for a million and the subscriber side is for a million. Now,
> when I
> go to the EM, and go to the Desgin Table in EM for a table, I see the
> identity seed to 1. Is this normal? But when I ran the script and
> everything
> and also when I go to the article properties, it shows the correct
> identity
> ranges. Please let me know. thank you very much...

Newbie: Merge Replication

I have setup merge replication and it appears to be working fine
multiple publishers to a single subscriber. with continuous push
subscription
If the subscribing SQL Server is unavailable for a period of time the
replication monitor shows an error
"could not connect to SERVERNAME"
Ok so fairly easy to understand.
Now when the subscribing server is available again it does not seem to
connect again. I can click the "start synchronizing" option from the
replication monitor, however I would have thought continuous updating would
reconnect when available.
If this is the case,
1. How can I make it connect/start sycnronising again sooner automatically,
without user invervention?
2. Am I able to call the start synchronising feature through commands so
that I can have a force update type feature through code.
Thanks in advance.
Cheers,
Tim
Timmeah,
you could schedule the merge agent to run once a minute rather than
continuously. Alternatively you could force the job steps to run in a loop.
To start the merge agent in TSQL you can use sp_start_job.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)