all groups > sql server replication > september 2007 >
You're in the

sql server replication

group:

Replication Problem


Replication Problem Mark
9/8/2007 10:29:50 AM
sql server replication:
We have multiple SQL 2005 databases that do merge replication. One database
has now started giving the following error:

· The schema script '5090Mark_2.sch' could not be propagated to the
subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001

Multiple-step OLE DB operation generated errors. Check each OLE DB status
value, if available. No work was done. (Source: MSSQLServer, Error number:
0)
Get help: http://help/0

This started after we added a new table to the database and as a new article
in the publication. That invalidated the snapshot so we ran the snapshot
and since then we have been receiving the error. We have dropped and
recreated the subscription and that didn't fix it. Then we dropped and
recreated the publication and subscription, still not luck.

We have run profiler on the subscriber. It appears that the first statement
in the schema file is being executed correctly, so we know it is accessing
the schema file in the replication folder successfully. Also, it has rights
to drop and create the table, since it will run successfully either of those
as the first statement in the schema file. (The generated schema file
drops, then creates the table.)

It is a push subscription and we have changed it to login to the subscriber
as SA.

We are able to run the schema scripts manually and they work fine.

Thanks for any ideas.
Re: Replication Problem gjdulian NO[at]SPAM hotmail.com
9/8/2007 5:28:28 PM
No, 5090Mark is not the new table. It is an old, old table.
Here is the schema script for 5090Mark that is failing to propagate to
the subscriber.

Note that the first statement, the drop table works the first time it
runs, then complains that the table isn't there to drop the next time
it runs. I have tried commenting out the drop table for subsequent
runs, and then the replication process is able to create the table.
However, it again only executes the first statement (the create in
this case) and fails with the same error message (and doesn't create
the clustered index.)


drop Table [dbo].[5090Mark]
go
SET ANSI_PADDING ON
go

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[5090Mark](
[NumberOfTickets] [int] NOT NULL,
[AveDaysOpen] [int] NOT NULL,
[Month] [char](2) NOT NULL,
[Year] [char](4) NOT NULL,
[Department] [nvarchar](50) NOT NULL,
[50%Mark] [int] NOT NULL,
[90%Mark] [int] NOT NULL,
[DepartmentId] [int] NOT NULL,
[Type] [char](10) NOT NULL,
[5090MarkID] [int] IDENTITY(1,1) NOT FOR REPLICATION NOT NULL,
[rowguid] [uniqueidentifier] ROWGUIDCOL NOT NULL CONSTRAINT
[DF__5090Mark__rowgui__548C6944] DEFAULT (newsequentialid())
)

GO
SET ANSI_NULLS ON

go

SET QUOTED_IDENTIFIER ON

go

CREATE CLUSTERED INDEX [IdnMonthYearType] ON [dbo].[5090Mark]
(
[Month] ASC,
[Year] ASC,
[Type] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB
= OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF,
ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 90)
GO
Re: Replication Problem Hilary Cotter
9/8/2007 7:47:12 PM
Is this the new table? If so, could you post its schema here?

--
Hilary Cotter
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

[quoted text, click to view]

AddThis Social Bookmark Button