Rogue Insert statement running

SqlServr.exe is eating up CPU time and choking the server.  I ran a SLQ trace through Profiler and found a bulk insert statement that keeps running over and over.  There is no replication to the affected table and no scripts that I have written to do this insert.  The only update to the table happens via a SQL job overnight and it is showing idle.  According to the trace output, the application name is Microsoft SQL Server and the user name and login account is a  local admin account.  How do I shut the insert down?

If there is another way to better identify the problem, let me know.

Thanks,

McLeanIS
McLeanISAsked:
Who is Participating?
 
McLeanISConnect With a Mentor Author Commented:
Sorry for late handling of this issue.  I have been out sick alot.  One of our network techs shut down SQL Server for a while and resovled this issue as well as some others that came up after this post.  All has been running well since then.

McLeanIS
0
 
QlemoDeveloperCommented:
I would go and check the Scheduled Tasks for something running at that time.
In SQL Trace output you should also monitor the connection info (especially the machine).
Though, you should see some other application in the trace ... Even it is a SQL Server Agent job, you should see that.
0
 
Aaron ShiloChief Database ArchitectCommented:
hi

it probably a job running.

can you post the data from profiler ?
0
 
McLeanISAuthor Commented:
The issue resolved itself.
0
All Courses

From novice to tech pro — start learning today.