I believe that you can try this out in a test environment and doing a sync should give you an error message if the row is too large.

I thought the...

From what I can see when I look at my server, there is a constraint - as listed below

CONSTRAINT [unique_pubsrvdb] UNIQUE NONCLUSTERED

(

[pubid] ASC,

[subscriber_server] ASC,

[db_name] ASC

)

This is a unique...

Did you check that you still get the same results?

A group by will very probably change what data gets returned.

Given that @search=1 seems to have nothing to do with the query other than to determine if it should run at all, why not put it in an IF clause

IF...

If you are not replicating the same tables I would imagine you could, but if you have an overlap with the same table being replicated from both servers, I would...

I've not worked with that many tables before, but perhaps you could consider the following,

1. Group logical tables togther within a publication - if you have related tables then this...

Sounds to me like you have data being updated at both subscribers with the same data. This same data, on synchronisation, returns the error.

Or have I misread your post?

Typically, you...

Which SQL files are you looking at?

Typically a databases files (.mdf and .ldf - and .ndf if you have filegroups) are located by default in

C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data

I doubt you can do it from Enterprise manager but imagine that you could write the appropriate t-sql to determine what conflicts exist

You just need to right mix of base...

Using the Management Studio, drill down to the stored proceudre through database, programmability, stored procedures.

right click the stoerd procedure and select properties.

choose the permissions tab

Last on the list is view...

I can only suggest going back to square one by removing the exsting publisher and subscriber setup - right click Replication node in Management Studio, select disalbe Publishing and distributing

Then,...

You can specify it as part of the opions from the query analyser window (management studio).

Instead of "results to text" or "results to grid", you can use "results to file"...

No difference from the access that they currently have for SQL 2000.

Can't see where the problem lies if they couldn't cause damage in the existing system because all the permissions...

You could always try to set up a table to audit the actual data being inserted.

Essentially, create a separate table withte the following columns

CREATE TABLE audit_table_name

(

...

SQL CE 2.0 would be your most likely candidate.

Talks to SQL Server 2000 via the server side setup of SQL CE 2.0.

Does not require you to apply a different...