SQL2005 Merge replication Help! Help!

  • dbo.conflict_GenDev_Tables_tb_ApptStudioNotes

    The above table has been deleted from system.tables in my GenDev database

    When a conflict arises the system does not have any place to put the conflict so it can be resolved. How do I create this table again?

    Any information would be very much appreciated

  • Can you restore from a backup?

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • NO - That is one option I do not have

  • So, basically you don't back up the database, and someone deleted a system table that you need?

    I'm really not sure what to do about that. I tried a Google search for that table name and it came back with zero results.

    How was the table created in the first place? (I'm not myself familiar with Merge replication.) Is it part of setting up the replication?

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • Yes we do backups. I should have said that's a option I would rather not use right now because of all the tranactions that have occured in the last 4 days.

    Yes - Merge replication will create a dbo.conflict table for every replicated table.

    I have done my research on google also and was not getting anywhere hence the post.


  • Yes we do backups. I should have said that's a option I would rather not use right now because of all the tranactions that have occured in the last 4 days.

    I once had a similar case in SQL 2000 there some conflict tables simply were not created. Back then you could create a table with the required layout and name it the way you needed. Afterwards you must run EXEC sp_MS_marksystemobject 'myConflictTable' to mark it as a system object. If you don't do that replication will not use the table.

    Not sure if it will work for SQL2005, but it's worth a try.

    [font="Verdana"]Markus Bohse[/font]

  • Also - I can create the table becuase I have the definition but it is a User table "U". Do you know of an easy way to change that user table to a system table? Change category?

  • OK - Were you reading my mind or What!

    I will try and let you know.

    Thanks

  • Well - EXEC sp_MS_marksystemobject 'myConflictTable' does not work in SQL 2005 I looked for its replacement for SQL 2005 and did not find anything I checked google but still could not find anything.

    FYI - When I check my logs I noticed the following error:

    2008-05-05 17:29:00.453 The merge process is retrying a failed operation made to article 'tb_ApptStudioNotes' - Reason: 'Invalid object name 'dbo.Sync_Log'.'.

    I hope this helps

    If anyone has any ideas I sure would appreciate any direction.

  • Well EXEC sp_MS_marksystemobject 'myConflictTable' does work in SQL 2005. It might not be the solution to your problem, but it does work.

    Try this

    use tempdb

    go

    CREATE TABLE Test1 (c1 int, c2varchar(20))

    GO

    EXEC sp_MS_marksystemobject 'Test1'

    go

    when you look in SSMS you will see the table is listed under system tables, even though the type in sys.objects shows as 'U'

    Also the error you got from your logfile indicates that there are more things wrong, not just a missing conflict table. In that case I would advise to remove replication and re-create publication articles and subscription.

    [font="Verdana"]Markus Bohse[/font]

  • Late night - Basically I found that an individual here put triggers into the production tables (not going thru the right channels or change request forms or anything!!!!!). When I created the new subscription and applied the new snapshot it created these new triggers on that machine but the tables the triggers where referencing where not set to replicate so it would error.

    We desperately need to lock down the servers and assign one individual DBA rights.

    Sorry for all the confusion but thanks for the help.

Viewing 11 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply