Scheduling enable tick box not working

Hi all,
I have a simple question, as follows.
I have set up a couple of jobs which I have scheduled to
run around the same time each night.
One of the jobs works fine, but the other does not run, I
have lloked into the problem and found that the tick box
which enables scheduling, unchecks it's self each night.
Is this possible and how can I stop it.
Both jobs were set-up in exactly the same manner.
Cheers.Hi,
Is that job scheduled to run "One Time".
Check that by looking in to the "schedule" property of that job. If it is
the case make the job "Recurring"
Thanks
Hari
MCDBA
"Gazzer J" <anonymous@.discussions.microsoft.com> wrote in message
news:f99901c43e39$fc06ab50$a001280a@.phx.gbl...
> Hi all,
> I have a simple question, as follows.
> I have set up a couple of jobs which I have scheduled to
> run around the same time each night.
> One of the jobs works fine, but the other does not run, I
> have lloked into the problem and found that the tick box
> which enables scheduling, unchecks it's self each night.
> Is this possible and how can I stop it.
> Both jobs were set-up in exactly the same manner.
> Cheers.|||There is a bug that can cause something like this. Do you
have any warnings in the SQL Agent log along the lines of
Possible date calculation spin for Schedule nn
If you have these warnings make sure you are on the latest
service pack. You may also want to try adding a minute or
two to the scheduled time as this can often correct the
problems with the data calculation "confusion" that SQL
Agent sometimes experiences.
-Sue
On Thu, 20 May 2004 00:13:43 -0700, "Gazzer J"
<anonymous@.discussions.microsoft.com> wrote:

>Hi all,
>I have a simple question, as follows.
>I have set up a couple of jobs which I have scheduled to
>run around the same time each night.
>One of the jobs works fine, but the other does not run, I
>have lloked into the problem and found that the tick box
>which enables scheduling, unchecks it's self each night.
>Is this possible and how can I stop it.
>Both jobs were set-up in exactly the same manner.
>Cheers.

Scheduling enable tick box not working

Hi all,
I have a simple question, as follows.
I have set up a couple of jobs which I have scheduled to
run around the same time each night.
One of the jobs works fine, but the other does not run, I
have lloked into the problem and found that the tick box
which enables scheduling, unchecks it's self each night.
Is this possible and how can I stop it.
Both jobs were set-up in exactly the same manner.
Cheers.Hi,
Is that job scheduled to run "One Time".
Check that by looking in to the "schedule" property of that job. If it is
the case make the job "Recurring"
Thanks
Hari
MCDBA
"Gazzer J" <anonymous@.discussions.microsoft.com> wrote in message
news:f99901c43e39$fc06ab50$a001280a@.phx.gbl...
> Hi all,
> I have a simple question, as follows.
> I have set up a couple of jobs which I have scheduled to
> run around the same time each night.
> One of the jobs works fine, but the other does not run, I
> have lloked into the problem and found that the tick box
> which enables scheduling, unchecks it's self each night.
> Is this possible and how can I stop it.
> Both jobs were set-up in exactly the same manner.
> Cheers.|||There is a bug that can cause something like this. Do you
have any warnings in the SQL Agent log along the lines of
Possible date calculation spin for Schedule nn
If you have these warnings make sure you are on the latest
service pack. You may also want to try adding a minute or
two to the scheduled time as this can often correct the
problems with the data calculation "confusion" that SQL
Agent sometimes experiences.
-Sue
On Thu, 20 May 2004 00:13:43 -0700, "Gazzer J"
<anonymous@.discussions.microsoft.com> wrote:
>Hi all,
>I have a simple question, as follows.
>I have set up a couple of jobs which I have scheduled to
>run around the same time each night.
>One of the jobs works fine, but the other does not run, I
>have lloked into the problem and found that the tick box
>which enables scheduling, unchecks it's self each night.
>Is this possible and how can I stop it.
>Both jobs were set-up in exactly the same manner.
>Cheers.

Scheduling enable tick box not working

Hi all,
I have a simple question, as follows.
I have set up a couple of jobs which I have scheduled to
run around the same time each night.
One of the jobs works fine, but the other does not run, I
have lloked into the problem and found that the tick box
which enables scheduling, unchecks it's self each night.
Is this possible and how can I stop it.
Both jobs were set-up in exactly the same manner.
Cheers.
Hi,
Is that job scheduled to run "One Time".
Check that by looking in to the "schedule" property of that job. If it is
the case make the job "Recurring"
Thanks
Hari
MCDBA
"Gazzer J" <anonymous@.discussions.microsoft.com> wrote in message
news:f99901c43e39$fc06ab50$a001280a@.phx.gbl...
> Hi all,
> I have a simple question, as follows.
> I have set up a couple of jobs which I have scheduled to
> run around the same time each night.
> One of the jobs works fine, but the other does not run, I
> have lloked into the problem and found that the tick box
> which enables scheduling, unchecks it's self each night.
> Is this possible and how can I stop it.
> Both jobs were set-up in exactly the same manner.
> Cheers.
|||There is a bug that can cause something like this. Do you
have any warnings in the SQL Agent log along the lines of
Possible date calculation spin for Schedule nn
If you have these warnings make sure you are on the latest
service pack. You may also want to try adding a minute or
two to the scheduled time as this can often correct the
problems with the data calculation "confusion" that SQL
Agent sometimes experiences.
-Sue
On Thu, 20 May 2004 00:13:43 -0700, "Gazzer J"
<anonymous@.discussions.microsoft.com> wrote:

>Hi all,
>I have a simple question, as follows.
>I have set up a couple of jobs which I have scheduled to
>run around the same time each night.
>One of the jobs works fine, but the other does not run, I
>have lloked into the problem and found that the tick box
>which enables scheduling, unchecks it's self each night.
>Is this possible and how can I stop it.
>Both jobs were set-up in exactly the same manner.
>Cheers.

Scheduling DTS packages in SQLServer 2005 via the Run Time utility

All,
I installed SQLServer 2005 on a new box and installed the DTS Runtime
utility as well so that the DTS packages run in the 2005 environment.
I imported all the DTS packages but I dont know how to schedule each of
them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on a DTS
package would create and schedule a job. I'm not sure how to do it here other
than creating the job manually.
Thanks,
rgnCreate an Agent job with a CmdExec jobstep. In this jobstep, you execute DTSRUN.EXE with appropriate
command-line options (see 2000 Books Online for documentation of the command-line options for
DTSRUN.EXE).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:5B08D6C7-9A39-49AF-8EA5-532627D5E310@.microsoft.com...
> All,
> I installed SQLServer 2005 on a new box and installed the DTS Runtime
> utility as well so that the DTS packages run in the 2005 environment.
> I imported all the DTS packages but I dont know how to schedule each of
> them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on a DTS
> package would create and schedule a job. I'm not sure how to do it here other
> than creating the job manually.
> Thanks,
> rgn
>|||rgn,
Apparently, since DTS is being deprecated the scheduling function did not
move over with the legacy support.
However, creating your own job is pretty easy, especially if you examine the
job definitions created for you on your SQL Server 2000 server. In fact, you
may be able to simply script out the jobs from SQL Server 2000 and run those
scripts on your 2005 SQL Server.
Some adjustements may be necessary. For example, if the same logins used
for the jobs on 2000 do not exist on your new 2005 server, you will need to
adjust the scripts to point to the logins you wish to use.
RLF
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:5B08D6C7-9A39-49AF-8EA5-532627D5E310@.microsoft.com...
> All,
> I installed SQLServer 2005 on a new box and installed the DTS Runtime
> utility as well so that the DTS packages run in the 2005 environment.
> I imported all the DTS packages but I dont know how to schedule each of
> them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on a
> DTS
> package would create and schedule a job. I'm not sure how to do it here
> other
> than creating the job manually.
> Thanks,
> rgn
>|||Tibor/Russell,
I should have been clearer in my earlier post. I can create a job for each
one of the DTS packages with DTSRUN. However, I dont know how to generate the
encrypted details of the package name, login name, Password ... etc.
It is against our SOX policy to include password in open text.
THis example is for a different DTS on a different server altogether.[DTSRun
/~Z0xBBA31CD08C42214454A70882A4D929948FA0915B8AA465A7BEF16CCA4AC7639EB256D85DB6780227228D2D92A3FF92D1AAC3354C13AF4CCF5704F24B8EA95C5C95E33BE0EAF73A5ED7C9F1D9AA391B364F64B7473F9E27823B3EF142CE09CF1F1BF7E08A031026BC2F7E03E544C824E13C2584B3C7197F19A12371 ]
Thanks,
rgn
"Russell Fields" wrote:
> rgn,
> Apparently, since DTS is being deprecated the scheduling function did not
> move over with the legacy support.
> However, creating your own job is pretty easy, especially if you examine the
> job definitions created for you on your SQL Server 2000 server. In fact, you
> may be able to simply script out the jobs from SQL Server 2000 and run those
> scripts on your 2005 SQL Server.
> Some adjustements may be necessary. For example, if the same logins used
> for the jobs on 2000 do not exist on your new 2005 server, you will need to
> adjust the scripts to point to the logins you wish to use.
> RLF
>
> "rgn" <rgn@.discussions.microsoft.com> wrote in message
> news:5B08D6C7-9A39-49AF-8EA5-532627D5E310@.microsoft.com...
> > All,
> >
> > I installed SQLServer 2005 on a new box and installed the DTS Runtime
> > utility as well so that the DTS packages run in the 2005 environment.
> >
> > I imported all the DTS packages but I dont know how to schedule each of
> > them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on a
> > DTS
> > package would create and schedule a job. I'm not sure how to do it here
> > other
> > than creating the job manually.
> >
> > Thanks,
> > rgn
> >
> >
>
>|||rgn,
I poked around a bit and found that the encrypted details are not as secure
as you might wish. So... user beware. Here is how you can generate one:
dtsrun /S ServerName /E /N PackagePathAndName /!Y
You will see that it gives a different encryption each time, but try it out
and see if the results work for you.
Since you are in SQL Server 2005, I encourage you to study up on SQL Agent
Proxies, which use Credentials for Logins to switch execution context before
running the Operating System step of DTSRUN. If that works for you, you can
run your DTS Packages without any user names or passwords in the command
line. Much more secure.
RLF
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:C777E793-E904-4D38-A361-E642C056AF7A@.microsoft.com...
> Tibor/Russell,
> I should have been clearer in my earlier post. I can create a job for each
> one of the DTS packages with DTSRUN. However, I dont know how to generate
> the
> encrypted details of the package name, login name, Password ... etc.
> It is against our SOX policy to include password in open text.
> THis example is for a different DTS on a different server
> altogether.[DTSRun
> /~Z0xBBA31CD08C42214454A70882A4D929948FA0915B8AA465A7BEF16CCA4AC7639EB256D85DB6780227228D2D92A3FF92D1AAC3354C13AF4CCF5704F24B8EA95C5C95E33BE0EAF73A5ED7C9F1D9AA391B364F64B7473F9E27823B3EF142CE09CF1F1BF7E08A031026BC2F7E03E544C824E13C2584B3C7197F19A12371
> ]
> Thanks,
> rgn
> "Russell Fields" wrote:
>> rgn,
>> Apparently, since DTS is being deprecated the scheduling function did not
>> move over with the legacy support.
>> However, creating your own job is pretty easy, especially if you examine
>> the
>> job definitions created for you on your SQL Server 2000 server. In fact,
>> you
>> may be able to simply script out the jobs from SQL Server 2000 and run
>> those
>> scripts on your 2005 SQL Server.
>> Some adjustements may be necessary. For example, if the same logins used
>> for the jobs on 2000 do not exist on your new 2005 server, you will need
>> to
>> adjust the scripts to point to the logins you wish to use.
>> RLF
>>
>> "rgn" <rgn@.discussions.microsoft.com> wrote in message
>> news:5B08D6C7-9A39-49AF-8EA5-532627D5E310@.microsoft.com...
>> > All,
>> >
>> > I installed SQLServer 2005 on a new box and installed the DTS Runtime
>> > utility as well so that the DTS packages run in the 2005 environment.
>> >
>> > I imported all the DTS packages but I dont know how to schedule each of
>> > them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on
>> > a
>> > DTS
>> > package would create and schedule a job. I'm not sure how to do it here
>> > other
>> > than creating the job manually.
>> >
>> > Thanks,
>> > rgn
>> >
>> >
>>sql

Scheduling a job under SA

I've shceduled a job under sa account (I've changed the password
though),this job access local folder of the box running SQL server.I have
added sa to the sysadmin role and it dose have access to the local folder
..How is it possible as *sa* is a sql server account and how it has the
enough permissions to access local file system?
Thanks a lot
If the job is owned by a sysadmin, it's operating under the
security context of the service account for SQL Agent.
-Sue
On Mon, 8 Aug 2005 16:25:10 -0700, "J-T" <J-T@.nospam.com>
wrote:

>I've shceduled a job under sa account (I've changed the password
>though),this job access local folder of the box running SQL server.I have
>added sa to the sysadmin role and it dose have access to the local folder
>.How is it possible as *sa* is a sql server account and how it has the
>enough permissions to access local file system?
>Thanks a lot
>
|||Thanks a lot
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:e36gf11g82of53tigjia7dqobotkfvp5pt@.4ax.com...
> If the job is owned by a sysadmin, it's operating under the
> security context of the service account for SQL Agent.
> -Sue
> On Mon, 8 Aug 2005 16:25:10 -0700, "J-T" <J-T@.nospam.com>
> wrote:
>

Scheduling a job under SA

I've shceduled a job under sa account (I've changed the password
though),this job access local folder of the box running SQL server.I have
added sa to the sysadmin role and it dose have access to the local folder
.How is it possible as *sa* is a sql server account and how it has the
enough permissions to access local file system?
Thanks a lotIf the job is owned by a sysadmin, it's operating under the
security context of the service account for SQL Agent.
-Sue
On Mon, 8 Aug 2005 16:25:10 -0700, "J-T" <J-T@.nospam.com>
wrote:

