scheduling package - Urgent

Hi all gurus
If I create a package and schedule it for jobs and then if i delete the
package and create a new package with same name. Then my job for old package
will run on new package which has name of old deleted package?
In my case my old job runs new package.
will it make any problem?
Thanks
AMHuh?
"AM" <anonymous@.codecomments.com> wrote in message
news:Or0wyERRFHA.3544@.TK2MSFTNGP12.phx.gbl...
> Hi all gurus
> If I create a package and schedule it for jobs and then if i delete the
> package and create a new package with same name. Then my job for old
> package
> will run on new package which has name of old deleted package?
> In my case my old job runs new package.
> will it make any problem?
> Thanks
> AM
>
>|||AM,
If you create a DTS package, then schedule it, then delete the package, and
create a new one with the EXACT same name, your scheduled job will still wor
k.
Hope that answers your question.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602_.html
"AM" wrote:

> Hi all gurus
> If I create a package and schedule it for jobs and then if i delete the
> package and create a new package with same name. Then my job for old packa
ge
> will run on new package which has name of old deleted package?
> In my case my old job runs new package.
> will it make any problem?
> Thanks
> AM
>
>sql

scheduling package - Urgent

Hi all gurus
If I create a package and schedule it for jobs and then if i delete the
package and create a new package with same name. Then my job for old package
will run on new package which has name of old deleted package?
In my case my old job runs new package.
will it make any problem?
Thanks
AMHuh?
"AM" <anonymous@.developersdex.com> wrote in message
news:Or0wyERRFHA.3544@.TK2MSFTNGP12.phx.gbl...
> Hi all gurus
> If I create a package and schedule it for jobs and then if i delete the
> package and create a new package with same name. Then my job for old
> package
> will run on new package which has name of old deleted package?
> In my case my old job runs new package.
> will it make any problem?
> Thanks
> AM
>
>|||AM,
If you create a DTS package, then schedule it, then delete the package, and
create a new one with the EXACT same name, your scheduled job will still work.
Hope that answers your question.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602­.html
"AM" wrote:
> Hi all gurus
> If I create a package and schedule it for jobs and then if i delete the
> package and create a new package with same name. Then my job for old package
> will run on new package which has name of old deleted package?
> In my case my old job runs new package.
> will it make any problem?
> Thanks
> AM
>
>

scheduling package- Urgent

Hi all gurus
If I create a package and schedule it for jobs and then if i delete the
package and create a new package with same name. Then my job for old package
will run on new package which has name of old deleted package?
In my case my old job runs new package.
will it make any problem?
Thanks
AM
Huh?
"AM" <anonymous@.codecomments.com> wrote in message
news:Or0wyERRFHA.3544@.TK2MSFTNGP12.phx.gbl...
> Hi all gurus
> If I create a package and schedule it for jobs and then if i delete the
> package and create a new package with same name. Then my job for old
> package
> will run on new package which has name of old deleted package?
> In my case my old job runs new package.
> will it make any problem?
> Thanks
> AM
>
>
|||AM,
If you create a DTS package, then schedule it, then delete the package, and
create a new one with the EXACT same name, your scheduled job will still work.
Hope that answers your question.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602X.html
"AM" wrote:

> Hi all gurus
> If I create a package and schedule it for jobs and then if i delete the
> package and create a new package with same name. Then my job for old package
> will run on new package which has name of old deleted package?
> In my case my old job runs new package.
> will it make any problem?
> Thanks
> AM
>
>

Scheduling Maintenance Jobs

Hi,

I have setup some maintenance jobs in SQL 2005 but when I try to schedule them I and then "save" the changes I get an error in a popup dialog saying

Caption "Microsoft SQL server management studio"

Error "Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)"

I have no idea what is causing this but it is preventing me from schduling my maintanance tasks. I would really appriciate any assistance with this.

Many thanks

Derek

Hi Derek,

The link http://support.microsoft.com/kb/922651 provides a workaround for the problem.

Thanks,

