Compare 10.4.8.87 : bug store proc with multiple modules ?

Compares and synchronizes SQL Server databases, backups and scripts.

Moderators: JonathanWatts, Chris Auckland, David Atkinson, eddie davis, Anu Deshpande, Michelle Taylor, alice.easey, james.billings, chengvoon.tong

Compare 10.4.8.87 : bug store proc with multiple modules ?

Postby Philippe LEGRAND » Thu Oct 10, 2013 9:53 am

This version 10.4.8.87 bug on store procedure with multiple modules.
Without any modification, each refresh show difference (module lacking) between the same procedure (exactly the same procedure in fact)

Regards
Philippe LEGRAND
 
Posts: 3
Joined: Thu Oct 10, 2013 9:45 am
Location: FRANCE - PARIS

Postby Brian Donahue » Mon Oct 14, 2013 2:45 pm

Can you please let us know how to reproduce this behaviour?
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am

Postby Philippe LEGRAND » Mon Oct 14, 2013 3:35 pm

Of course :

Please, create 2 databases nammed DB_1 and DB_2

Create this store procédure on DB_1 and DB_2

GO
/****** Object: StoredProcedure [dbo].[Z_RG_CS_Test] Script Date: 10/14/2013 16:22:15 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO


CREATE procedure [dbo].[Z_RG_CS_Test] as
begin
print 'M1'
end



GO
/****** Object: NumberedStoredProcedure [dbo].[Z_RG_CS_Test];2 Script Date: 10/14/2013 16:22:16 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO


CREATE procedure [dbo].[Z_RG_CS_Test];2 as
begin
print 'M2'
end


GO
/****** Object: NumberedStoredProcedure [dbo].[Z_RG_CS_Test];3 Script Date: 10/14/2013 16:22:16 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO


CREATE procedure [dbo].[Z_RG_CS_Test];3 as
begin
print 'M3'
end


Then, compare structure on DB_1 and DB_2.
Refresh the comparaison more and more, without any change.

On my computer, after 4 or 5 refresh, a difference appear.

Regards,
Philippe LEGRAND
 
Posts: 3
Joined: Thu Oct 10, 2013 9:45 am
Location: FRANCE - PARIS

Postby Brian Donahue » Tue Oct 15, 2013 8:24 am

The issue is probably that SQL Compare doesn't support numbered stored procedures, since they were deprecated after SQL 2000.
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am

Postby kevinsalot » Wed Jul 30, 2014 7:59 pm

I too am having this issue.

This was working for me in SQL Compare 8. We purchased SQL Compare 10 in order to get support for SQL Server 2012. Since the upgrade we have had unreliable comparisons for our SPs.

Has RedGate acknowledged this as a defect that will be corrected in an update? Does anyone know a workaround for this?

Thanks!
- Kevin
kevinsalot
 
Posts: 3
Joined: Wed Jul 30, 2014 7:53 pm

Postby Brian Donahue » Mon Aug 04, 2014 10:47 am

Since we have no reproduction of this issue, I cannot offer any advice. There is no huge, sweeping problem in the comparison of stored procedures - if there was believe me this forum would be struggling to keep up with the traffic.
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am

Postby Brian Donahue » Mon Aug 04, 2014 10:59 am

Kevin, I noticed you already opened a call with support regarding numbered stored procedures. If this is the case then that's a firm no - numbered stored procedures were deprecated in SQL Server 2000 and they won't ever be back-ported in SQL Compare as Red Gate have deprecated support for SQL Server 2000*.

I am somewhat confused about "it stopped working in SQL Server 2012" though - I expect that's a coincidence?

* Specifically SQL 2000 will continue to work but current/future versions are no longer tested and any fixes necessary to support SQL 2000 will not be done**.

** Unless someone blackmails our CEO or it's otherwise necessary to save mankind from complete and utter destruction.
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am

Postby kevinsalot » Mon Aug 04, 2014 1:28 pm

I think you've misunderstood. The issue isn't SQL 2012 related.

Our organization wants to upgrade to a new version of SQL Compare because we want to use SQL 2012 (instead of 2008R2).

On version 8, SQL Compare works with numbered SPs. After the upgrade, it does not. As you can see in the ticket, this is acknowledged as a defect in the product. it was broken sometime in version 8.2:

"Unfortunately this is a known bug with versions 8.2 and higher. The reference is SC-4638."


Support had me try the beta for SQL Compare 11, and at least in my testing the defect was fixed.
- Kevin
kevinsalot
 
Posts: 3
Joined: Wed Jul 30, 2014 7:53 pm

Postby Brian Donahue » Mon Aug 04, 2014 2:59 pm

I had a look at the bug report, and it is still open. It hasn't been fixed *intentionally*. You are awaiting an answer from Evan about whether or not this has been fixed. I'd keep in correspondence with him, as he is looking into this for you.
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am


Return to SQL Compare 10

Who is online

Users browsing this forum: No registered users and 0 guests