What are the challenges you face when working across database platforms? Take the survey
Options

Comparing SET options

gunneykgunneyk Posts: 14
I am comparing two sets of script files and some of the objects such as UDF's similar to this example below: The compare with the SDK runs fine and detects any differences in the UDF itself but not the SET ANSI_NULL's or Quoted ID etc. I have tried various options even no options and it still won't detect the differences in the SET settings. I know this works if I compare two DB's (Not scripts) using SQL Compare. Why doesn't it detect it in this case? Is there a way to do this?


SET ANSI_NULLS OFF
GO
SET QUOTED_IDENTIFIER ON
GO
IF EXISTS (...
DROP FUNCTION [ConvertToBytes]
GO

CREATE FUNCTION [dbo].[ConvertToBytes](@input varchar(50)) RETURNS BIGINT AS
BEGIN
blah blah blah
END
GO

Thanks

Andy

Comments

  • Options
    Thanks for your post.

    The issue seems to be that the SET settings are not displayed if they're set to ON. They sync will still work correctly as ON will be assumed if not set to OFF.

    However, this can look misleading, and can cause the SQL Differences in reports to line up strangely.

    For this reason I have logged it as a bug (SC-4495) with SQL Compare 8.0.
    Chris
Sign In or Register to comment.