Re: Replication Monitor didn't work because different collations

can you enable logging to see which object it is breaking on? Then post the
DDL for this object.

Here's a link on how to do that.
http://support.microsoft.com/kb/312292/en-us

--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

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



"Katja" <Katja@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8CC06C48-F74F-4BBE-BB5F-C03430746BE1@xxxxxxxxxxxxxxxx
Hi,

We have setup WinServer 2003, SQL 2005 filtered merge replication.

We couldn't get Replication Monitor work at our new testing server.
It didn't show the publication we had created.
Finally we realized it was because we had different collations at server
level and at user database/distribution db.
("SQL_SwedishStd_Pref_CP1_CI_AS"
and "Finnish_Swedish_CI_AS").
I guess there is no way to use SQL_SwedishStd_Pref_CP1_CI_AS collation at
normal setup (maybe command prompt setup could...)
We changed collations to match the server collation and Replication
monitor
started to work, great.

After this change we started all (4) publication snapshots.
3 went ok, 1 didn't.
We deleted that problem publication and tried to create it again. No luck.
We can't add any articles to the publication.

Does anybody have any ideas what this error could mean?
Perhaps that collation change broke something?


Creating Publication
- Creating Publication 'Keskus96' (Success)
* SQL Server created publication 'Keskus96'.
- Adding article 1 of 1 (Error)
Messages
* SQL Server Management Studio could not create article 'BXB'. (New
Publication Wizard)
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
------------------------------
Could not resolve expression for schemabound object or constraint.
Changed database context to 'MK2000'. (Microsoft SQL Server, Error: 2791)

- Starting the Snapshot Agent (Stopped)

Any ideas would be appreciated. Thanks.
-Katja


.

Relevant Pages

  • RE: Error creating new push subscription after deleting the existi
    ... To drop a push subscription to all articles for a transactional ... At the Publisher, open SQL Server Enterprise Manager, expand a server ... group, expand the Replication folder, expand the Publications folder, click ... the publication that has the subscription you want to delete, ...
    (microsoft.public.sqlserver.replication)
  • When do we need to delete/recreate a subscription?
    ... I'm using SQL Server for Merge replication and I looking for a list of ... Deleting a sub. ... when modifying a publication table's structure (like ...
    (microsoft.public.sqlserver.replication)
  • HELP: Dropped table column causes sp_addmergearticle to fail with replication
    ... I'm setting up merge replication on sql server 2000 sp3. ... there is no identity column in this table ... The article 'tkDPLRS' could not be added to the publication 'TEST1'. ...
    (microsoft.public.sqlserver.replication)
  • Re: Replication over a firewall
    ... for a publication named "MyDB" should be "c:\MyDB"? ... Since it works inside the firewall, i think items 1,2 and 3 are ok. ... make sure the snapshot folder name is the default name that SQL Server ... merge replication just has a lot of points of failure ...
    (microsoft.public.sqlserver.ce)
  • Re: Transactional replication from SQL Server 2005 to SQL Server 7 - how?
    ... SQL Server 7.0 from the SQL2005 management tools but I would encourage to ... primary keys are replicated as unique indexes if you ... configure replication using the SQL2000 Enterprise Manager. ... If you plan to reinitialize your SQL2000->SQL2005 subscription in the ...
    (microsoft.public.sqlserver.replication)