Kuntal

Scheduling jobs?

I need to schedule a job to run 6 days after the last Friday of the month.
How would I go about this?
Using SQL Server 2000 SP4
thanks in advanced.Hi,
SQLAgent will allow you to schedule based on the requirement. But what you
could do is schedule the job for all 30 days and
inside the procerdure you could write the logic to control this. For the
other days the procedure just checks and exits.
Thanks
Hari
"philt" <philt@.discussions.microsoft.com> wrote in message
news:3DE331CC-CE2B-4444-AB82-D80685FC099E@.microsoft.com...
>I need to schedule a job to run 6 days after the last Friday of the month.
> How would I go about this?
> Using SQL Server 2000 SP4
> thanks in advanced.|||Thanks Hari,
I understand what you are saying and did think about doing it that way. The
problem is I'm not sure what logic I could use or how as I don't write much
code. I'm reading up on GETDATE to see if that helps but if you or others
have an example it would be really helpful and appreciated.
Cheers,
Phil
"Hari Prasad" wrote:

> Hi,
> SQLAgent will allow you to schedule based on the requirement. But what you
> could do is schedule the job for all 30 days and
> inside the procerdure you could write the logic to control this. For the
> other days the procedure just checks and exits.
> Thanks
> Hari
> "philt" <philt@.discussions.microsoft.com> wrote in message
> news:3DE331CC-CE2B-4444-AB82-D80685FC099E@.microsoft.com...
>
>

Scheduling jobs?

I need to schedule a job to run 6 days after the last Friday of the month.
How would I go about this?
Using SQL Server 2000 SP4
thanks in advanced.Hi,
SQLAgent will allow you to schedule based on the requirement. But what you
could do is schedule the job for all 30 days and
inside the procerdure you could write the logic to control this. For the
other days the procedure just checks and exits.
Thanks
Hari
"philt" <philt@.discussions.microsoft.com> wrote in message
news:3DE331CC-CE2B-4444-AB82-D80685FC099E@.microsoft.com...
>I need to schedule a job to run 6 days after the last Friday of the month.
> How would I go about this?
> Using SQL Server 2000 SP4
> thanks in advanced.|||Thanks Hari,
I understand what you are saying and did think about doing it that way. The
problem is I'm not sure what logic I could use or how as I don't write much
code. I'm reading up on GETDATE to see if that helps but if you or others
have an example it would be really helpful and appreciated.
Cheers,
Phil
"Hari Prasad" wrote:
> Hi,
> SQLAgent will allow you to schedule based on the requirement. But what you
> could do is schedule the job for all 30 days and
> inside the procerdure you could write the logic to control this. For the
> other days the procedure just checks and exits.
> Thanks
> Hari
> "philt" <philt@.discussions.microsoft.com> wrote in message
> news:3DE331CC-CE2B-4444-AB82-D80685FC099E@.microsoft.com...
> >I need to schedule a job to run 6 days after the last Friday of the month.
> > How would I go about this?
> >
> > Using SQL Server 2000 SP4
> >
> > thanks in advanced.
>
>

Scheduling jobs?

I need to schedule a job to run 6 days after the last Friday of the month.
How would I go about this?
Using SQL Server 2000 SP4
thanks in advanced.
Hi,
SQLAgent will allow you to schedule based on the requirement. But what you
could do is schedule the job for all 30 days and
inside the procerdure you could write the logic to control this. For the
other days the procedure just checks and exits.
Thanks
Hari
"philt" <philt@.discussions.microsoft.com> wrote in message
news:3DE331CC-CE2B-4444-AB82-D80685FC099E@.microsoft.com...
>I need to schedule a job to run 6 days after the last Friday of the month.
> How would I go about this?
> Using SQL Server 2000 SP4
> thanks in advanced.
|||Thanks Hari,
I understand what you are saying and did think about doing it that way. The
problem is I'm not sure what logic I could use or how as I don't write much
code. I'm reading up on GETDATE to see if that helps but if you or others
have an example it would be really helpful and appreciated.
Cheers,
Phil
"Hari Prasad" wrote:

> Hi,
> SQLAgent will allow you to schedule based on the requirement. But what you
> could do is schedule the job for all 30 days and
> inside the procerdure you could write the logic to control this. For the
> other days the procedure just checks and exits.
> Thanks
> Hari
> "philt" <philt@.discussions.microsoft.com> wrote in message
> news:3DE331CC-CE2B-4444-AB82-D80685FC099E@.microsoft.com...
>
>

scheduling jobs that query linked servers

I have some SQL Servers that are linked and have created
a stored procedure on my primary SQL Server that queries
the linked servers. I also created a new login ID for
this.
I can run the stored proc anytime and it works great.
However, when I attempt to execute the stored proc from a
scheduled job I get the message: "Remote access not
allowed for Windows NT user activated by SETUSER."
I don't see how to get around this and still use the job
scheduler. Do I really have to use isql and put it in
scheduler software running outside MSSQL?
Can I run this T-SQL inside the scheduler with a
configuration switch somewhere? Or is this a "feature"
of MSSQL?
thanksIf you go to step properties, there is a drop down
box "run as user", from that list select the login that
has access to the linked server, that login also need to
have some access privileges to the database from which the
step is run.
hth.
>--Original Message--
>I have some SQL Servers that are linked and have created
>a stored procedure on my primary SQL Server that queries
>the linked servers. I also created a new login ID for
>this.
>I can run the stored proc anytime and it works great.
>However, when I attempt to execute the stored proc from a
>scheduled job I get the message: "Remote access not
>allowed for Windows NT user activated by SETUSER."
>I don't see how to get around this and still use the job
>scheduler. Do I really have to use isql and put it in
>scheduler software running outside MSSQL?
>Can I run this T-SQL inside the scheduler with a
>configuration switch somewhere? Or is this a "feature"
>of MSSQL?
>thanks
>
>.
>|||I tried that before and it did not work. I have not been
able to run this via any user in that drop down.
I have a situation where I can login via isql (sql server
authentication - not Windows auth.) and I am able to
execute the stored proc just fine. The stored proc
queries linked servers and works fine.
However when I try to use the Job Scheduler, I get the
error: "Remote access not allowed for Windows NT user
activated by SETUSER." When I attempt to run the job as
[self] I get: "Login failed for user 'NT
AUTHORITY\ANONYMOUS LOGON'."
Unless there is a hidden config option somewhere it
appears that the job scheduler cannot be used for remote
access to linked servers unless via a windows auth. login.
Is that true? If this is supposed to be a "security
feature" then it is pointless as far as I can tell.
We're on 2000 sp 3a
Jeff
>--Original Message--
>If you go to step properties, there is a drop down
>box "run as user", from that list select the login that
>has access to the linked server, that login also need to
>have some access privileges to the database from which
the
>step is run.
>hth.
>>--Original Message--
>>I have some SQL Servers that are linked and have
created
>>a stored procedure on my primary SQL Server that
queries
>>the linked servers. I also created a new login ID for
>>this.
>>I can run the stored proc anytime and it works great.
>>However, when I attempt to execute the stored proc from
a
>>scheduled job I get the message: "Remote access not
>>allowed for Windows NT user activated by SETUSER."
>>I don't see how to get around this and still use the
job
>>scheduler. Do I really have to use isql and put it in
>>scheduler software running outside MSSQL?
>>Can I run this T-SQL inside the scheduler with a
>>configuration switch somewhere? Or is this a "feature"
>>of MSSQL?
>>thanks
>>
>>.
>.
>|||I tried it myself and came to same conclusion as you for
now that you have to use windows auth. to access linked
servers via a jobschedule.
And looks like the problem is with the setuser command,
because when using nt auth. sqlagent is not using setuser
command, and if you use sql auth. then sqlagent is using
the setuser command. I tried this in QA also using setuser
for an nt auth. user who has sysadmin rights on both
servers and came back with the same error message "emote
access not allowed for Windows NT user activated by
SETUSER."
I will post more if I find something.
>--Original Message--
>I tried that before and it did not work. I have not been
>able to run this via any user in that drop down.
>I have a situation where I can login via isql (sql server
>authentication - not Windows auth.) and I am able to
>execute the stored proc just fine. The stored proc
>queries linked servers and works fine.
>However when I try to use the Job Scheduler, I get the
>error: "Remote access not allowed for Windows NT user
>activated by SETUSER." When I attempt to run the job as
>[self] I get: "Login failed for user 'NT
>AUTHORITY\ANONYMOUS LOGON'."
>Unless there is a hidden config option somewhere it
>appears that the job scheduler cannot be used for remote
>access to linked servers unless via a windows auth. login.
>Is that true? If this is supposed to be a "security
>feature" then it is pointless as far as I can tell.
>We're on 2000 sp 3a
>Jeff
>>--Original Message--
>>If you go to step properties, there is a drop down
>>box "run as user", from that list select the login that
>>has access to the linked server, that login also need to
>>have some access privileges to the database from which
>the
>>step is run.
>>hth.
>>--Original Message--
>>I have some SQL Servers that are linked and have
>created
>>a stored procedure on my primary SQL Server that
>queries
>>the linked servers. I also created a new login ID for
>>this.
>>I can run the stored proc anytime and it works great.
>>However, when I attempt to execute the stored proc from
>a
>>scheduled job I get the message: "Remote access not
>>allowed for Windows NT user activated by SETUSER."
>>I don't see how to get around this and still use the
>job
>>scheduler. Do I really have to use isql and put it in
>>scheduler software running outside MSSQL?
>>Can I run this T-SQL inside the scheduler with a
>>configuration switch somewhere? Or is this a "feature"
>>of MSSQL?
>>thanks
>>
>>.
>>.
>.
>|||This just gets stranger and stranger. On a hunch I set
up execution of my stored proc by a DTS package. I
schedule it and voila! it works!!?! It's not my
preferred way of doing this but if this is the kludge I
need to use to employ our of these inconsistent
behaviors, I'm going to use it.
Jeff
>--Original Message--
>I tried it myself and came to same conclusion as you for
>now that you have to use windows auth. to access linked
>servers via a jobschedule.
>And looks like the problem is with the setuser command,
>because when using nt auth. sqlagent is not using
setuser
>command, and if you use sql auth. then sqlagent is using
>the setuser command. I tried this in QA also using
setuser
>for an nt auth. user who has sysadmin rights on both
>servers and came back with the same error
message "emote
>access not allowed for Windows NT user activated by
>SETUSER."
>I will post more if I find something.
>
>>--Original Message--
>>I tried that before and it did not work. I have not
been
>>able to run this via any user in that drop down.
>>I have a situation where I can login via isql (sql
server
>>authentication - not Windows auth.) and I am able to
>>execute the stored proc just fine. The stored proc
>>queries linked servers and works fine.
>>However when I try to use the Job Scheduler, I get the
>>error: "Remote access not allowed for Windows NT user
>>activated by SETUSER." When I attempt to run the job
as
>>[self] I get: "Login failed for user 'NT
>>AUTHORITY\ANONYMOUS LOGON'."
>>Unless there is a hidden config option somewhere it
>>appears that the job scheduler cannot be used for
remote
>>access to linked servers unless via a windows auth.
login.
>>Is that true? If this is supposed to be a "security
>>feature" then it is pointless as far as I can tell.
>>We're on 2000 sp 3a
>>Jeff
>>--Original Message--
>>If you go to step properties, there is a drop down
>>box "run as user", from that list select the login
that
>>has access to the linked server, that login also need
to
>>have some access privileges to the database from which
>>the
>>step is run.
>>hth.
>>--Original Message--
>>I have some SQL Servers that are linked and have
>>created
>>a stored procedure on my primary SQL Server that
>>queries
>>the linked servers. I also created a new login ID
for
>>this.
>>I can run the stored proc anytime and it works
great.
>>However, when I attempt to execute the stored proc
from
>>a
>>scheduled job I get the message: "Remote access not
>>allowed for Windows NT user activated by SETUSER."
>>I don't see how to get around this and still use the
>>job
>>scheduler. Do I really have to use isql and put it
in
>>scheduler software running outside MSSQL?
>>Can I run this T-SQL inside the scheduler with a
>>configuration switch somewhere? Or is this
a "feature"
>>of MSSQL?
>>thanks
>>
>>.
>>.
>>.
>.
>

Scheduling jobs

It appears that SQL 2005 Express has removed the SQL Agent. Is this true?
Or, am I simply missing something obvious? If not there, does anyone know
the minimum version of SQL 2005 which enables job scheduling?
Thank in advance,
Gary Johnson
Hello,
Yes it is. SQL Express do not have SQL Agent. You could use Windows
schedular to schedule the tasks like Backup, Monitoring, Procedure execution
ect...
See the info from Microsoft URL:-
SQL Agent
SQL Agent is a SQL Server service that is used to automatically schedule job
execution for SQL Server. It is typically used to schedule the execution of
DTS packages or to perform system maintenance tasks like database backups.
While MSDE includes the SQL Agent service, SQL Server 2005 Express does not.
However, you can use the Windows built-in Task Scheduler to schedule jobs
for SQL Server 2005 Express. You can use Task Scheduler in combination with
the downloadable DTS runtime to automatically schedule the execution of DTS
packages. Likewise, you can use Task Scheduler in combination with the SQL
Server 2005 Express command-line SQLCMD tool to regularly execute SQL Server
2005 Express system maintenance jobs like database backups and other
database access jobs.
http://www.microsoft.com/technet/prodtechnol/sql/2005/msde2sqlexpress.mspx
Thanks
Hari
"Gary Johnson" <gary.johnson@.geoffreynyc.com> wrote in message
news:b9401$45baae1c$44a72b52$14138@.msgid.meganewss ervers.com...
> It appears that SQL 2005 Express has removed the SQL Agent. Is this true?
> Or, am I simply missing something obvious? If not there, does anyone know
> the minimum version of SQL 2005 which enables job scheduling?
> Thank in advance,
> Gary Johnson
>
|||Service Broker also works well as a job scheduler and is available in SQL
Express:
http://blogs.msdn.com/rogerwolterblog/archive/2006/04/13/575974.aspx
http://www.microsoft.com/technet/technetmag/issues/2005/05/ServiceBroker/default.aspx
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Gary Johnson" <gary.johnson@.geoffreynyc.com> wrote in message
news:b9401$45baae1c$44a72b52$14138@.msgid.meganewss ervers.com...
> It appears that SQL 2005 Express has removed the SQL Agent. Is this true?
> Or, am I simply missing something obvious? If not there, does anyone know
> the minimum version of SQL 2005 which enables job scheduling?
> Thank in advance,
> Gary Johnson
>
sql

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 jobs fails

