SQL 服务器 - 当运行 SQL 脚本通过 SQLCMD 和通过 MSSQL 时，相同的代码会产生不同的结果

Question

我有一个奇怪的问题，即相同的脚本有不同的结果。下面是我的代码：

--Create table ExtractForCustomerLoyalty--------------------------------------------------------------------
--This contains the customer extract records and is used by CustomerLoyaltyExporter batch job.
--Version 1 - 8/14/2018
IF NOT EXISTS (SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = 'ExtractForCustomerLoyalty')
BEGIN
    Print 'Creating [dbo].[ExtractForCustomerLoyalty] table...'

    CREATE TABLE [dbo].[ExtractForCustomerLoyalty](
        [rowID] [int] NOT NULL,
        [sequenceCount] [int] NOT NULL,
        [extractTime] [datetime] NOT NULL,
        [extractData] [varchar](8000) NOT NULL,
        [exported] [varchar](1) NOT NULL DEFAULT ('N')
    ) ON [PRIMARY]
END
GO


--Create trigger customer_extract---------------------------------------------------------------------------
--This trigger is used to create customer extract records
--Version 1 - 8/14/2018
IF EXISTS (SELECT * FROM sys.objects WHERE [object_id] = OBJECT_ID(N'['+OBJECT_SCHEMA_NAME(object_id)+N'].[customer_extract]') AND [type] = 'TR')
BEGIN
    Print 'Dropping [dbo].[customer_extract] Trigger'
    DROP TRIGGER [dbo].[customer_extract];
END;
GO

CREATE TRIGGER [dbo].[customer_extract] on [CCSV4].[dbo].[ExtractForStandardCustomer]
AFTER INSERT
AS
    SET ANSI_NULLS ON
    SET ANSI_PADDING ON
    SET ANSI_WARNINGS ON
    SET ARITHABORT ON
    SET CONCAT_NULL_YIELDS_NULL ON
    SET QUOTED_IDENTIFIER ON

    --Just in case we need to deactivate trigger
    DECLARE @Cinfo VARBINARY(128)  
    SELECT @Cinfo = Context_Info()  
    IF @Cinfo = 0x55555  
        RETURN

    --Declaration
    DECLARE @rowID int
    DECLARE @dataXML XML
    DECLARE @data VARCHAR(MAX) = ''

    -- Get the complete extractData xml from ExtractForStandardCustomer table
    SET @rowID = (select rowID from inserted)
    SELECT @data = @data + extractData FROM ExtractForStandardCustomer where rowID = @rowID order by sequenceCount
    SET @dataXML = TRY_CAST(@data as XML)

    IF @dataXML IS NULL
        RETURN

    -- Check the CustomerUpdate type (Create / Update / Delete)
    IF (@dataXML.exist('(/CustomerExtract/Change)') = 1)
        -- Customer Update
        INSERT INTO [dbo].[ExtractForCustomerLoyalty](rowID, sequenceCount, extractTime, extractData)
        SELECT i.rowID, i.sequenceCount, i.extractTime,
            '' + '|' +
            '' + '|' +
            ISNULL(@dataXML.value('(//After/Customer/Loyalty/LoyaltyID)[1]', 'VARCHAR(8000)'),'') + '|' +
            ISNULL(@dataXML.value('(//After/Customer/Loyalty/JoinLocation)[1]', 'VARCHAR(8000)'),'') + '|' +
            ISNULL(@dataXML.value('(//After/Customer/Loyalty/JoinDate)[1]', 'VARCHAR(8000)'),'') + '|' +
            ISNULL(@dataXML.value('(//After/Customer/Loyalty/FirstPurchaseDate)[1]', 'VARCHAR(8000)'),'') + '|' +
            ISNULL(@dataXML.value('(//After/Customer/Loyalty/FirstPurchaseLocation)[1]', 'VARCHAR(8000)'),'') + '|'
            ---More here
        FROM inserted i
    ELSE
        BEGIN
        --Customer Create / Delete
        INSERT INTO [dbo].[ExtractForCustomerLoyalty](rowID, sequenceCount, extractTime, extractData)
        SELECT top 1 i.rowID, i.sequenceCount, i.extractTime,
            '' + '|' +  --CUSTOMER_ID (NULL for now)
            '' + '|' +  --HOUSEHOLD_ID (NULL for now)
            ISNULL(@dataXML.value('(//Customer/Loyalty/LoyaltyID)[1]', 'VARCHAR(8000)'),'') + '|' +
            ISNULL(@dataXML.value('(//Customer/Loyalty/JoinLocation)[1]', 'VARCHAR(8000)'),'') + '|' +
            ISNULL(@dataXML.value('(//Customer/Loyalty/JoinDate)[1]', 'VARCHAR(8000)'),'') + '|' +
            ISNULL(@dataXML.value('(//Customer/Loyalty/FirstPurchaseDate)[1]', 'VARCHAR(8000)'),'') + '|' +
            ISNULL(@dataXML.value('(//Customer/Loyalty/FirstPurchaseLocation)[1]', 'VARCHAR(8000)'),'') + '|' +
            ISNULL(@dataXML.value('(//Customer/Name/First)[1]', 'VARCHAR(8000)'),'') + '|'
            --More here

        FROM inserted i
        END
GO

当我运行使用 SQL Server Management Studio 2014 UI 时，当我在 ExtractForStandardCustomer table 上插入内容时，触发器正常执行。它用所需的记录填充 ExtractForCustomerLoyalty table...

但是，当我尝试运行通过 cmd 使用相同的脚本时：

sqlcmd -E -d testDB -i TESTSCRIPT.sql > TESTSCRIPT.log

它抛出这个错误：

 com.microsoft.sqlserver.jdbc.SQLServerException: CONDITIONAL failed because the following SET options have incorrect settings: 'QUOTED_IDENTIFIER'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations.

Answer 1

不同的工具和库有不同的默认设置。

来自SET QUOTED_IDENTIFIER：

The SQL Server Native Client ODBC driver and SQL Server Native Client OLE DB Provider for SQL Server automatically set QUOTED_IDENTIFIER to ON when connecting. This can be configured in ODBC data sources, in ODBC connection attributes, or OLE DB connection properties. The default for SET QUOTED_IDENTIFIER is OFF for connections from DB-Library applications.

如果您不喜欢接受默认值，或者（如此处）您希望能够运行脚本可预测地不管使用什么默认值，请明确设置您需要的选项。

另外，请特别注意 QUOTED_IDENTIFIER 和 ANSI_NULLS 在定义模块（例如触发器、存储过程等）时被捕获。您要确保这些设置应用于您的连接，而不是任何特定的模块定义。

在执行 SQLCMD 时始终指定 -I 命令行参数是一个很好的（也许是最好的）做法，这样 QUOTED_IDENTIFIER 默认处于启用状态。为了向后兼容，该设置在 SQLCMD 中默认关闭。

SQL 服务器 - 当运行 SQL 脚本通过 SQLCMD 和通过 MSSQL 时，相同的代码会产生不同的结果

SQL SERVER - Same code different result when running SQL script via SQLCMD and via MSSQL

sql-server

xpath

quoted-identifier

SQL 服务器 - 当 运行 SQL 脚本通过 SQLCMD 和通过 MSSQL 时，相同的代码会产生不同的结果

SQL SERVER - Same code different result when running SQL script via SQLCMD and via MSSQL

sql-server

xpath

quoted-identifier

SQL 服务器 - 当运行 SQL 脚本通过 SQLCMD 和通过 MSSQL 时，相同的代码会产生不同的结果