Problem with SQL Packager (and Compare)

Brian Donahue

Hi Scott,

I am aware of a bug in SQL Compare that causes numbered stored
procedures to not be handled correctly -- although I'm not 100% sure, I
think it may be a related problem so as soon as we can get that fixed, can
we check to see if that fixes this problem as well?

Thanks for reminding me about the newsgroup for SQL Packager. I will set
it up as soon as the product is 'officially' released.

Regards,

Brian Donahue
Red Gate Technical Support

"Scott Tucholka" <scott.tucholka@aqssys.com> wrote in message
news:kTf%23GkOSEHA.3156@server53...
> Here is the script that is created using SQL Packager and SQL Compare. You
> can see that the script is missing a GO statement right before the CREATE
> PROCEDURE statements on the second and third ([ ; number ]) grouped
stored
> procedures. In SQL Compare, we have a work-around by manually saving the
> script and added the GO statements (if we remember!), but in SQL Packager,
> there is no option to modify the script before the package is created. Let
> me know if you need any additional information. Is there going to be a
> newsgroup just for SQL Packager?
>
> Thanks, Scott
>
>
>
> PRINT N'Creating [dbo].[ABCsp_Test]'
> GO
>
/*==========================================================================
> =======================
> ** NAME: dbo.ABCsp_Test;1
>
**==========================================================================
> =======================
> ** CHANGE LOG:
> ** 06/02/2004 SAT - Created.
>
**==========================================================================
> =====================*/
> CREATE PROCEDURE dbo.ABCsp_Test;1
> @InputLOB CHAR(3) = NULL,
> @Debug INT = NULL
> AS
>
> SET NOCOUNT ON
>
> DECLARE @SQL NVARCHAR(4000)
> DECLARE @CountLOB INT
>
> EXEC dbo.ABCsp_Test;2 @InputLOB, @CountLOB OUTPUT, @Debug
>
> RETURN 0
>
/*==========================================================================
> =======================
> ** NAME: dbo.ABCsp_Test;2
>
**==========================================================================
> =======================
> ** CHANGE LOG:
> ** 06/02/2004 SAT - Created.
>
**==========================================================================
> =====================*/
> CREATE PROCEDURE dbo.ABCsp_Test;2
> @LOB CHAR(3),
> @CountLOB INT OUTPUT,
> @Debug INT = NULL
> AS
>
> SET NOCOUNT ON
>
> DECLARE @SQL NVARCHAR(4000)
> DECLARE @TableName VARCHAR(50)
> DECLARE @Order INT
> DECLARE @Path INT
>
> EXEC dbo.ABCsp_Test;3 @LOB, @TableName, @Order, @Path, @CountLOB, @Debug
>
> RETURN 0
>
/*==========================================================================
> =======================
> ** NAME: dbo.ABCsp_Test;3
>
**==========================================================================
> =======================
> ** CHANGE LOG:
> ** 06/02/2004 SAT - Created.
>
**==========================================================================
> =====================*/
> CREATE PROCEDURE dbo.ABCsp_Test;3
> @LOB CHAR(3),
> @TableName VARCHAR(50),
> @Order INT,
> @Path INT,
> @CountLOB INT OUTPUT,
> @Debug INT = NULL
> AS
>
> PRINT 'HERE'
>
> RETURN 0
>
> GO
@TRANCOUNT&gt;0 ROLLBACK TRANSACTION
> GO
@TRANCOUNT=0 BEGIN INSERT INTO #tmpErrors (Error) SELECT 1 BEGIN
> TRANSACTION END
> GO
> IF EXISTS (SELECT * FROM #tmpErrors) ROLLBACK TRANSACTION
> GO
@TRANCOUNT&gt;0 BEGIN
> PRINT 'The database updated succeeded'
> COMMIT TRANSACTION
> END
> ELSE PRINT 'The database update failed'
> GO
> DROP TABLE #tmpErrors
> GO
>
>

Brian Donahue

Scripts should be created correctly for numbered stored procedures in SQL Compare and Packager now.