Hello,
Could somebody tell me what i'm doing wrong. I have created a dts job from
the client console on my computer. Next i want to schedule the dts job, but
whenever it starts it is always failing.
Is it because i've created the dts job on my computer? I can see the owner
of the job is the name of my computer/username.
Greetings,
Zeke
I guess it has to do with security. When you schedule a job, it is executed
under different user account, not under yours. if you are a member of the
sysadmin role, then it is executed using SQL Server Agent's account.
Otherwise you can use so-called proxy account (check more in Books OnLine).
And the account used might not have permissions (maybe on file system as
well, not just SQL Server, depends on whatever the package is doing). Or it
does not see the drives you mapped using your account, etc.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Ezekil" <ezekiel@.lycos.nl> wrote in message
news:%23EwqWe1MEHA.2540@.TK2MSFTNGP10.phx.gbl...
> Hello,
> Could somebody tell me what i'm doing wrong. I have created a dts job from
> the client console on my computer. Next i want to schedule the dts job,
but
> whenever it starts it is always failing.
> Is it because i've created the dts job on my computer? I can see the owner
> of the job is the name of my computer/username.
> Greetings,
> Zeke
>

scheduling dts jobs fails

Hello,
Could somebody tell me what i'm doing wrong. I have created a dts job from
the client console on my computer. Next i want to schedule the dts job, but
whenever it starts it is always failing.
Is it because i've created the dts job on my computer? I can see the owner
of the job is the name of my computer/username.
Greetings,
ZekeI guess it has to do with security. When you schedule a job, it is executed
under different user account, not under yours. if you are a member of the
sysadmin role, then it is executed using SQL Server Agent's account.
Otherwise you can use so-called proxy account (check more in Books OnLine).
And the account used might not have permissions (maybe on file system as
well, not just SQL Server, depends on whatever the package is doing). Or it
does not see the drives you mapped using your account, etc.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Ezekil" <ezekiel@.lycos.nl> wrote in message
news:%23EwqWe1MEHA.2540@.TK2MSFTNGP10.phx.gbl...
> Hello,
> Could somebody tell me what i'm doing wrong. I have created a dts job from
> the client console on my computer. Next i want to schedule the dts job,
but
> whenever it starts it is always failing.
> Is it because i've created the dts job on my computer? I can see the owner
> of the job is the name of my computer/username.
> Greetings,
> Zeke
>

