June 29, 2009 at 3:14 pm
I have setup trasaction replication with a remote distribution.
SQL Server 2000 (The publisher)
SQL Server 2008 (The remote ditributor)
SQL Server 2008 (The subscriber)
Non-trushted environment.
The setup was completed with no errors initial snapshot. The developers dropped my database replications due to some application update.
I resetup my database replication by testing out the Northwind database in SQL 2000 machine.
When I run the initial snapshot, I received errors of:
Command attempted:
create procedure sp_MSins_Categories
@c1 int,
@c2 nvarchar(15),
@c3 ntext,
@c4 image
as
begin
insert into [Categories](
[CategoryID],
[CategoryName],
[Description],
[Picture]
) values (
@c1,
@c2,
@c3,
@c4 )
end
(Transaction sequence number: 0x0000001D00000152001800000001, Command ID: 6)
Error messages:
The transaction ended in the trigger. The batch has been aborted. (Source: MSSQLServer, Error number: 3609)
Get help: http://help/3609
The transaction ended in the trigger. The batch has been aborted. (Source: MSSQLServer, Error number: 3609)
Get help: http://help/3609
I am not familiar with those errors. Can anyone help and advice?
June 29, 2009 at 3:30 pm
When they updated the DB , did they add any trace flags? Seems like they have DBCC TRACEON(3607), DBCC TRACEON(3608) and DBCC TRACEON(3609). This can cause SQL server to misbehave.
I am not sure about this solution, but please check.
-Roy
June 29, 2009 at 5:21 pm
Hi Roy,
Thanks for your kind information. How to turn it off in SQL 2000 Enterprise Manager?
June 30, 2009 at 7:23 am
As per BOL... The following example disables trace flags 3205 and 260 globally.
DBCC TRACEOFF (3205, 260, -1);
GO
Where -1 means global.
-Roy
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply