Options
Problem with synchronize group procedures with the same name
kp
Posts: 2
Hello,
I found the problem with synchronize databases (SQL Server 2000) using SQL Compare 7.0. When I try synchronize one group procedures with two stored procedure:
create procedure "sp_MSdel_dbotest" @pkc1 varchar(19)
as
delete "dbo"."test"
where "client" = @pkc1
@rowcount = 0
@microsoftversion>0x07320000
exec sp_MSreplraiserror 20598
GO
create procedure "sp_MSdel_dbotest";2 @pkc1 varchar(19)
as
delete "dbo"."test"
where "client" = @pkc1
GO
i get following error message:
"There was a problem executing the synchronization script. All changes have been rolled back so that the database is in its orginal state." .....
Best regards
KP
I found the problem with synchronize databases (SQL Server 2000) using SQL Compare 7.0. When I try synchronize one group procedures with two stored procedure:
create procedure "sp_MSdel_dbotest" @pkc1 varchar(19)
as
delete "dbo"."test"
where "client" = @pkc1
@rowcount = 0
@microsoftversion>0x07320000
exec sp_MSreplraiserror 20598
GO
create procedure "sp_MSdel_dbotest";2 @pkc1 varchar(19)
as
delete "dbo"."test"
where "client" = @pkc1
GO
i get following error message:
"There was a problem executing the synchronization script. All changes have been rolled back so that the database is in its orginal state." .....
Best regards
KP
Comments
The way that SQL Compare runs the script is to cut it up into batches itself and then send individual batches, but numbered stored procedures are treated as one entity by SQL Compare and therefore you end up with a 'GO' in the middle of a batch, which is invalid.
As numbered stored procedures are no longer supported in new versions of SQL Server and a workaround exists, we probably won't fix this any time soon, I'm afraid.
Redgate Software