scheduling dts jobs fails

Hello,
Could somebody tell me what i'm doing wrong. I have created a dts job from
the client console on my computer. Next i want to schedule the dts job, but
whenever it starts it is always failing.
Is it because i've created the dts job on my computer? I can see the owner
of the job is the name of my computer/username.
Greetings,
ZekeI guess it has to do with security. When you schedule a job, it is executed
under different user account, not under yours. if you are a member of the
sysadmin role, then it is executed using SQL Server Agent's account.
Otherwise you can use so-called proxy account (check more in Books OnLine).
And the account used might not have permissions (maybe on file system as
well, not just SQL Server, depends on whatever the package is doing). Or it
does not see the drives you mapped using your account, etc.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Ezekiël" <ezekiel@.lycos.nl> wrote in message
news:%23EwqWe1MEHA.2540@.TK2MSFTNGP10.phx.gbl...
> Hello,
> Could somebody tell me what i'm doing wrong. I have created a dts job from
> the client console on my computer. Next i want to schedule the dts job,
but
> whenever it starts it is always failing.
> Is it because i've created the dts job on my computer? I can see the owner
> of the job is the name of my computer/username.
> Greetings,
> Zeke
>

Scheduling a .sql file through "jobs"

This is going to be a stupid, easy question; but I'm a SQL Server Newbie, so
here goes...
I have a .sql file that I need to schedule to run through SQL Server. The
actual SQL in it is too large to be pasted into the Exec Transact-SQL screen
on the scheduler. Is there a way to just call the .sql file from
transact-sql? Something like, "exec c:\scripts\analyzedb.sql", or something
along those lines? I've just been looking and looking for this, and can't
find it... thanks for any help anyone can give me.
Set the type of your jobstep to CmdExec instead of TSQL. CmdExec steps can
run commandline commands and batch files. You can then use the SQL Server
command line tool to run the script. The syntax for this is something like:
osql -E -i yourfilename.sql
For more details on osql see Books Online.
Jacco Schalkwijk
SQL Server MVP
"Amy" <Amy@.discussions.microsoft.com> wrote in message
news:999685D4-886D-42B0-A24A-F8A4FEBCAE00@.microsoft.com...
> This is going to be a stupid, easy question; but I'm a SQL Server Newbie,
> so
> here goes...
> I have a .sql file that I need to schedule to run through SQL Server. The
> actual SQL in it is too large to be pasted into the Exec Transact-SQL
> screen
> on the scheduler. Is there a way to just call the .sql file from
> transact-sql? Something like, "exec c:\scripts\analyzedb.sql", or
> something
> along those lines? I've just been looking and looking for this, and can't
> find it... thanks for any help anyone can give me.
>
|||Thanks, Jacco! That was just what I needed to know... :-)
"Jacco Schalkwijk" wrote:

