Home All Groups Group Topic Archive Search About

.Working with jobs when Agent is stopped.

Author
8 Sep 2006 5:12 PM
David Reabow
Hi All,

How can I work with jobs when agent is stopped? This could be done in SQL
2000 Enterprise manager but does not appear to be available in Management
studio.

I don't want to start the Agent as this will run the jobs.

Thanks,
David

Author
8 Sep 2006 10:26 PM
Erland Sommarskog
David Reabow (da***@invalid.com) writes:
> How can I work with jobs when agent is stopped? This could be done in SQL
> 2000 Enterprise manager but does not appear to be available in Management
> studio.

The best I can propose is that you go to
http://connect.microsoft.com/feedback/default.aspx?SiteID=68
and post this as a suggestion for a future version of Agent.


--
Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Author
9 Sep 2006 2:51 AM
Warren Brunk
David,
What you should do is remove the dtsx packages off of the SQL sever and put
them on the file system.
To edit packages in 2005 you want to use the Business Intelligence studio
not the management studio.

here is an article on the topic

http://www.sqljunkies.com/WebLog/knight_reign/archive/2005/05/05/13523.aspx
http://www.databasejournal.com/features/mssql/article.php/3598546


Show quote
"David Reabow" <da***@invalid.com> wrote in message
news:%23sZesn20GHA.1288@TK2MSFTNGP03.phx.gbl...
> Hi All,
>
> How can I work with jobs when agent is stopped? This could be done in SQL
> 2000 Enterprise manager but does not appear to be available in Management
> studio.
>
> I don't want to start the Agent as this will run the jobs.
>
> Thanks,
> David
>
Author
9 Sep 2006 7:34 AM
Tibor Karaszi
I can create and edit a job, even though Agent service is stopped. I'm on 2005, sp1.

Show quote
"David Reabow" <da***@invalid.com> wrote in message news:%23sZesn20GHA.1288@TK2MSFTNGP03.phx.gbl...
> Hi All,
>
> How can I work with jobs when agent is stopped? This could be done in SQL
> 2000 Enterprise manager but does not appear to be available in Management
> studio.
>
> I don't want to start the Agent as this will run the jobs.
>
> Thanks,
> David
>
>
Author
9 Sep 2006 8:50 AM
Erland Sommarskog
Tibor Karaszi (tibor_please.no.email_kara***@hotmail.nomail.com) writes:
> I can create and edit a job, even though Agent service is stopped. I'm
> on 2005, sp1.

Even if Agent was stopped when you started SSMS? The problem is that if
Agent is stopped, SSMS does not permit you to open the node. You can start
Agent, open the node, and stop Agent and go on editing. But that could
also start job that you don't want to be started.

Of course, it's probably a better ideas to disable the jobs rather than
relying on that no one starts Agent. But it's still a funny GUI behaviour.


--
Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Author
9 Sep 2006 3:33 PM
Tibor Karaszi
> Even if Agent was stopped when you started SSMS?

Yep, Agent was stopped when I start SSMS and I have no problems expanding Agent and work with the
jobs. I just double.checked. I have a feeling that this wasn't the case a while ago, I seem to
recall this demoing Agent in class. I wouldn't be surprised if this is a change in sp1...

> Of course, it's probably a better ideas to disable the jobs rather than
> relying on that no one starts Agent.

Yep, but what if the job currently is enabled and you want to disable it through the GUI? (A stored
procedure call is always an option...)

Anyhow, first step, IMO is the check out what service pack on both the client and the server...

Show quote
"Erland Sommarskog" <esq***@sommarskog.se> wrote in message
news:Xns98396E4888E9EYazorman@127.0.0.1...
> Tibor Karaszi (tibor_please.no.email_kara***@hotmail.nomail.com) writes:
>> I can create and edit a job, even though Agent service is stopped. I'm
>> on 2005, sp1.
>
> Even if Agent was stopped when you started SSMS? The problem is that if
> Agent is stopped, SSMS does not permit you to open the node. You can start
> Agent, open the node, and stop Agent and go on editing. But that could
> also start job that you don't want to be started.
>
> Of course, it's probably a better ideas to disable the jobs rather than
> relying on that no one starts Agent. But it's still a funny GUI behaviour.
>
>
> --
> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Author
9 Sep 2006 9:00 PM
Erland Sommarskog
Tibor Karaszi (tibor_please.no.email_kara***@hotmail.nomail.com) writes:
> Yep, Agent was stopped when I start SSMS and I have no problems
> expanding Agent and work with the jobs. I just double.checked. I have a
> feeling that this wasn't the case a while ago, I seem to recall this
> demoing Agent in class. I wouldn't be surprised if this is a change in
> sp1...

Ah, I found the switch. When I moved the mouse of the nodeless SQL Server
Agent icon, I got a tooltip saying "Agent XP's disabled". Once I had enabled
them, I could expand the node.



--
Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Author
9 Sep 2006 8:59 PM
Erland Sommarskog
David Reabow (da***@invalid.com) writes:
> How can I work with jobs when agent is stopped? This could be done in SQL
> 2000 Enterprise manager but does not appear to be available in Management
> studio.
>
> I don't want to start the Agent as this will run the jobs.

Unfortunately the previous answers were wrong. There is indeed a setting
for this. Run:

  exec sp_configure 'Agent XP', 1
  reconfigure

Under the principle "off by default" if its not neeed, the extended stored
procedures for Agent are disabled by default, and if they are no available,
you can for some reason not expand the node.

--
Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Author
16 Sep 2006 1:30 PM
David Reabow
Thanks Erland,

This was exactly what I needed.


Show quote
"Erland Sommarskog" <esq***@sommarskog.se> wrote in message
news:Xns9839E9D8929C5Yazorman@127.0.0.1...
> David Reabow (da***@invalid.com) writes:
>> How can I work with jobs when agent is stopped? This could be done in SQL
>> 2000 Enterprise manager but does not appear to be available in Management
>> studio.
>>
>> I don't want to start the Agent as this will run the jobs.
>
> Unfortunately the previous answers were wrong. There is indeed a setting
> for this. Run:
>
>  exec sp_configure 'Agent XP', 1
>  reconfigure
>
> Under the principle "off by default" if its not neeed, the extended stored
> procedures for Agent are disabled by default, and if they are no
> available,
> you can for some reason not expand the node.
>
> --
> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

AddThis Social Bookmark Button