April 14, 2009 at 8:54 am
create table #tmpDBCCinputbuffer ([Event Type] nvarchar(512), [Parameters] int, [Event Info] nvarchar(512))
insert into #tmpDBCCinputbuffer exec ('DBCC INPUTBUFFER(213)')
select [Event Info] from #tmpDBCCinputbuffer
April 14, 2009 at 9:59 am
You're running DBCC INPUTBUFFER to see the text of the last statement executed by process ID 213 and putting the results into a temporary table. The SELECT statement shows the text.
Greg
April 14, 2009 at 10:09 am
I am not running it, and I don't see any jobs doing it.
April 14, 2009 at 10:32 am
I see a similar message when I run Activity Monitor from SSMS. The only difference being I see '52' (right now) instead of '213'. I'm fairly sure that this query is being executed by Activity Monitor to get the most recently executed T-SQL for a given spid.
Can anyone confirm this?
April 14, 2009 at 10:49 am
Yes - it is Activity Monitor that is generating that statement. The question really would be why is this showing up in the logs? Generally, things like this would not show up in any of the logs that I am aware of.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
April 14, 2009 at 12:16 pm
Yes, It is in Activity Monitor, sorry. But my question still I am not running, why is it showing?
April 14, 2009 at 12:20 pm
yulichka (4/14/2009)
Yes, It is in Activity Monitor, sorry. But my question still I am not running, why is it showing?
You are running it, it is running as a part of Activity Monitor.
April 14, 2009 at 12:24 pm
Should I stop it, what is the purpose of it? Is this a build in job?
April 14, 2009 at 12:39 pm
What you're seeing there is the code that Management studio is running to get the results displayed by Activity Monitor. That's what management studio runs when you look at a spid's activity.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 14, 2009 at 12:51 pm
Thank you very much, how can I find out why I get this:
in SQL Logs:
Date4/14/2009 9:30:30 AM
LogSQL Server (Current - 4/14/2009 12:00:00 PM)
Sourcelogon
Message
Login failed for user 'cdi_js'.
April 14, 2009 at 1:11 pm
yulichka (4/14/2009)
Thank you very much, how can I find out why I get this:in SQL Logs:
Date4/14/2009 9:30:30 AM
LogSQL Server (Current - 4/14/2009 12:00:00 PM)
Sourcelogon
Message
Login failed for user 'cdi_js'.
The user (cdi_js) failed to login to SQL Server. Seems quite self explanatory to me. Most likely a bad password.
April 14, 2009 at 1:25 pm
this is my user name and this error I get every 5 minutes, so I don't know where it is coming from, how can I know?
April 14, 2009 at 1:25 pm
If you can post the full error, with the error number, severity, line and state, we can tell you why the login failed. From what you've posted, the only thing that can be determined is that the login did indeed fail.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 14, 2009 at 1:27 pm
Job? Windows Service? You're typing the password wrong? Registered servers with wrong credentials?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 14, 2009 at 1:50 pm
I copied the the hall message from Activity Monitor
Viewing 15 posts - 1 through 15 (of 20 total)
You must be logged in to reply to this topic. Login to reply