> Set the type of your jobstep to CmdExec instead of TSQL. CmdExec steps can
> run commandline commands and batch files. You can then use the SQL Server
> command line tool to run the script. The syntax for this is something like:
> osql -E -i yourfilename.sql
> For more details on osql see Books Online.
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Amy" <Amy@.discussions.microsoft.com> wrote in message
> news:999685D4-886D-42B0-A24A-F8A4FEBCAE00@.microsoft.com...
>
>

scheduled TRN backups failing (sql2000)

I have created a backup that does once weekly BAK and every night it does TRN backup. This is in the same maintaince plan, the jobs appear as seprate jobs as they should. I have noticed my TRN is always failing, after looking into the event logs i see this.

please note this is lastest time to early:

4:22pm
this is the warning that the event log gives:

SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan 'xxxxxxxx TRN'' (0xB87B2FA07E4FB74CA01A1D38134C9C4F) - Status: Failed - Invoked on: 2007-03-09 16:19:40 - Message: The job failed. The Job was invoked by User domain\Administrator. The last step to run was step 1 (Step 1).

the next is
4:22pm
18265 :
Log backed up: Database: Staging, creation date(time): 2007/01/30(09:35:34), first LSN: 24624:14008:1, last LSN: 24624:14021:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'f:\program files\microsoft sql server\MSSQL\BACKUP\Staging\Staging_tlog_200703091622.TRN'}).

last is 4:21pm
18264 :
Database backed up: Database: Staging, creation date(time): 2007/01/30(09:35:34), pages dumped: 93982, first LSN: 24624:14008:2, last LSN: 24624:14018:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'f:\program files\microsoft sql server\MSSQL\BACKUP\Staging\Staging_db_200703091618.BAK'}).

So for some very strange reason its running a full backup then a Transactional, for this reason i would say its failing but why is it even doing this backup? the job is only for TRN?

A manual TRN backup works like a treat

Thanks

BRAD

CHECK what is the recovery model of your database... make sure it is not Simple... If it is simple it is normal to have this behaviour

Madhu

|||

ran sp_helpdb all of my databases are at full recovery apart from the tmpdb and another system DB but these are not in the backup plan only user databases are.

any other ideas?

|||

never mind you were right there was the northwind database still active (by default set to simple) this is classed as a user DB.

Thanks

Brad

Scheduled transaction log backup never finish

Hi,
I run a scheduled transaction log job back up serval database's log
everyday, it was fine before, however, today, one of jobs seems can not stop
running. Checked no deadlock process, checked log file in disk, only two
database can not finish. using dbcc opentran, no active tran. change those
two database to another job, same thing happening, What could I do?
Any help would be appreciated.
Cheers
YifeiCancel the job using the Process Info under Current
Activity.
Have a look and see if there are any error messages being
generated in the SQL Server Logs, then try again.
Peter
"Never ascribe to malice, that which can be explained by
incompetence."
Napoleon
>--Original Message--
>Hi,
>I run a scheduled transaction log job back up serval
database's log
>everyday, it was fine before, however, today, one of jobs
seems can not stop
>running. Checked no deadlock process, checked log file in
disk, only two
>database can not finish. using dbcc opentran, no active
tran. change those
>two database to another job, same thing happening, What
could I do?
>Any help would be appreciated.
>Cheers
>Yifei
>
>.
>|||Hi Peter,
Thank you for reply, I do cancel the job and restart it again, the problem
still exist.
Actually I restart sql server, it's been fixed.
But, it looks strange.
Yifei
"Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:18a901c51b1f$feb702f0$a601280a@.phx.gbl...
> Cancel the job using the Process Info under Current
> Activity.
> Have a look and see if there are any error messages being
> generated in the SQL Server Logs, then try again.
> Peter
> "Never ascribe to malice, that which can be explained by
> incompetence."
> Napoleon
>
> >--Original Message--
> >Hi,
> >
> >I run a scheduled transaction log job back up serval
> database's log
> >everyday, it was fine before, however, today, one of jobs
> seems can not stop
> >running. Checked no deadlock process, checked log file in
> disk, only two
> >database can not finish. using dbcc opentran, no active
> tran. change those
> >two database to another job, same thing happening, What
> could I do?
> >
> >Any help would be appreciated.
> >
> >Cheers
> >
> >Yifei
> >
> >
> >
> >.
> >

