Questions[merge-replication](server)

I'm looking for a couple different things here.

From what I can find, Workgroup edition supports up to 25 subscribers per publication. Does anyone know the limit, if there is one, to the number of subs per pub in both Enterprise and Standard editions of SQL 2008 R2? (2008 info is good too)

Also, anyone have any experience with 50+ subs against one pub? We are looking to get some ideas on what performance looked like with that many subs. Did you need to add an additional pub to handle the load? Were there issues when a certain number of pubs tried to sync at the same time?

I have a Win Form, Data Entry, application that uses 4 seperate Data Bases. This is an occasionally connected app that uses Merge Replication (SQL 2005) to stay in Sync. This is working just fine. The next hurdle I am trying to tackle is adding Filters to my Publications.

Right now we are replicating 70mbs, compressed, to each of our 150 subscribers when, truthfully, they only need a tiny fraction of that. Using Filters I am able to accomplish this(see code below) but I had to make a mapping table in order to do so. This mapping table consists of 3 columns. A PrimaryID(Guid), WorkerName(varchar), and ClientID(int).

The problem is I need this table present in all FOUR Databases in order to use it for the filter since, to my knowledge, views or cross-db query's are not allowed in a Filter Statement.

What are my options?

Seems like I would set it up to be maintained in 1 Database and then use Triggers to keep it updated in the other 3 Databases. In order to be a part of the Filter I have to include that table in the Replication Set so how do I flag it appropriately.

Is there a better way, altogether?

SELECT <published_columns> FROM [dbo].[tblPlan] WHERE [ClientID] IN (select ClientID from [dbo].[tblWorkerOwnership] where WorkerID = SUSER_SNAME())

Which allows you to chain together Filters, this next one is below the first one so it only pulls from the first's Filtered Set.

SELECT <published_columns> FROM [dbo].[tblPlan] INNER JOIN [dbo].[tblHealthAssessmentReview] ON [tblPlan].[PlanID] = [tblHealthAssessmentReview].[PlanID]

How do I, properly, ALTER a StoredProcedure in a SQL 2005 Merge Replication?

I just need to add a Column. I already successfully added it to the Table and I now need to add it to a SP. I did so but now it will not synchronize with the following error -->

Insert Error: Column name or number of supplied values does not match table definition. (Source: MSSQLServer, Error number: 213)

Add my comment below here for easier viewing

Yes the table change was already replicated. THEN the Stored PRocedure quit working as the columns were off so I did an ALTER on the stored procedure and tried to replicate that. Now it won't sync

I need to add a couple of columns to a table that is a part of a replication set. It is not a constraint coulumn or a part of any article filters and it allows NULL. I have a pretty good idea that I can run this --> ALTER TABLE tblPlanDomain ADD ReportWageES VARCHAR (100) NULL

and NOT force all my clients to reinitialize but I was hoping for some reassurance. Can anyone verify this one way or the other for me?

Thanks,

Edit: Addtnl Info

This is what I am talking about --> http://msdn.microsoft.com/en-us/library/ms151870.aspx

It would seem, based on that, that the answer to my question is NO but I would still like a human confirmation.

I have Merge Replication set up with a SQL 2005 Publisher/Distributor and roughly 100 SQL 2005 Express Subscribers. Everything was working fine for months and now all of a sudden everyone is getting the below errors.

I have been Googling around but to no avail. Can anyone offer some insight? I even tried deleting a user's Subscription. I also tried running -->

sp_adjustpublisheridentityrange @publication='MyDB'

Anyway, here are the errors -->

Error messages:
The Publisher failed to allocate a new set of identity ranges for the subscription. This can occur when a Publisher or a republishing Subscriber has run out of identity ranges to allocate to its own Subscribers or when an identity column data type does not support an additional identity range allocation. If a republishing Subscriber has run out of identity ranges, synchronize the republishing Subscriber to obtain more identity ranges before restarting the synchronization. If a Publisher runs out of identit (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199417)
Get help: http://help/MSSQL_REPL-2147199417
Not enough range available to allocate a new range for a subscriber. (Source: MSSQLServer, Error number: 20668)
Get help: http://help/20668
Failed to allocate new identity range. (Source: MSSQLServer, Error number: 21197)
Get help: http://help/21197