>I've shceduled a job under sa account (I've changed the password
>though),this job access local folder of the box running SQL server.I have
>added sa to the sysadmin role and it dose have access to the local folder
>.How is it possible as *sa* is a sql server account and how it has the
>enough permissions to access local file system?
>Thanks a lot
>|||Thanks a lot
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:e36gf11g82of53tigjia7dqobotkfvp5pt@.
4ax.com...
> If the job is owned by a sysadmin, it's operating under the
> security context of the service account for SQL Agent.
> -Sue
> On Mon, 8 Aug 2005 16:25:10 -0700, "J-T" <J-T@.nospam.com>
> wrote:
>
>

Scheduling a job under SA

I've shceduled a job under sa account (I've changed the password
though:)),this job access local folder of the box running SQL server.I have
added sa to the sysadmin role and it dose have access to the local folder
.How is it possible as *sa* is a sql server account and how it has the
enough permissions to access local file system?
Thanks a lotIf the job is owned by a sysadmin, it's operating under the
security context of the service account for SQL Agent.
-Sue
On Mon, 8 Aug 2005 16:25:10 -0700, "J-T" <J-T@.nospam.com>
wrote:
>I've shceduled a job under sa account (I've changed the password
>though:)),this job access local folder of the box running SQL server.I have
>added sa to the sysadmin role and it dose have access to the local folder
>.How is it possible as *sa* is a sql server account and how it has the
>enough permissions to access local file system?
>Thanks a lot
>|||Thanks a lot
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:e36gf11g82of53tigjia7dqobotkfvp5pt@.4ax.com...
> If the job is owned by a sysadmin, it's operating under the
> security context of the service account for SQL Agent.
> -Sue
> On Mon, 8 Aug 2005 16:25:10 -0700, "J-T" <J-T@.nospam.com>
> wrote:
>>I've shceduled a job under sa account (I've changed the password
>>though:)),this job access local folder of the box running SQL server.I
>>have
>>added sa to the sysadmin role and it dose have access to the local folder
>>.How is it possible as *sa* is a sql server account and how it has the
>>enough permissions to access local file system?
>>Thanks a lot
>sql

Scheduled Job History

Is there a way to increase the number of records preserved in job
history? I have 82 jobs on my box, 30 of them run every 20 minutes
for 23 hours a day, every 30 days. Another 30 run once, every 30
days. The system seems to have a limit of 50 history records for any
job that hasn't run since yesterday and purges all history records if
the job is more than a week old. I didn't know if there might be a
configuration record buried in MSDB or somewhere else that would allow
me to increase this size or perhaps a system SP that prunes job
history that I could modify.

It isn't critical as the system is set to notify me when jobs fail,
but still, I'd like to be able to look at a given day and verify that
everything went normally."P.D.N. Tame" <wwphx@.hotmail.com> wrote in message
news:bcc5d277.0312090628.5061b581@.posting.google.c om...
> Is there a way to increase the number of records preserved in job
> history? I have 82 jobs on my box, 30 of them run every 20 minutes
> for 23 hours a day, every 30 days. Another 30 run once, every 30
> days. The system seems to have a limit of 50 history records for any
> job that hasn't run since yesterday and purges all history records if
> the job is more than a week old. I didn't know if there might be a
> configuration record buried in MSDB or somewhere else that would allow
> me to increase this size or perhaps a system SP that prunes job
> history that I could modify.
> It isn't critical as the system is set to notify me when jobs fail,
> but still, I'd like to be able to look at a given day and verify that
> everything went normally.

In Enterprise Manage, right-click SQL Server Agent, then pick Properties,
Job System, and set the history options as you want. You can also use
sp_set_sqlagent_properties, but this procedure isn't documented, so it may
not be the best way to go.

Simon

schedule data driven subscription using stored procedure

I'm trying to set up a data driven subscription using stored
procedure, on step 3 box I typed in my stored procudure
name:proc_Reports_test and clicked on validate button, I got following
error message:
The dataset cannot be generated. An error occurred while connecting to
a data source, or the query is not valid for the data source.
(rsCannotPrepareQuery)
Line 1: Incorrect syntax near 'proc_Reports_test'.
Has anyone else had this issue?
Thanks advance for any help.Try 'exec proc_Reports_test' instead
--
-- "This posting is provided 'AS IS' with no warranties, and confers no
rights."
jhmiller@.online.microsoft.com
"Danni Liao" <danniliao@.yahoo.com> wrote in message
news:9d716b4a.0410210752.5a1fd0ba@.posting.google.com...
> I'm trying to set up a data driven subscription using stored
> procedure, on step 3 box I typed in my stored procudure
> name:proc_Reports_test and clicked on validate button, I got following
> error message:
> The dataset cannot be generated. An error occurred while connecting to
> a data source, or the query is not valid for the data source.
> (rsCannotPrepareQuery)
> Line 1: Incorrect syntax near 'proc_Reports_test'.
> Has anyone else had this issue?
> Thanks advance for any help.