Mystery Proccess

I have set up a job on one of my sql servers to inform me
of any processes that run for more than a specified
amount of time. It eails me and the message tells me the
SPID, Host name, login and duration. A proccess keeps on
cropping up that i cannot account for so is causing me
concern. This procces is a bulk insert, the host is one of
out test servers, it is issued using dts designer and the
login used is for the server that the job is running on. I
also return the last TSQL command issued using dbcc
inputbuffer but this is blank. I have looked on the test
server and there are no jobs.
Can any one suggest a way that i can trace the source of
this processI have never realy used SQL profier before, can you
suggest which event i should be tracing
Cheers
>--Original Message--
>Hi,
>Start a trace with SQL Profiler. You can even specify the
minimum duration
>for a statement before it is show in the trace.
>--
>Karl Gram
>"Mat" wrote:
>> I have set up a job on one of my sql servers to inform
me
>> of any processes that run for more than a specified
>> amount of time. It eails me and the message tells me
the
>> SPID, Host name, login and duration. A proccess keeps
on
>> cropping up that i cannot account for so is causing me
>> concern. This procces is a bulk insert, the host is one
of
>> out test servers, it is issued using dts designer and
the
>> login used is for the server that the job is running
on. I
>> also return the last TSQL command issued using dbcc
>> inputbuffer but this is blank. I have looked on the
test
>> server and there are no jobs.
>> Can any one suggest a way that i can trace the source
of
>> this process
>>
>.
>|||Solved the problem..
Maybe you may wish to know the cause...
a dts package was moved from the test server to the
production server. The connectins were changed to reflect
this but the name was left as the original name (test
server)
For what ever reason, sp_who, current activity and SQL
profiler pick up the conection name as the host name for
proccesss created by scheduled dts packages.
>--Original Message--
>Mat,
>From the 4 default events classes only the Stored
Procedures (RPC:Completed)
>and TSQL (SQL:BatchCompleted) events should be enough.
The rest should be
>removed.
>--
>Karl Gram
>"mat" wrote:
>> I have never realy used SQL profier before, can you
>> suggest which event i should be tracing
>> Cheers
>> >--Original Message--
>> >Hi,
>> >
>> >Start a trace with SQL Profiler. You can even specify
the
>> minimum duration
>> >for a statement before it is show in the trace.
>> >
>> >--
>> >Karl Gram
>> >
>> >"Mat" wrote:
>> >
>> >> I have set up a job on one of my sql servers to
inform
>> me
>> >> of any processes that run for more than a specified
>> >> amount of time. It eails me and the message tells me
>> the
>> >> SPID, Host name, login and duration. A proccess
keeps
>> on
>> >> cropping up that i cannot account for so is causing
me
>> >> concern. This procces is a bulk insert, the host is
one
>> of
>> >> out test servers, it is issued using dts designer
and
>> the
>> >> login used is for the server that the job is running
>> on. I
>> >> also return the last TSQL command issued using dbcc
>> >> inputbuffer but this is blank. I have looked on the
>> test
>> >> server and there are no jobs.
>> >>
>> >> Can any one suggest a way that i can trace the
source
>> of
>> >> this process
>> >>
>> >>
>> >.
>> >
>.
>|||Hi,
Start a trace with SQL Profiler. You can even specify the minimum duration
for a statement before it is show in the trace.
--
Karl Gram
"Mat" wrote:
> I have set up a job on one of my sql servers to inform me
> of any processes that run for more than a specified
> amount of time. It eails me and the message tells me the
> SPID, Host name, login and duration. A proccess keeps on
> cropping up that i cannot account for so is causing me
> concern. This procces is a bulk insert, the host is one of
> out test servers, it is issued using dts designer and the
> login used is for the server that the job is running on. I
> also return the last TSQL command issued using dbcc
> inputbuffer but this is blank. I have looked on the test
> server and there are no jobs.
> Can any one suggest a way that i can trace the source of
> this process
>|||Mat,
From the 4 default events classes only the Stored Procedures (RPC:Completed)
and TSQL (SQL:BatchCompleted) events should be enough. The rest should be
removed.
--
Karl Gram
"mat" wrote:
> I have never realy used SQL profier before, can you
> suggest which event i should be tracing
> Cheers
> >--Original Message--
> >Hi,
> >
> >Start a trace with SQL Profiler. You can even specify the
> minimum duration
> >for a statement before it is show in the trace.
> >
> >--
> >Karl Gram
> >
> >"Mat" wrote:
> >
> >> I have set up a job on one of my sql servers to inform
> me
> >> of any processes that run for more than a specified
> >> amount of time. It eails me and the message tells me
> the
> >> SPID, Host name, login and duration. A proccess keeps
> on
> >> cropping up that i cannot account for so is causing me
> >> concern. This procces is a bulk insert, the host is one
> of
> >> out test servers, it is issued using dts designer and
> the
> >> login used is for the server that the job is running
> on. I
> >> also return the last TSQL command issued using dbcc
> >> inputbuffer but this is blank. I have looked on the
> test
> >> server and there are no jobs.
> >>
> >> Can any one suggest a way that i can trace the source
> of
> >> this process
> >>
> >>
> >.
> >
>