SQL Compare 8.2.1.70 fails to parse the following CREATE PROCEDURE statement when contained within a script file (a 'High' severity error is listed in the 'Error Parsing Scripts' window):
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO
CREATE PROCEDURE dbo.TestProc
AS
IF NOT EXISTS
(SELECT name
FROM master.sys.server_principals
WHERE name = 'TestHarness')
BEGIN
CREATE LOGIN [TestHarness]
WITH PASSWORD = 0x0100781BD9C1BAD1800BDD17F5E519D0FDCE3859ED8744CCC60F HASHED,
SID = 0xB07B7164C1A45949AEBBA103DB785D7A
END
GO
It seems that the SQL Compare parser can't handle hashed passwords as parsing succeeds when changing the CREATE LOGIN statement to the
following:
CREATE LOGIN [TestHarness]
WITH PASSWORD = 'TestHarness',
SID = 0xB07B7164C1A45949AEBBA103DB785D7A
Is this something that could be fixed in a future release? I'm using SQL Server 2005 Developer SP3 CU1 (9.0.4207).
Thanks
Chris
It seems that the SQL Compare parser can't handle hashed passwords as parsing succeeds when changing the CREATE LOGIN statement to the
following:
Is this something that could be fixed in a future release? I'm using SQL Server 2005 Developer SP3 CU1 (9.0.4207).
Thanks
Chris