SQLServer Fmtonly and ADO
From: Gyuria (Gyuria_at_discussions.microsoft.com)
Date: 11/22/04
- Next message: Haissel: "ADO Installation"
- Previous message: Ronchese: "Stored Procedure - Oracle with ADO"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 22 Nov 2004 05:45:02 -0800
Hello!
ADO uses FMTONLY ON to get metadata from sql server. Recursive stored
procedures will fail with "Maximum stored procedure, function, trigger, or
view nesting level exceeded (limit 32)".
Errors generated when FMTONLY is ON will be ignored by ADO, but the
transaction will be rolled back.
Is it possible to get rid of this metadata checking?
SQL Server 2000 SP3, MDAC 2.8
Thanks,
Attila Gyuri
SQL Server MCP
Here is a simple script to reproduce the problem:
set fmtonly off
GO
drop procedure fmttest
GO
create procedure fmttest
as
if 1 = 0
begin
--this won't be invoked except when FMTONLY is ON
exec fmttest
end
GO
set fmtonly off
--this will be OK
exec fmttest
set fmtonly on
--this will cause "Maximum stored procedure, function, trigger, or view
nesting level exceeded (limit 32)"
exec fmttest
set fmtonly off
- Next message: Haissel: "ADO Installation"
- Previous message: Ronchese: "Stored Procedure - Oracle with ADO"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
