这似乎是一个相当普遍的问题,我正在摸索它为什么会发生。我正在使用无法直接访问源代码的软件应用程序(我只能使用 .NET Reflector 查看一些)。
存储过程是这样的:
ALTER PROCEDURE [dbo].[CS_GetMessages] (
@CustomerID C_ID, @Level C_Integer, @UsersTimeZoneOffset C_Integer
)
AS
BEGIN
SET NOCOUNT ON
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED
DECLARE @Date Datetime
SELECT @Date = CONVERT(nvarchar(10), getutcdate(), 101)
SELECT
[MessageID]
FROM
[dbo].[Messages]
WHERE
([CustomerID] = @CustomerID OR [CustomerID] IS NULL)
AND Enabled = 1
AND Deleted = 0
AND (EffectiveDate IS NULL OR @Date >= CONVERT(nvarchar(10), DATEADD(minute, @UsersTimeZoneOffset, EffectiveDate), 101))
AND (ExpiryDate IS NULL OR @Date < CONVERT(nvarchar(10), DATEADD(minute, @UsersTimeZoneOffset, ExpiryDate), 101))
AND Publish = 1
AND Level = ISNULL(@Level, Level)
ORDER BY MaintenanceDate DESC
END
现在,根据源代码(不幸的是因为许可我无法粘贴它),它发送了适当数量的参数。SQL Profiler 也正确显示了这一点:
exec CS_GetMessages @CustomerID=N'CT000001',@Level=NULL,@UsersTimezoneOffset=0
但是,它抛出一个错误:
Error: 8144, Severity: 16, State: 2 Procedure or function CS_GetMessages has too many arguments specified.
但是,如果我手动运行该过程,它会正确返回一个值。我使用了以下测试代码:
DECLARE @return_value int
EXEC @return_value = [dbo].[CS_GetMessages]
@CustomerID = 'CT000001',
@Level = NULL,
@UsersTimeZoneOffset = 0
SELECT 'Return Value' = @return_value
GO
请注意,由于数据库为空白(空表),因此没有数据,因此它适当地返回 0。关于可能发生什么的任何想法?
更新:执行数据库调用的源代码:
private SystemMessageManager LoadSystemMessages()
{
int paramValue = Conversions.ToInteger(Utility.DataFromSession("UsersTimezoneOffset", string.Empty));
SystemMessageManager messageManager = new SystemMessageManager();
CriteriaCollection loadCriteria = new CriteriaCollection();
CriteriaCollection criterias2 = loadCriteria;
criterias2.Add("CustomerID", DbType.String, Utility.GetCurrentCustomer().CustomerID, ParameterDirection.Input, "");
criterias2.Add("Level", DbType.Int32, null, ParameterDirection.Input, "");
criterias2.Add("UsersTimezoneOffset", DbType.Int32, paramValue, ParameterDirection.Input, "");
criterias2 = null;
messageManager.Load(loadCriteria);
this.CheckForDeactivation(messageManager);
return messageManager;
}