Nesting level exceeded (limit 32)

Question

Post reply

Nesting level exceeded (limit 32)

Anchelin

SSCrazy

Points: 2418
More actions
March 12, 2008 at 5:50 am

#379174

Hi All
I'm running the following script to get all failed logins from a server, via a linked server:
SELECT * FROM OPENQUERY (myserver,'master.dbo.usp__Failed_LogIns')
The script is as follows (called usp__Failed_LogIns):
truncate table Errors
INSERT INTO Errorstmp
(textRow, continuationRow)
EXEC dbo.xp_readerrorlog
insert into Errors
SELECT @@servername as ServerName,textRow as ErrorMsg,
(convert(varchar(8),getdate(),112)) as RunDate
FROM Errorstmp
WHERE CHARINDEX('logon ', textRow) > 0 and
textRow like '%login f%'
ORDER by rowID
--insert into Errors
--select * from Errors_tmp
truncate table Errorstmp
select * from Errors
Can anyone please shed some light on this? I did read other blogs, but can someone give me a clear undertsanding of whats happening? Thanks in advance.
A

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Anchelin SSCrazy Points: 2418 More actions · Answer 1

Hi

Seems like I called the same procedure in the usp__Failed_Logins proc

😉

I do however get the following error when I execute the linked server script:

Could not process object 'master.dbo.usp__Failed_LogIns'. The OLE DB provider 'SQLOLEDB' indicates that the object has no columns.

OLE DB error trace [Non-interface error: OLE DB provider unable to process the object:ProviderName='SQLOLEDB', Query=master.dbo.usp__Failed_LogIns'].

Any ideas?

Thanks

A

Steve Jones - SSC Editor SSC Guru Points: 738632 More actions · Answer 2

You have issued a "SELECT", which expects results to be returned back. however your script does an insert and doesn't return any results.

Anchelin SSCrazy Points: 2418 More actions · Answer 3

Hi there

Thanks for the reply.But can you be a bit clearer. Can you perhaps guide me into the right direction?

Thanks

A

Matt Miller (4) SSC Guru Points: 124210 More actions · Answer 4

Nesting level tells me you likely have a trigger that's firing over and over and over again. If a trigger is set up in such a way as to make itself fire, (like doing an insert in an ON INSERT query on a database with Recursive Triggers turned on) - you will get the "Nested level exceeded" error.

----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?