Scheduled jobs suddenly failing

I have MS SQL Server 2000 sp? on Windows 2000.
I have various jobs set up to run with the SQL Server Agent. I have a
job that imports data from an Access database located on the same
server. Then later, a job runs that updates some rows.

The import job fails with an error saying the source data is opened
exclusively by someone else, or I don't have permission. I have
verifed through various tests that no one else is using the source
Access database. I have even tried this import from excel files and
csv text files.

The job which updates a few rows will run with no problem.

This is a newly created job (actually a DTS package that was saved and
scheduled to run as a job)

Recently though, the server was renamed, and I feel this is the cause.
I have checked the msdb.sysjobs table and some of the jobs with the
new server name work, and some of them don't. The DTS jobs don't seem
to work.

I have maintenace jobs that used to run successfully, but now fail.

I have also tried to run the job with various users as well as SA.

Any ideas would greatly be appreciated.<OakRogbak_erPine@.yahoo.com> wrote in message
news:13fdc9b4.0408100537.1b66cbec@.posting.google.c om...
> I have MS SQL Server 2000 sp? on Windows 2000.
> I have various jobs set up to run with the SQL Server Agent. I have a
> job that imports data from an Access database located on the same
> server. Then later, a job runs that updates some rows.
> The import job fails with an error saying the source data is opened
> exclusively by someone else, or I don't have permission. I have
> verifed through various tests that no one else is using the source
> Access database. I have even tried this import from excel files and
> csv text files.
> The job which updates a few rows will run with no problem.
> This is a newly created job (actually a DTS package that was saved and
> scheduled to run as a job)
> Recently though, the server was renamed, and I feel this is the cause.
> I have checked the msdb.sysjobs table and some of the jobs with the
> new server name work, and some of them don't. The DTS jobs don't seem
> to work.
> I have maintenace jobs that used to run successfully, but now fail.
> I have also tried to run the job with various users as well as SA.
> Any ideas would greatly be appreciated.

You might want to investigate if the server name was changed correctly - did
you follow the steps in Books Online exactly?

http://support.microsoft.com/defaul...4&Product=sql2k

You might also want to check if sp_helpserver and select @.@.servername return
the correct output. If you have data sources in DTS packages which reference
the old name, then they will need to be updated in each package also (unless
you set the name dynamically at runtime of course).

If this doesn't help, please post the precise error messages, as well as the
version of MSSQL/Excel.

Simon

scheduled jobs question

what are the elements that I should review to ensure multiple scheduled SQL
jobs do not ''collide'' with each other? Thank you.
You can have only one instance of a scheduled job running at a given time.
However, you could have several different jobs that could conflict. Check
out sp_getapplock and sp_releaseapplock in the BOL for a means of dealing
with this issue.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
..
"baybreeze" <baybreeze@.discussions.microsoft.com> wrote in message
news:1FBF3609-8879-4E84-AEC0-050EED1A3154@.microsoft.com...
what are the elements that I should review to ensure multiple scheduled SQL
jobs do not ''collide'' with each other? Thank you.
|||What is yoru specifc issue?
What you can also do is start others jobs based on conditions is other
jobs using sp_start_job. Sometimes I will use this technique to start
a fullbackup job after DBCC runs.
Bert