Re: disable/enable all SQL Agent jobs in a non cursor approach

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Aaron [SQL Server MVP] (ten.xoc_at_dnartreb.noraa)
Date: 03/01/05 

Date: Mon, 28 Feb 2005 19:51:32 -0500

I don't think so, because you should be calling a stored procedure for each
job. (As opposed to updating a table somewhere in MSDB, which you shouldn't
do without fully understanding what else the procedure does.)

What is wrong with a cursor approach for this type of one-off, admin task?

On 2/28/05 2:53 PM, in article eGUAu8cHFHA.904@tk2msftngp13.phx.gbl,
"Hassan" <fatima_ja@hotmail.com> wrote:

> Is there a way to disable/enable all SQL Agent jobs using a set based
> operation as opposed to a cursory approach that i can think of right now
>
> If so, can one provide the SQL for it
>
>

Relevant Pages

  • Re: noise words, @@ERROR, and stop and resume indexing
    ... these words at the beginning before sending them to the cursor. ... Looking for a FAQ on Indexing Services/SQL FTS ... >>Create table Noise ... >>> 1) check noise words inside stored procedure ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Error adding command properties for stored procedure call
    ... I see you are using the SQL Native Client for SQL Server ... A server cursor is not allowed on a remote stored procedure or stored ... The stored procedure called is a test one that simply SELECTs the name field ... int InitializeAndConnect; ...
    (microsoft.public.data.oledb)
  • Re: SQL stored procedure not working.
    ... If I do not use that, how can I get the total record count? ... >> I create a stored procedure and a asp page. ... Even if you could specify the cursor type there, ... > interested in the RETURN value, you do not need to use a Command object. ...
    (microsoft.public.inetserver.asp.db)
  • Re: Error adding command properties for stored procedure call
    ... Microsoft OLE DB Provider for SQL Server ... properties to the command the execute call attempts to create a cursor. ... A server cursor is not allowed on a remote stored procedure or stored ...
    (microsoft.public.data.oledb)
  • Re: Null columns and then adding data...
    ... When updating large tables, it is usually a good idea to ... When the row has not been processed by the stored procedure the ... > NULL consume as much memory as a number? ...
    (microsoft.public.sqlserver.server)