我发现了一些存储过程,它们从缺少的表中选择数据或尝试ORDER BY不存在的列.

包装sql以在SET PARSEONLY ON中创建过程并在try / catch中捕获错误仅捕获ORDER BY中的无效列.在从缺失表中选择数据的过程中找不到错误.然而,SSMS 2008的智能感知会找到问题,但我仍然可以继续并成功运行ALTER脚本,而不会抱怨它.

那么,为什么我甚至可以创建一个在运行时失败的程序呢？那里有什么工具比我尝试过的更好吗？

我找到的第一个工具不是很有用：DbValidator from CodeProject,但它找到的问题比我在sqlServerCentral上找到的脚本少,后者发现了无效的列引用.

-------------------------------------------------------------------------
-- Check Syntax of Database Objects
-- Copyrighted work.  Free to use as a tool to check your own code or in 
--  any software not sold. All other uses require written permission.
-------------------------------------------------------------------------
-- Turn on ParSEOnly so that we don't actually execute anything.
SET PARSEONLY ON 
GO
 
-- Create a table to iterate through
declare @ObjectList table (ID_NUM int NOT NULL IDENTITY (1,1),OBJ_NAME varchar(255),OBJ_TYPE char(2))
 
-- Get a list of most of the scriptable objects in the DB.
insert into @ObjectList (OBJ_NAME,OBJ_TYPE)
SELECT   name,type
FROM     sysobjects WHERE type in ('P','FN','IF','TF','TR','V')
order by type,name
 
-- Var to hold the sql that we will be Syntax checking
declare @sqltocheckSyntaxFor varchar(max)
-- Var to hold the name of the object we are currently checking
declare @ObjectName varchar(255)
-- Var to hold the type of the object we are currently checking
declare @ObjectType char(2)
-- Var to indicate our current location in iterating through the list of objects
declare @IDNum int
-- Var to indicate the max number of objects we need to iterate through
declare @MaxIDNum int
-- Set the inital value and max value
select  @IDNum = Min(ID_NUM),@MaxIDNum = Max(ID_NUM)
from    @ObjectList
 
-- Begin iteration
while @IDNum <= @MaxIDNum
begin
  -- Load per iteration values here
  select  @ObjectName = OBJ_NAME,@ObjectType = OBJ_TYPE
  from    @ObjectList
  where   ID_NUM = @IDNum 
 
  -- Get the text of the db Object (ie create script for the sproc)
  SELECT @sqltocheckSyntaxFor = OBJECT_DEFINITION(OBJECT_ID(@ObjectName,@ObjectType))
 
  begin try
    -- Run the create script (remember that PARSEONLY has been turned on)
    EXECUTE(@sqltocheckSyntaxFor)
  end try
  begin catch
    -- See if the object name is the same in the script and the catalog (kind of a special error)
    if (ERROR_PROCEDURE() <> @ObjectName)
    begin
      print 'Error in ' + @ObjectName
      print '  The Name in the script is ' + ERROR_PROCEDURE()+ '. (They don''t match)'
    end
    -- If the error is just that this already exists then  we don't want to report that.
    else if (ERROR_MESSAGE() <> 'There is already an object named ''' + ERROR_PROCEDURE() + ''' in the database.')
    begin
      -- Report the error that we got.
      print 'Error in ' + ERROR_PROCEDURE()
      print '  ERROR TEXT: ' + ERROR_MESSAGE() 
    end
  end catch
 
  -- Setup to iterate to the next item in the table
  select  @IDNum = case
            when Min(ID_NUM) is NULL then @IDNum + 1
            else Min(ID_NUM)
          end  
  from    @ObjectList
  where   ID_NUM > @IDNum
 
end
-- Turn the ParSEOnly back off.
SET PARSEONLY OFF 
GO