No Agent Indication

How can I tell if my SQL Server Agent is running without using the EM? The
network admins have control of the server in such a way as to not let the DBA
start or stop the service on the server. This of course does not light up
the indicator in the EM for the Agent.
Hi
If you run sp_who2 or query sysprocesses, you will see connections from
Agent. They are always there as they poll for jobs.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:D060BCE2-BE0D-493A-81FD-C0E7E18C9E15@.microsoft.com...
> How can I tell if my SQL Server Agent is running without using the EM?
> The
> network admins have control of the server in such a way as to not let the
> DBA
> start or stop the service on the server. This of course does not light up
> the indicator in the EM for the Agent.

No Agent Indication

How can I tell if my SQL Server Agent is running without using the EM? The
network admins have control of the server in such a way as to not let the DBA
start or stop the service on the server. This of course does not light up
the indicator in the EM for the Agent.Hi
If you run sp_who2 or query sysprocesses, you will see connections from
Agent. They are always there as they poll for jobs.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:D060BCE2-BE0D-493A-81FD-C0E7E18C9E15@.microsoft.com...
> How can I tell if my SQL Server Agent is running without using the EM?
> The
> network admins have control of the server in such a way as to not let the
> DBA
> start or stop the service on the server. This of course does not light up
> the indicator in the EM for the Agent.sql

No Agent Indication

How can I tell if my SQL Server Agent is running without using the EM? The
network admins have control of the server in such a way as to not let the DB
A
start or stop the service on the server. This of course does not light up
the indicator in the EM for the Agent.Hi
If you run sp_who2 or query sysprocesses, you will see connections from
Agent. They are always there as they poll for jobs.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:D060BCE2-BE0D-493A-81FD-C0E7E18C9E15@.microsoft.com...
> How can I tell if my SQL Server Agent is running without using the EM?
> The
> network admins have control of the server in such a way as to not let the
> DBA
> start or stop the service on the server. This of course does not light up
> the indicator in the EM for the Agent.

Nixing a Transaction Log

Is it possible to nix a transaction log without backing it
up? My disk is not large enought to back it up and the
snapshot agent continually tells me that there is not
enough space (error 112) although I have 5GB Free on the
array.
Sql 2k
daveWe were just having this same issue - and did this.
With nobody in the DB - so you are sure that no log
activity is going on.
Not sure it's the safest thing to do...
In query analyzer do BACKUP LOG dbname WITH TRUNCATE_ONLY
Them back to Enterprise Manager - right click on DB - all
tasks - SHRINK FILES - click on the FILES cmd button -
choose the log file from the drop down and press OK /
then press CANCEL when you get back to the SHRINK FILES
dialog box.
This dropped the size of the log file to 1024 k
MS KB article give you different (but similar steps):
http://support.microsoft.com/default.aspx?scid=kb;en-
us;272318
>--Original Message--
>Is it possible to nix a transaction log without backing
it
>up? My disk is not large enought to back it up and the
>snapshot agent continually tells me that there is not
>enough space (error 112) although I have 5GB Free on the
>array.
>Sql 2k
>dave
>.
>|||Thanks! That totally helped out in the biggest way!!!
Dave
>--Original Message--
>We were just having this same issue - and did this.
>With nobody in the DB - so you are sure that no log
>activity is going on.
>Not sure it's the safest thing to do...
>In query analyzer do BACKUP LOG dbname WITH TRUNCATE_ONLY
>Them back to Enterprise Manager - right click on DB - all
>tasks - SHRINK FILES - click on the FILES cmd button -
>choose the log file from the drop down and press OK /
>then press CANCEL when you get back to the SHRINK FILES
>dialog box.
>This dropped the size of the log file to 1024 k
>MS KB article give you different (but similar steps):
>http://support.microsoft.com/default.aspx?scid=kb;en-
>us;272318
>>--Original Message--
>>Is it possible to nix a transaction log without backing
>it
>>up? My disk is not large enought to back it up and the
>>snapshot agent continually tells me that there is not
>>enough space (error 112) although I have 5GB Free on the
>>array.
>>Sql 2k
>>dave
>>.
>.
>