【问题标题】:GO commands in the middle of an IF statementIF 语句中间的 GO 命令
【发布时间】:2013-03-19 01:33:20
【问题描述】:

我一直在寻找关于仅当当前数据库上不存在表时才创建表的 SO(以便能够在可能或可能没有它们的不同数据库中创建它)并发现这两个有用的主题

所以我做了这个查询

IF (NOT EXISTS (SELECT * 
             FROM INFORMATION_SCHEMA.TABLES 
             WHERE TABLE_NAME = 'EMAILCONTAS'))
BEGIN
SET ANSI_NULLS ON
GO

SET QUOTED_IDENTIFIER ON
GO

SET ANSI_PADDING ON
GO

CREATE TABLE [dbo].[EMAILCONTAS](
    [NRSEQEMAILCONTAS] [numeric](8, 0) NOT NULL,
    [CDEMAILCONTAS] [varchar](40) NULL,
    [MSGEMAILCONTAS] [varchar](4000) NOT NULL,
    [CCOEMAIL] [varchar](100) NULL,
    [NRSEQOPERADORA] [numeric](8, 0) NOT NULL,
 CONSTRAINT [PK_EMAILCONTAS] PRIMARY KEY CLUSTERED 
(
    [NRSEQEMAILCONTAS] ASC
)WITH (PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON) ON [PRIMARY]
) ON [PRIMARY]

GO

SET ANSI_PADDING OFF
GO

ALTER TABLE [dbo].[EMAILCONTAS]  WITH CHECK ADD FOREIGN KEY([NRSEQOPERADORA])
REFERENCES [dbo].[OPERADORA] ([NRSEQOPERADORA])
GO

ALTER TABLE [dbo].[EMAILCONTAS]  WITH CHECK ADD  CONSTRAINT [FK_EMAILCONTAS_OPERADORA] FOREIGN KEY([NRSEQOPERADORA])
REFERENCES [dbo].[OPERADORA] ([NRSEQOPERADORA])
GO

ALTER TABLE [dbo].[EMAILCONTAS] CHECK CONSTRAINT [FK_EMAILCONTAS_OPERADORA]
GO
END

但是当我执行它时,我在错误列表中得到了这个。

Msg 102, Level 15, State 1, Line 5
Incorrect syntax near 'ON'.

但它无论如何都会创建我的表(我在上面的代码之后放了一个“Select * from PERSON;”,以检查错误是否会阻止下一个脚本编译。错误阻止了它。显示这个错误:

Msg 156, Level 15, State 1, Line 3
Incorrect syntax near the keyword 'Select'.

有办法避免吗?)。当我执行这个查询并且表已经存在时,我得到了以下错误。

Msg 102, Level 15, State 1, Line 5
Incorrect syntax near 'ON'.
Msg 2714, Level 16, State 6, Line 2
There is already an object named 'EMAILCONTAS' in the database.
Msg 2714, Level 16, State 5, Line 2
There is already an object named 'FK_EMAILCONTAS_OPERADORA' in the database.
Msg 1750, Level 16, State 0, Line 2
Could not create constraint. See previous errors.

如何在不出现这些错误的情况下完成此操作?有没有办法可以毫无问题地创建多个这样的代码?我做错了什么?

【问题讨论】:

    标签: sql-server tsql


    【解决方案1】:

    GO 类似于脚本的结尾;您可以从 BEGIN-END 语句中删除 GOs。

    如果您绝对需要在代码中包含GO,您可以将查询分解为:

    IF (criteria)
    BEGIN
        ...
    END
    
    GO
    
    IF (newcriteria)
    BEGIN
        ...
    END
    

    【讨论】:

    • 非常感谢,这行得通。我认为你的答案是正确的,因为GO 解释
    【解决方案2】:

    在我工作的地方,所有脚本都必须进行此项检查。在此示例中,我在检查之前拥有所有设置:

    SET ANSI_NULLS ON
    GO
    
    SET QUOTED_IDENTIFIER ON
    GO
    
    SET ANSI_PADDING ON
    GO
    
    IF NOT EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[DimTime]') AND type in (N'U'))
        BEGIN
            Create Table [dbo].[DimTime]
            (
                TimeID int PRIMARY KEY IDENTITY(1,1),
                Month int,
                Year int,
                Day int,
            )
        END
    

    【讨论】:

      猜你喜欢
      • 2021-06-21
      • 2016-05-27
      • 2021-02-12
      • 2018-04-09
      • 2012-07-09
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 2023-03-06
      相关资源
      最近更新 更多