confused about pull

I have setup multiple merge replications that are continuously updating.
Now, we need to have laptops in the field that connect occasionally that
will merge. Because of that, I assume it needs merge PULL subscription.
I have had tons of problems and it has never worked. Right now it seems
to always be a permission issue.
First, I need to test this in the office to make sure it works. If it is
working, can I take that laptop out in the field, connect via the
internet, and it will work there with no changes? This is needed because
90% of the time the user is in the field, but occasionally he is in the
office, and I don't want to have to change configurations when he comes
and goes.
Next, to get a pull setup and functioning in the office, this seems to
require both access to SQL (via a sql login I created) AND access to the
server via a windows login - is this true? If so, what is the windows
login access for (the snapshot I beleive)?
So, I guess in a perfect world the laptop can be first configured and
replicated in the office (to get the snapshot) and then taken out of the
office and connect via the internet.
Does all of this sound reasonable. I know (according to Hilary) this is
a very complex issue and I am discovering it is. Hopefully this is like
a push/merge that seemed complex until it was working, then it was(is)
easy.
Let me know people's thoughts.
Thanks.
Darin
*** Sent via Developersdex http://www.codecomments.com ***
Darin,
the initial Initialization process will require access to the share holding
the snapshot files. This access is by default achieved using the sql server
agent and impersonation. If the account which the agent uses doesn't have
rights to the distributor's working folder (snapshot share) or if the
account is simply not recognised on this server, then there will be
problems. In the case of a non-trusted environment you then have to use an
alternative (usually FTP) to get the initialization going. Once it's going,
the merge agent uses whatever you've set up to do synchronization, over your
configured port. This can be trusted or sql authentication, and by default
it is also trusted.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Conflicts and String or Binary Data would be truncated

I have an application using SQL Server 2000 and Delphi
for the front end. I have 2 SQL Server, on each side of a
WAN and 15 offline users with Laptops that sync using
Merge replication. This app has been running for about 6
months now. Lately, I am getting a few conflicts saying
that the row was inserted or updated at the Laptop, but
could not be updated or inserted at the Server - String
or Binary Data would be truncated. The Merge agent
reports no errors, saying that the session succeeded. I
have a Trigger that updates a Datestamp field, but I have
the "NOT FOR REPLICATION" line at the top. I do not get
the error using the app, only when the user replicates.
Out of 15 users, 3 are getting the message in the
conflicts screen.
Any ideas.
Thanks,
John,
2 possibilities I can think of:
are the schemas identical on publisher and subscribers? If you have done a
nosync subscription with different schemas, this could be the cause.
If the schemas are the same, then there is a known issue if you are not yet
on sp3:
http://support.microsoft.com/default...ticle%3D319258
HTH,
Paul Ibison
|||Well we are at service pack 3 (I had them go into query
analyzer)and the schemas seem to be identical. It only
seems to happen to 3 of our laptop users and no on e els
gets the errors

>--Original Message--
>John,
>2 possibilities I can think of:
>
>are the schemas identical on publisher and subscribers?
If you have done a
>nosync subscription with different schemas, this could
be the cause.
>If the schemas are the same, then there is a known issue
if you are not yet
>on sp3:
>http://support.microsoft.com/default.aspx?scid=%
2Fservicedesks%2Fbin%2Fkbsearch.asp%3FArticle%3D31 9258
>HTH,
>Paul Ibison
>
>.
>
|||OK - can you try using DATALENGTH on hte problematic row's text data to
compare to the publisher. Also, can you check that the collations are the
same between publisher and subscriber (at column level).
Regards,
Paul Ibison
|||I will look into this on Monday. I really appreciate
your input.
Thank You
>--Original Message--
>OK - can you try using DATALENGTH on hte problematic
row's text data to
>compare to the publisher. Also, can you check that the
collations are the
>same between publisher and subscriber (at column level).
>Regards,
>Paul Ibison
>
>.
>

Conflicts and "String and Binary Datawould be truncated"

I have an application using SQL Server 2000 and Delphi
for the front end. I have 2 SQL Server, on each side of a
WAN and 15 offline users with Laptops that sync using
Merge replication. This app has been running successfully
for about 6 months now.
Lately, I am getting a few conflicts from 3 of the 15
offline users saying that the row was inserted or updated
at the Laptop, but could not be updated or inserted at
the Server - String or Binary Data would be truncated.
The Merge agent reports no errors, saying that the
session succeeded. I have a Trigger that updates a
Datestamp field when the app makes an update, but I have
the "NOT FOR REPLICATION" line at the top. I do not get
the error using the app, only when the selected users
replicates. Out of 15 users, 3 are getting the message in
the conflicts screen.
Thanks for the Help.
Steve
Steve,
it could be a service pack issue. Have a look at
http://support.microsoft.com/default...icle%3D319258.
Also, you could do some logging from the trigger to a separate table, just
to confirm that it is/isn't firing during the replication process.
HTH,
Paul Ibison