scheduling sql sp needing to access mapped network drives

How to make network drives accessible to a stored procedure? Currently the sp works only if I open a session on the server and execute the sp with SQL Server Management Studio on the server.

If you want to use ressources within the network you will need appropiate permissions either for the service account SQL Server Service is running with or the service account SQL Server Agent is running with (if you do that within a scheduled job). An alternative would be to setup a proxy account for the service [1]

[1] http://www.databasejournal.com/features/mssql/article.php/1580041

In SQL Server 2005 proxy accounts can also be configured through the Configuration interface which you will find in the program collection.

HTH, Jens SUessmeyer.

http://www.sqlserver2005.de

|||Moving to "SQL Server Database Engine", which is more suitable for this question.|||You want to access via UNC instead of mapped network drive (i.e. \\server\shared).

Do check out security implication posted by Jens.sql

Scheduling sp_updatestats

Any reason NOT to use DTS to execute sp_updatestats on a daily basis?
Is there a better way to schedule that outside of a maintenance plan ?I prefer to use a SQL Agent Job. Using DTS isn't really necessary (and is
the wrong tool) in 'most' cases.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"J1C" <just1coder@.yahoo.ca> wrote in message
news:1164670349.026026.226980@.l39g2000cwd.googlegroups.com...
> Any reason NOT to use DTS to execute sp_updatestats on a daily basis?
> Is there a better way to schedule that outside of a maintenance plan ?
>|||Hello,
Why do you need DTS for this. All you have to do is:-
1. Open Enterprise Manager
2. Connect to SQL Server
3. Expand Management, Select Jobs and create new job.
4. In the job step give sp_updatestats and choose database
5. Provide a schedule to execute
6. Save the job
Based on the schedule.. SQL Server agent will trigger this job
Thanks
Hari
"J1C" <just1coder@.yahoo.ca> wrote in message
news:1164670349.026026.226980@.l39g2000cwd.googlegroups.com...
> Any reason NOT to use DTS to execute sp_updatestats on a daily basis?
> Is there a better way to schedule that outside of a maintenance plan ?
>|||Hari Prasad wrote:[vbcol=seagreen]
> Hello,
> Why do you need DTS for this. All you have to do is:-
> 1. Open Enterprise Manager
> 2. Connect to SQL Server
> 3. Expand Management, Select Jobs and create new job.
> 4. In the job step give sp_updatestats and choose database
> 5. Provide a schedule to execute
> 6. Save the job
> Based on the schedule.. SQL Server agent will trigger this job
> Thanks
> Hari
> "J1C" <just1coder@.yahoo.ca> wrote in message
> news:1164670349.026026.226980@.l39g2000cwd.googlegroups.com...
Thanks - that is what I ended up doing rather than DTS.

Scheduling sp_updatestats

Any reason NOT to use DTS to execute sp_updatestats on a daily basis?
Is there a better way to schedule that outside of a maintenance plan ?I prefer to use a SQL Agent Job. Using DTS isn't really necessary (and is
the wrong tool) in 'most' cases.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"J1C" <just1coder@.yahoo.ca> wrote in message
news:1164670349.026026.226980@.l39g2000cwd.googlegroups.com...
> Any reason NOT to use DTS to execute sp_updatestats on a daily basis?
> Is there a better way to schedule that outside of a maintenance plan ?
>|||Hello,
Why do you need DTS for this. All you have to do is:-
1. Open Enterprise Manager
2. Connect to SQL Server
3. Expand Management, Select Jobs and create new job.
4. In the job step give sp_updatestats and choose database
5. Provide a schedule to execute
6. Save the job
Based on the schedule.. SQL Server agent will trigger this job
Thanks
Hari
"J1C" <just1coder@.yahoo.ca> wrote in message
news:1164670349.026026.226980@.l39g2000cwd.googlegroups.com...
> Any reason NOT to use DTS to execute sp_updatestats on a daily basis?
> Is there a better way to schedule that outside of a maintenance plan ?
>|||Hari Prasad wrote:
> Hello,
> Why do you need DTS for this. All you have to do is:-
> 1. Open Enterprise Manager
> 2. Connect to SQL Server
> 3. Expand Management, Select Jobs and create new job.
> 4. In the job step give sp_updatestats and choose database
> 5. Provide a schedule to execute
> 6. Save the job
> Based on the schedule.. SQL Server agent will trigger this job
> Thanks
> Hari
> "J1C" <just1coder@.yahoo.ca> wrote in message
> news:1164670349.026026.226980@.l39g2000cwd.googlegroups.com...
> > Any reason NOT to use DTS to execute sp_updatestats on a daily basis?
> > Is there a better way to schedule that outside of a maintenance plan ?
> >
Thanks - that is what I ended up doing rather than DTS.

Scheduling sp_updatestats

Any reason NOT to use DTS to execute sp_updatestats on a daily basis?
Is there a better way to schedule that outside of a maintenance plan ?
I prefer to use a SQL Agent Job. Using DTS isn't really necessary (and is
the wrong tool) in 'most' cases.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"J1C" <just1coder@.yahoo.ca> wrote in message
news:1164670349.026026.226980@.l39g2000cwd.googlegr oups.com...
> Any reason NOT to use DTS to execute sp_updatestats on a daily basis?
> Is there a better way to schedule that outside of a maintenance plan ?
>
|||Hello,
Why do you need DTS for this. All you have to do is:-
1. Open Enterprise Manager
2. Connect to SQL Server
3. Expand Management, Select Jobs and create new job.
4. In the job step give sp_updatestats and choose database
5. Provide a schedule to execute
6. Save the job
Based on the schedule.. SQL Server agent will trigger this job
Thanks
Hari
"J1C" <just1coder@.yahoo.ca> wrote in message
news:1164670349.026026.226980@.l39g2000cwd.googlegr oups.com...
> Any reason NOT to use DTS to execute sp_updatestats on a daily basis?
> Is there a better way to schedule that outside of a maintenance plan ?
>
|||Hari Prasad wrote:[vbcol=seagreen]
> Hello,
> Why do you need DTS for this. All you have to do is:-
> 1. Open Enterprise Manager
> 2. Connect to SQL Server
> 3. Expand Management, Select Jobs and create new job.
> 4. In the job step give sp_updatestats and choose database
> 5. Provide a schedule to execute
> 6. Save the job
> Based on the schedule.. SQL Server agent will trigger this job
> Thanks
> Hari
> "J1C" <just1coder@.yahoo.ca> wrote in message
> news:1164670349.026026.226980@.l39g2000cwd.googlegr oups.com...
Thanks - that is what I ended up doing rather than DTS.

Scheduling not working

I have an Active Task in a DTS which uses CDONTS to send an email. When I
execute the package manually it works. The schedule doesn't. It says in the
job list that it has been successful. The email does not, however, get sent.
The job, server agent and task scheduler are all enabled. I have even tried
setting up the job/dts package on the server in case there was some kind of
permissions issue. Any ideas? Regards, Chris.The solution was specify a user name that belonged to sysadmin when creating
the package and schedule.
"Chris Kennedy" <chrisknospam@.cybase.co.uk> wrote in message
news:enmaP4%23REHA.3444@.TK2MSFTNGP12.phx.gbl...
> I have an Active Task in a DTS which uses CDONTS to send an email. When I
> execute the package manually it works. The schedule doesn't. It says in
the
> job list that it has been successful. The email does not, however, get
sent.
> The job, server agent and task scheduler are all enabled. I have even
tried
> setting up the job/dts package on the server in case there was some kind
of
> permissions issue. Any ideas? Regards, Chris.
>

scheduling delivery

i would like to ask how to execute the email delivery setting? can it be done
in the report server homepage'it is a must to get it work through web
service programming?
thanks in advanceIts form the report MANAGER home page http://servername/reports. Go to
whtever report you want the set the subscription on, and when you view the
report, you have a tab saying new subscription, click on tht and give the
parameter info and the schedule info.
"Jasonymk" wrote:
> i would like to ask how to execute the email delivery setting? can it be done
> in the report server homepage'it is a must to get it work through web
> service programming?
> thanks in advancesql

Scheduling a DTS package without admin privileges.

I have created a dts package that I can execute from within sql server
enterprise manager. However, I don’t have admin privileges so when I
schedule a job within sql server it fails to execute because I don’t have
the
necessary privileges.
Since I have the privileges to run the DTS package I have created I am
interested in another means of scheduling my DTS package. I was thinking of
making use of the windows task scheduler or if that is not possible making a
windows service.
Right now I am using the dtsrun.exe but I can only use this if sql
server is installed on the machine that requests the DTS package to be
executed. I was hoping to find a way to request the DTS Package to be run
from any machine of my choosing. I got excited when I found the DTS com dl
l
but it appears only to provide a wrapper that communicates with the locally
installed sqlserver. Is there another way to do this other than have admin
privileges and keep it on the actually server? For now I have created a dts
substitute…Basically I have every thing I need to do in a series of stored
procedures and I call that from a windows task scheduler. (However I am
missing email and other capabilities.) Do I really need admin privileges to
be able to schedule a DTS package?Hello,
The security context in which the DTS job is run is determined by the owner
of the job. If the job is owned by a login that is not a member of the
Symin server role, then the package is run under the context of the
account setup as the SQL Agent Proxy Account, and has the rights and
permissions of that account.
For SQL Agent Proxy to be able to run jobs that connect to SQL Server, the
SQL Agent Proxy account must have proper Windows/NT permissions and be
granted login access to SQL Server with appropriate database permissions.
For the jobs that execute a DTS package, the SQL Agent Proxy Account must
have read and write permissions to the temp directory of the Account the
SQL Server Agent is running under. For example,
c:\Documents and Settings\<Account>\Local Settings\Temp
You may want to look at the following article:
http://support.microsoft.com/defaul...kb;en-us;269074
also the security discussions at:
http://support.microsoft.com/defaul...kb;en-us;252987
http://support.microsoft.com/defaul...kb;en-us;322746
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Scheduling a DTS package without admin privileges.
>thread-index: AcZD0ZYb2apHTm+GQoGmib/7CppZqQ==
>X-WBNR-Posting-Host: 66.162.65.194
>From: examnotes <JeffDotNet@.newsgroups.nospam>
>Subject: Scheduling a DTS package without admin privileges.
>Date: Thu, 9 Mar 2006 15:31:27 -0800
>Lines: 20
>Message-ID: <2AB4DFE2-6F42-4DD5-8AAF-339819986F39@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.programming
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.programming:586021
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.programming
>I have created a dts package that I can execute from within sql server
>enterprise manager. However, I don’t have admin privileges so when I
>schedule a job within sql server it fails to execute because I don’t
have the
>necessary privileges.
> Since I have the privileges to run the DTS package I have created I am
>interested in another means of scheduling my DTS package. I was thinking
of
>making use of the windows task scheduler or if that is not possible making
a
>windows service.
> Right now I am using the dtsrun.exe but I can only use this if sql
>server is installed on the machine that requests the DTS package to be
>executed. I was hoping to find a way to request the DTS Package to be run
>from any machine of my choosing. I got excited when I found the DTS com
dll
>but it appears only to provide a wrapper that communicates with the
locally
>installed sqlserver. Is there another way to do this other than have
admin
>privileges and keep it on the actually server? For now I have created a
dts
>substitute…Basically I have every thing I need to do in a series of
stored
>procedures and I call that from a windows task scheduler. (However I am
>missing email and other capabilities.) Do I really need admin privileges
to
>be able to schedule a DTS package?
>

Scheduling

Hi
when scheduling SQL server DTS packages, i know we can set up a chain of
steps saying(let's say) execute step2 on success of step1. But can we specify
multiple chaining...meaning to say that execute step3 on success of both
step1 and step2.
Any help would be appreciated.
Thanks
Neeraj
The default behavior of a SQL Agent job step is to quit the job when an
error occurs. Consequently, step 3 will execute only if both steps 1 and 2
succeed.
Hope this helps.
Dan Guzman
SQL Server MVP
"ReportFAQGuy" <ReportFAQGuy@.discussions.microsoft.com> wrote in message
news:335C71C0-D023-4C11-B99A-907CAC6DE965@.microsoft.com...
> Hi
> when scheduling SQL server DTS packages, i know we can set up a chain of
> steps saying(let's say) execute step2 on success of step1. But can we
> specify
> multiple chaining...meaning to say that execute step3 on success of both
> step1 and step2.
> Any help would be appreciated.
> Thanks
> Neeraj

Scheduling

Hi
when scheduling SQL server DTS packages, i know we can set up a chain of
steps saying(let's say) execute step2 on success of step1. But can we specify
multiple chaining...meaning to say that execute step3 on success of both
step1 and step2.
Any help would be appreciated.
Thanks
NeerajThe default behavior of a SQL Agent job step is to quit the job when an
error occurs. Consequently, step 3 will execute only if both steps 1 and 2
succeed.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"ReportFAQGuy" <ReportFAQGuy@.discussions.microsoft.com> wrote in message
news:335C71C0-D023-4C11-B99A-907CAC6DE965@.microsoft.com...
> Hi
> when scheduling SQL server DTS packages, i know we can set up a chain of
> steps saying(let's say) execute step2 on success of step1. But can we
> specify
> multiple chaining...meaning to say that execute step3 on success of both
> step1 and step2.
> Any help would be appreciated.
> Thanks
> Neerajsql

Scheduled tasks

Is it possible to schedule tasks in SQL Express, for example a database backup, or to periodically execute a stored procedure?

hi Allan,

yes, it is possible, but not using the SQL Server Agent as SQLExpress does not provide the relative bits.. you have so to rely on the native OS scheduler, third party (or self written alternative) scheduler, or rely on the Service Broker features..

personally I usually go for the native OS scheduler, where you can define a list of xx.sql scripts to be executed by a xx.cmd file.. then the xx.cmd file, connecting to SqlCMD.exe and executing each defined xx.sql script, has to be scheduled... quiete simple and not expensive... results are output to a text file similar to:

[cmdfile.cmd]

ECHO. >>Backing up databases

SqlCmd -E -S(Local)\InstanceName -i"c:\somefolder\ScheduledBackup.sql" >c:\SomeFolder\ScheduledBackupLog.txt

ECHO. >>Sending results via mail to aministrators

SqlCmd-E -S(Local) -Q"SET NOCOUNT ON; SELECT 'Mailing log of - ' + CONVERT(varchar, GETDATE());" >E:\e-VbHot\Files\Log\MailingLogBCKschedulato.txt
SqlCmd -E -S(Local)\InstanceName -Q"SET NOCOUNT ON; DECLARE @.ret int;EXEC @.ret = [applicationDB].[dbo].[amSMTPmail] @.Server = N'smtp server name', @.Sender = N'scheduledbackup@.my_company.com', @.AddressesTO = N'admin_name@.my_company.com', @.AddressesCC = N'me@.me.com', @.AddressesCCN = NULL, @.AttachFiles = N'c:\SomeFolder\ScheduledBackupLog.txt', @.Subject = N'Backup performed', @.MessageBody = N'Backup performed', @.UserName = NULL, @.UserPassword = NULL; SELECT @.ret AS [Execution result];" >>c:\SomeFolder\MailingLog.txt

[/cmdfile.cmd]

as you can see, I do personally even send the c:\SomeFolder\ScheduledBackupLog.txt resulting file via e-mail to a "list" of addresses.. this is performed via a (free) CLR stored procedure of mine, amDBObj, where the .Net code implements a poor's man SMTP mail feature to "replace" (ok... it is not comparable with) Database Mail missing feature of SQLExpress..

regards

|||

Thanks for the info Andrea. I will look into it.

Thanks, too, for the offer of the CLR email proc - but I already did one myself :)

sql

Scheduled package problem: Class not registered

Hi,

Attempting to schedule and execute a package. The server is a 64bit clustered sql 2005 server.

The package was developed on my local install of sql 2005 client tools. I can run the package within BIDS, I can export and run the package from MSDB, but I cannot get it to execute without failure when scheduled.

I suspect it is some weirdness caused by the difference between 32 bit and 64 bit type program, but do not know what to do to figure it out.

Job history output below:

Date 14/09/2007 1:07:30 PM
Log Job History (SISS)

Step ID 1
Server servername

Job Name SSIS test job
Step Name Import NE Outpat
Duration 00:00:02
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: HAHS\billsqlserver. ...9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 1:07:30 PM Progress: 2007-09-14 13:07:31.54 Source: Clinics Validating: 0% complete End Progress Progress: 2007-09-14 13:07:31.54 Source: Clinics Validating: 33% complete End Progress Progress: 2007-09-14 13:07:31.75 Source: Clinics Validating: 66% complete End Progress Error: 2007-09-14 13:07:31.89 Code: 0xC0202009 Source: ImportNewEnglandOutpatientData Connection manager "Clinics" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040154. An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered". End Error Error: 2007-09-14 13:07:31.89 Code: 0xC020801C Source: Clinics Clinics Access Database [15] Description: SSIS Error Code DTS_E_CANNOTACQ... The package execution fa... The step failed.

Thanks for all suggestions,

Does the package run when executed from SQL Management Studio on the server itself?|||

Hi,

Not sure.....

Been doing some further reading, and found:

"Noted that the Microsoft OLE DB Provider for Jet, used for Access and Excel databases, is not available in a 64-bit version."

on http://msdn2.microsoft.com/en-us/library/ms141766.aspx

The package has 4 MS access as datasources and imports the data into 2005.

Is this possible? is there another way around this?

|||

Well it sounds to me like you are on the right track.

Someone else will ahve to answer the 64bit question. I have no experience with using Access on a 64 bit install (thank god!)

|||

You cannot run this package in 64-bit mode as there is no 64-bit JET provider. Use the 32-bit dtexec when scheduling your jobs.

Thanks,

Bob

sql

Scheduled Jobs & Failed Notifications

Periodically on jobs scheduled in the SQL Server Management, a scheduled job will execute successfully, but fail to email the notification to the operator that the job completed successfully.....anyone have any thoughts as to the cause
I welcome any input ! :)Make sure your windows application log is not full, if it is, you will not
get notified.
--
Ray Higdon MCSE, MCDBA, CCNA
--
"David Moe" <dmoe@.coorstek.com> wrote in message
news:BCDD08D7-A9D6-4717-93D0-100DBBF38C98@.microsoft.com...
> Periodically on jobs scheduled in the SQL Server Management, a scheduled
job will execute successfully, but fail to email the notification to the
operator that the job completed successfully.....anyone have any thoughts
as to the cause ?
> I welcome any input ! :)|||if you never get email notification work, that means
maybe you havn't configure the sql mail utility.
>--Original Message--
>Periodically on jobs scheduled in the SQL Server
Management, a scheduled job will execute successfully,
but fail to email the notification to the operator that
the job completed successfully.....anyone have any
thoughts as to the cause ?
>I welcome any input ! :)
>.
>|||This thread is on a server which has other working alerts, typically including the one that failed
All other alerts executed with no problems...just this one fails periodically....haven't been able to coorelate any problems with server or database(s) on said server
It simply states in both the job history and the application event log that the notification failed. (Event log is set to overwrite
This same operator is used in all of the alerts coming from this particular server
-- David Moe wrote: --
Periodically on jobs scheduled in the SQL Server Management, a scheduled job will execute successfully, but fail to email the notification to the operator that the job completed successfully.....anyone have any thoughts as to the cause
I welcome any input ! :)

Scheduled Job works when run manually but not when scheduled

Hi
I have a very simple local package, which performs the following:
1. Execute SQL Task
Delete from PURCHASE_LEDGER
Delete from SALES_LEDGER
2. Transform Data task
Copy everything from SAGE PURCHASE_LEDGER to SQL PURCHASE_LEDGER
Copy everything from SAGE SALES_LEDGER to SQL SALES_LEDGER
There is a workflow between steps 1 and 2, so that step 2 only
executes if step 1 is successfull.
The connection to SAGE is ODBC (which I know works fine) and to SQL it
is OLE.
This package works perfectly if I right click on it and select
execute. However, if I schedule it, the first step works perfectly but
the second step fails. I know that the first step works because the
tables are empty. If I remove the first step and the workflow from the
package, the transform data task still does not work when scheduled,
but is fine when I run it manually. In the error log, it just says:
"SQL Server Scheduled Job 'Update SAGE
Tables' (0x3B6A429944F946459B15D8C8683396BA) - Status: Failed -
Invoked on: 2007-03-30 05:00:00 - Message: The job failed. The Job
was invoked by Schedule 6 (Update SAGE Tables). The last step to run
was step 1 (Update SAGE Tables)."
Any idea why this package should work manually but not when scheduled?
Thanks
Colin
Check the following knowledge base article for information
on troubleshooting this issue:
INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/?id=269074
-Sue
On 30 Mar 2007 03:11:12 -0700, "Bobby"
<bobby2@.blueyonder.co.uk> wrote:

>Hi
>I have a very simple local package, which performs the following:
>1. Execute SQL Task
> Delete from PURCHASE_LEDGER
> Delete from SALES_LEDGER
>2. Transform Data task
> Copy everything from SAGE PURCHASE_LEDGER to SQL PURCHASE_LEDGER
> Copy everything from SAGE SALES_LEDGER to SQL SALES_LEDGER
>There is a workflow between steps 1 and 2, so that step 2 only
>executes if step 1 is successfull.
>The connection to SAGE is ODBC (which I know works fine) and to SQL it
>is OLE.
>This package works perfectly if I right click on it and select
>execute. However, if I schedule it, the first step works perfectly but
>the second step fails. I know that the first step works because the
>tables are empty. If I remove the first step and the workflow from the
>package, the transform data task still does not work when scheduled,
>but is fine when I run it manually. In the error log, it just says:
>"SQL Server Scheduled Job 'Update SAGE
>Tables' (0x3B6A429944F946459B15D8C8683396BA) - Status: Failed -
>Invoked on: 2007-03-30 05:00:00 - Message: The job failed. The Job
>was invoked by Schedule 6 (Update SAGE Tables). The last step to run
>was step 1 (Update SAGE Tables)."
>Any idea why this package should work manually but not when scheduled?
>Thanks
>Colin
|||On 30 Mar, 12:52, Sue Hoegemeier <S...@.nomail.please> wrote:
> Check the following knowledge base article for information
> on troubleshooting this issue:
> INF: How to Run a DTS Package as a Scheduled Jobhttp://support.microsoft.com/?id=269074
> -Sue
Thanks, that's the answer. I've not set up ODBC to SAGE on the server.
It's set up on my p/c, which is why it works manually, but when it's
scheduled it runs from the server and can't find the link to SAGE.
Thanks
Colin
|||> Thanks, that's the answer. I've not set up ODBC to SAGE on the server.
> It's set up on my p/c, which is why it works manually, but when it's
> scheduled it runs from the server and can't find the link to SAGE.
>
Hmmm... Not quite as simple as I thought. Anybody know how to install
the SAGE ODBC driver without installing the whole software package?
Colin
|||On 30 Mar, 13:58, "Bobby" <bob...@.blueyonder.co.uk> wrote:
> Hmmm... Not quite as simple as I thought. Anybody know how to install
> the SAGE ODBC driver without installing the whole software package?
> Colin
Ok, forget it - I've worked it out
Colin

Scheduled Job works when run manually but not when scheduled

Hi
I have a very simple local package, which performs the following:
1. Execute SQL Task
Delete from PURCHASE_LEDGER
Delete from SALES_LEDGER
2. Transform Data task
Copy everything from SAGE PURCHASE_LEDGER to SQL PURCHASE_LEDGER
Copy everything from SAGE SALES_LEDGER to SQL SALES_LEDGER
There is a workflow between steps 1 and 2, so that step 2 only
executes if step 1 is successfull.
The connection to SAGE is ODBC (which I know works fine) and to SQL it
is OLE.
This package works perfectly if I right click on it and select
execute. However, if I schedule it, the first step works perfectly but
the second step fails. I know that the first step works because the
tables are empty. If I remove the first step and the workflow from the
package, the transform data task still does not work when scheduled,
but is fine when I run it manually. In the error log, it just says:
"SQL Server Scheduled Job 'Update SAGE
Tables' (0x3B6A429944F946459B15D8C8683396BA) - Status: Failed -
Invoked on: 2007-03-30 05:00:00 - Message: The job failed. The Job
was invoked by Schedule 6 (Update SAGE Tables). The last step to run
was step 1 (Update SAGE Tables)."
Any idea why this package should work manually but not when scheduled?
Thanks
ColinHi Colin,
Are the accounts you use to 1) execut the package manually and 2) the
account that runs it via a schedule, the same account?
Without digging too deeply to me it sounds like the account that is used for
the scheduled job, isnt the same as the one where you execute it manually.
Barry
"Bobby" <bobby2@.blueyonder.co.uk> wrote in message
news:1175249472.172771.158350@.y80g2000hsf.googlegroups.com...
> Hi
> I have a very simple local package, which performs the following:
> 1. Execute SQL Task
> Delete from PURCHASE_LEDGER
> Delete from SALES_LEDGER
> 2. Transform Data task
> Copy everything from SAGE PURCHASE_LEDGER to SQL PURCHASE_LEDGER
> Copy everything from SAGE SALES_LEDGER to SQL SALES_LEDGER
> There is a workflow between steps 1 and 2, so that step 2 only
> executes if step 1 is successfull.
> The connection to SAGE is ODBC (which I know works fine) and to SQL it
> is OLE.
> This package works perfectly if I right click on it and select
> execute. However, if I schedule it, the first step works perfectly but
> the second step fails. I know that the first step works because the
> tables are empty. If I remove the first step and the workflow from the
> package, the transform data task still does not work when scheduled,
> but is fine when I run it manually. In the error log, it just says:
> "SQL Server Scheduled Job 'Update SAGE
> Tables' (0x3B6A429944F946459B15D8C8683396BA) - Status: Failed -
> Invoked on: 2007-03-30 05:00:00 - Message: The job failed. The Job
> was invoked by Schedule 6 (Update SAGE Tables). The last step to run
> was step 1 (Update SAGE Tables)."
> Any idea why this package should work manually but not when scheduled?
> Thanks
> Colin
>|||Check the following knowledge base article for information
on troubleshooting this issue:
INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/?id=269074
-Sue
On 30 Mar 2007 03:11:12 -0700, "Bobby"
<bobby2@.blueyonder.co.uk> wrote:
>Hi
>I have a very simple local package, which performs the following:
>1. Execute SQL Task
> Delete from PURCHASE_LEDGER
> Delete from SALES_LEDGER
>2. Transform Data task
> Copy everything from SAGE PURCHASE_LEDGER to SQL PURCHASE_LEDGER
> Copy everything from SAGE SALES_LEDGER to SQL SALES_LEDGER
>There is a workflow between steps 1 and 2, so that step 2 only
>executes if step 1 is successfull.
>The connection to SAGE is ODBC (which I know works fine) and to SQL it
>is OLE.
>This package works perfectly if I right click on it and select
>execute. However, if I schedule it, the first step works perfectly but
>the second step fails. I know that the first step works because the
>tables are empty. If I remove the first step and the workflow from the
>package, the transform data task still does not work when scheduled,
>but is fine when I run it manually. In the error log, it just says:
>"SQL Server Scheduled Job 'Update SAGE
>Tables' (0x3B6A429944F946459B15D8C8683396BA) - Status: Failed -
>Invoked on: 2007-03-30 05:00:00 - Message: The job failed. The Job
>was invoked by Schedule 6 (Update SAGE Tables). The last step to run
>was step 1 (Update SAGE Tables)."
>Any idea why this package should work manually but not when scheduled?
>Thanks
>Colin|||On 30 Mar, 12:52, Sue Hoegemeier <S...@.nomail.please> wrote:
> Check the following knowledge base article for information
> on troubleshooting this issue:
> INF: How to Run a DTS Package as a Scheduled Jobhttp://support.microsoft.com/?id=269074
> -Sue
Thanks, that's the answer. I've not set up ODBC to SAGE on the server.
It's set up on my p/c, which is why it works manually, but when it's
scheduled it runs from the server and can't find the link to SAGE.
Thanks
Colin|||> Thanks, that's the answer. I've not set up ODBC to SAGE on the server.
> It's set up on my p/c, which is why it works manually, but when it's
> scheduled it runs from the server and can't find the link to SAGE.
>
Hmmm... Not quite as simple as I thought. Anybody know how to install
the SAGE ODBC driver without installing the whole software package?
Colin|||On 30 Mar, 13:58, "Bobby" <bob...@.blueyonder.co.uk> wrote:
> > Thanks, that's the answer. I've not set up ODBC to SAGE on the server.
> > It's set up on my p/c, which is why it works manually, but when it's
> > scheduled it runs from the server and can't find the link to SAGE.
> Hmmm... Not quite as simple as I thought. Anybody know how to install
> the SAGE ODBC driver without installing the whole software package?
> Colin
Ok, forget it - I've worked it out
Colin

Scheduled Job works when run manually but not when scheduled

Hi
I have a very simple local package, which performs the following:
1. Execute SQL Task
Delete from PURCHASE_LEDGER
Delete from SALES_LEDGER
2. Transform Data task
Copy everything from SAGE PURCHASE_LEDGER to SQL PURCHASE_LEDGER
Copy everything from SAGE SALES_LEDGER to SQL SALES_LEDGER
There is a workflow between steps 1 and 2, so that step 2 only
executes if step 1 is successfull.
The connection to SAGE is ODBC (which I know works fine) and to SQL it
is OLE.
This package works perfectly if I right click on it and select
execute. However, if I schedule it, the first step works perfectly but
the second step fails. I know that the first step works because the
tables are empty. If I remove the first step and the workflow from the
package, the transform data task still does not work when scheduled,
but is fine when I run it manually. In the error log, it just says:
"SQL Server Scheduled Job 'Update SAGE
Tables' (0x3B6A429944F946459B15D8C8683396BA) - Status: Failed -
Invoked on: 2007-03-30 05:00:00 - Message: The job failed. The Job
was invoked by Schedule 6 (Update SAGE Tables). The last step to run
was step 1 (Update SAGE Tables)."
Any idea why this package should work manually but not when scheduled?
Thanks
ColinHi Colin,
Are the accounts you use to 1) execut the package manually and 2) the
account that runs it via a schedule, the same account?
Without digging too deeply to me it sounds like the account that is used for
the scheduled job, isnt the same as the one where you execute it manually.
Barry
"Bobby" <bobby2@.blueyonder.co.uk> wrote in message
news:1175249472.172771.158350@.y80g2000hsf.googlegroups.com...
> Hi
> I have a very simple local package, which performs the following:
> 1. Execute SQL Task
> Delete from PURCHASE_LEDGER
> Delete from SALES_LEDGER
> 2. Transform Data task
> Copy everything from SAGE PURCHASE_LEDGER to SQL PURCHASE_LEDGER
> Copy everything from SAGE SALES_LEDGER to SQL SALES_LEDGER
> There is a workflow between steps 1 and 2, so that step 2 only
> executes if step 1 is successfull.
> The connection to SAGE is ODBC (which I know works fine) and to SQL it
> is OLE.
> This package works perfectly if I right click on it and select
> execute. However, if I schedule it, the first step works perfectly but
> the second step fails. I know that the first step works because the
> tables are empty. If I remove the first step and the workflow from the
> package, the transform data task still does not work when scheduled,
> but is fine when I run it manually. In the error log, it just says:
> "SQL Server Scheduled Job 'Update SAGE
> Tables' (0x3B6A429944F946459B15D8C8683396BA) - Status: Failed -
> Invoked on: 2007-03-30 05:00:00 - Message: The job failed. The Job
> was invoked by Schedule 6 (Update SAGE Tables). The last step to run
> was step 1 (Update SAGE Tables)."
> Any idea why this package should work manually but not when scheduled?
> Thanks
> Colin
>|||Check the following knowledge base article for information
on troubleshooting this issue:
INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/?id=269074
-Sue
On 30 Mar 2007 03:11:12 -0700, "Bobby"
<bobby2@.blueyonder.co.uk> wrote:

>Hi
>I have a very simple local package, which performs the following:
>1. Execute SQL Task
> Delete from PURCHASE_LEDGER
> Delete from SALES_LEDGER
>2. Transform Data task
> Copy everything from SAGE PURCHASE_LEDGER to SQL PURCHASE_LEDGER
> Copy everything from SAGE SALES_LEDGER to SQL SALES_LEDGER
>There is a workflow between steps 1 and 2, so that step 2 only
>executes if step 1 is successfull.
>The connection to SAGE is ODBC (which I know works fine) and to SQL it
>is OLE.
>This package works perfectly if I right click on it and select
>execute. However, if I schedule it, the first step works perfectly but
>the second step fails. I know that the first step works because the
>tables are empty. If I remove the first step and the workflow from the
>package, the transform data task still does not work when scheduled,
>but is fine when I run it manually. In the error log, it just says:
>"SQL Server Scheduled Job 'Update SAGE
>Tables' (0x3B6A429944F946459B15D8C8683396BA) - Status: Failed -
>Invoked on: 2007-03-30 05:00:00 - Message: The job failed. The Job
>was invoked by Schedule 6 (Update SAGE Tables). The last step to run
>was step 1 (Update SAGE Tables)."
>Any idea why this package should work manually but not when scheduled?
>Thanks
>Colin|||On 30 Mar, 12:52, Sue Hoegemeier <S...@.nomail.please> wrote:
> Check the following knowledge base article for information
> on troubleshooting this issue:
> INF: How to Run a DTS Package as a Scheduled Jobhttp://support.microsoft.c
om/?id=269074
> -Sue
Thanks, that's the answer. I've not set up ODBC to SAGE on the server.
It's set up on my p/c, which is why it works manually, but when it's
scheduled it runs from the server and can't find the link to SAGE.
Thanks
Colin|||> Thanks, that's the answer. I've not set up ODBC to SAGE on the server.
> It's set up on my p/c, which is why it works manually, but when it's
> scheduled it runs from the server and can't find the link to SAGE.
>
Hmmm... Not quite as simple as I thought. Anybody know how to install
the SAGE ODBC driver without installing the whole software package?
Colin|||On 30 Mar, 13:58, "Bobby" <bob...@.blueyonder.co.uk> wrote:
> Hmmm... Not quite as simple as I thought. Anybody know how to install
> the SAGE ODBC driver without installing the whole software package?
> Colin
Ok, forget it - I've worked it out
Colin

Scheduled Job Sometimes Error Sometimes Not

I have a scheduled job contain 2 steps. Step 1 is execute DTS Package
using CmdExec 'DTSRun', step 2 using TSQL to execute just simple query.
This job execute recurely every day, every 6 hours.
The problem is, sometimes this job was successfull, but sometimes
failed with error as below :

...
...
Process Exit Code -1073741819. The step failed.

Please help me, what the cause of the error?
Any help would be greatly appreciated.Resant (resant_v@.yahoo.com) writes:
> I have a scheduled job contain 2 steps. Step 1 is execute DTS Package
> using CmdExec 'DTSRun', step 2 using TSQL to execute just simple query.
> This job execute recurely every day, every 6 hours.
> The problem is, sometimes this job was successfull, but sometimes
> failed with error as below :
> ...
> ...
> Process Exit Code -1073741819. The step failed.
> Please help me, what the cause of the error?
> Any help would be greatly appreciated.

In View Job History, there is a check box for "Show step details". Check
that box, and you may find some more details.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Thanks for your reply.
The error that I've post is taken after I've checked "Show step
details". OK, I'll post the error again completely :

Executed as user: XXXX\xxxx. ...un OnStart:
DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_6 DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_10 DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_10 DTSRun OnStart:
DTSStep_DTSDataPumpTask_1 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
DTSStep_DTSDataPumpTask_4 DTSRun OnStart: DTSStep_DTSDataPumpTask_4
DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
DTSStep_DTSDataPumpTask_4 DTSRun OnStart: DTSStep_DTSDataPumpTask_4
DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
DTSStep_DTSDataPumpTask_4 DTSRun OnStart: DTSStep_DTSDataPumpTask_4
DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
DTSStep_DTSDataPumpTask_4 DTSRun OnStart: DTSStep_DTS... Process
Exit Code -1073741819. The step failed.|||Resant (resant_v@.yahoo.com) writes:
> Thanks for your reply.
> The error that I've post is taken after I've checked "Show step
> details". OK, I'll post the error again completely :
> Executed as user: XXXX\xxxx. ...un OnStart:
> DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish:
> DTSStep_DTSExecuteSQLTask_6 DTSRun OnStart:
> DTSStep_DTSExecuteSQLTask_10 DTSRun OnFinish:
> DTSStep_DTSExecuteSQLTask_10 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_1 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
> DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
> DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_4 DTSRun OnStart: DTSStep_DTSDataPumpTask_4
> DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_4 DTSRun OnStart: DTSStep_DTSDataPumpTask_4
> DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_4 DTSRun OnStart: DTSStep_DTSDataPumpTask_4
> DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_4 DTSRun OnStart: DTSStep_DTS... Process
> Exit Code -1073741819. The step failed.

That's pretty anonymous. Unfortunately I don't know DTS, so I don't
have any suggestions to offer. Maybe the people in
microsoft.public.sqlserver.dts has any ideas.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Some Googling suggests that the error may be caused by a Windows bug:

http://support.microsoft.com/defaul...kb;EN-US;306497
http://groups-beta.google.com/group...lr=&sa=N&tab=wg

If you don't already have the latest servicepacks for Windows and
MSSQL, it would probably be worth installing them to see if that
resolves the issue. Since a few people seem to have seen this error in
connection with a virus infection, that would be something else to
check. If this doesn't help, then it might be worth calling Microsoft.

Simon

Scheduled job for a backup device stopped working

Hi all...
The are a number of real databases on our SQL Server 2000 and initially I
set out a number of Backup Devices to execute both FULL and DIFFERENTIAL
backups. My concern is with the FULL backups and the DIFFs are working just
fine. I scheduled a number of FULL backup jobs to execute each Sunday only
and at difference times, such as, the 1st database at 4 am, the next at 4:15
am, the next at 4:30 am etc…each Sunday only. Well I was monitoring them and
like clock work each of these real databases were over written as defined.
The job history shows that a FULL backup for these jobs was performed Nov
13th (when initially defined); the next showed the jobs run at Nov 20th, then
Nov 27th, then Dec 4th, then and Dec 11th. Each of .bak files had the
correct date stamp, but all jobs stopped? I expected, after returning from
holidays to see in the job history a backup for Dec 18, Dec 25, and Jan 1st.
But no, the last run was the 11th of Dec?
The definitions of one particular job (under the Management> SQL Server
Agent > Jobs definition) is as follows:
Name : Auscott Sunday overwrite BU
Under its property definition:
General Tab> enable is checked, Category is Database Maintenance, Owner is sa
Steps Tab> there are 2 Steps with the first having a Type: Transact-SQL
Script (TSQL), and Database: Auscott, and Command:
BACKUP DATABASE [Auscott] TO [Auscott_full_backup] WITH INIT, NOUNLOAD ,
NAME = N'Auscott Sunday overwrite BU', NOSKIP , STATS = 10, DESCRIPTION =
N'Sunday scheduled overwrite Backup of AUSCOTT DB', NOFORMAT DECLARE @.i INT
select @.i = position from msdb..backupset where database_name='Auscott'and
type!='F' and backup_set_id=(select max(backup_set_id) from msdb..backupset
where database_name='Auscott')
RESTORE VERIFYONLY FROM [Auscott_full_backup] WITH FILE = @.
Schedules Tab> is defined as Schedules Sunday AUSCOTT job, enabled,
Recurring radio button with a description of “occurs every 1 week(s) on
Sunday, at 4:15:00 am
To my way of thinking, every thing seemed to be defined correctly using
backup devices and it wrote 5 times, every Sunday, at 4:15am but stopped?
And there was no disck space issues...so I am stumped.
Does anyone have any suggestions?
Cheers….Roger Sager
Sounds like SQL Agent is stopped. Have you checked that?
Andrew J. Kelly SQL MVP
"Rog" <Rog@.discussions.microsoft.com> wrote in message
news:2421FB88-6004-4490-8B66-6F93A2E6CA7D@.microsoft.com...
> Hi all...
> The are a number of real databases on our SQL Server 2000 and initially I
> set out a number of Backup Devices to execute both FULL and DIFFERENTIAL
> backups. My concern is with the FULL backups and the DIFFs are working
> just
> fine. I scheduled a number of FULL backup jobs to execute each Sunday
> only
> and at difference times, such as, the 1st database at 4 am, the next at
> 4:15
> am, the next at 4:30 am etc.each Sunday only. Well I was monitoring them
> and
> like clock work each of these real databases were over written as defined.
> The job history shows that a FULL backup for these jobs was performed Nov
> 13th (when initially defined); the next showed the jobs run at Nov 20th,
> then
> Nov 27th, then Dec 4th, then and Dec 11th. Each of .bak files had the
> correct date stamp, but all jobs stopped? I expected, after returning
> from
> holidays to see in the job history a backup for Dec 18, Dec 25, and Jan
> 1st.
> But no, the last run was the 11th of Dec?
> The definitions of one particular job (under the Management> SQL Server
> Agent > Jobs definition) is as follows:
> Name : Auscott Sunday overwrite BU
> Under its property definition:
> General Tab> enable is checked, Category is Database Maintenance, Owner
> is sa
> Steps Tab> there are 2 Steps with the first having a Type: Transact-SQL
> Script (TSQL), and Database: Auscott, and Command:
> BACKUP DATABASE [Auscott] TO [Auscott_full_backup] WITH INIT, NOUNLOAD
> ,
> NAME = N'Auscott Sunday overwrite BU', NOSKIP , STATS = 10, DESCRIPTION
> =
> N'Sunday scheduled overwrite Backup of AUSCOTT DB', NOFORMAT DECLARE @.i
> INT
> select @.i = position from msdb..backupset where database_name='Auscott'and
> type!='F' and backup_set_id=(select max(backup_set_id) from
> msdb..backupset
> where database_name='Auscott')
> RESTORE VERIFYONLY FROM [Auscott_full_backup] WITH FILE = @.
> Schedules Tab> is defined as Schedules Sunday AUSCOTT job, enabled,
> Recurring radio button with a description of "occurs every 1 week(s) on
> Sunday, at 4:15:00 am
> To my way of thinking, every thing seemed to be defined correctly using
> backup devices and it wrote 5 times, every Sunday, at 4:15am but stopped?
> And there was no disck space issues...so I am stumped.
> Does anyone have any suggestions?
> Cheers..Roger Sager
>
|||Check to make sure the SQL Server agent is running
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Rog" <Rog@.discussions.microsoft.com> wrote in message
news:2421FB88-6004-4490-8B66-6F93A2E6CA7D@.microsoft.com...
> Hi all...
> The are a number of real databases on our SQL Server 2000 and initially I
> set out a number of Backup Devices to execute both FULL and DIFFERENTIAL
> backups. My concern is with the FULL backups and the DIFFs are working
> just
> fine. I scheduled a number of FULL backup jobs to execute each Sunday
> only
> and at difference times, such as, the 1st database at 4 am, the next at
> 4:15
> am, the next at 4:30 am etc.each Sunday only. Well I was monitoring them
> and
> like clock work each of these real databases were over written as defined.
> The job history shows that a FULL backup for these jobs was performed Nov
> 13th (when initially defined); the next showed the jobs run at Nov 20th,
> then
> Nov 27th, then Dec 4th, then and Dec 11th. Each of .bak files had the
> correct date stamp, but all jobs stopped? I expected, after returning
> from
> holidays to see in the job history a backup for Dec 18, Dec 25, and Jan
> 1st.
> But no, the last run was the 11th of Dec?
> The definitions of one particular job (under the Management> SQL Server
> Agent > Jobs definition) is as follows:
> Name : Auscott Sunday overwrite BU
> Under its property definition:
> General Tab> enable is checked, Category is Database Maintenance, Owner
> is sa
> Steps Tab> there are 2 Steps with the first having a Type: Transact-SQL
> Script (TSQL), and Database: Auscott, and Command:
> BACKUP DATABASE [Auscott] TO [Auscott_full_backup] WITH INIT, NOUNLOAD
> ,
> NAME = N'Auscott Sunday overwrite BU', NOSKIP , STATS = 10, DESCRIPTION
> =
> N'Sunday scheduled overwrite Backup of AUSCOTT DB', NOFORMAT DECLARE @.i
> INT
> select @.i = position from msdb..backupset where database_name='Auscott'and
> type!='F' and backup_set_id=(select max(backup_set_id) from
> msdb..backupset
> where database_name='Auscott')
> RESTORE VERIFYONLY FROM [Auscott_full_backup] WITH FILE = @.
> Schedules Tab> is defined as Schedules Sunday AUSCOTT job, enabled,
> Recurring radio button with a description of "occurs every 1 week(s) on
> Sunday, at 4:15:00 am
> To my way of thinking, every thing seemed to be defined correctly using
> backup devices and it wrote 5 times, every Sunday, at 4:15am but stopped?
> And there was no disck space issues...so I am stumped.
> Does anyone have any suggestions?
> Cheers..Roger Sager
>
|||No.. the SQL Server Agent is running, plus for this scheduled jobs, there is
no end-date.
Roger
"Kevin3NF" wrote:

> Check to make sure the SQL Server agent is running
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
> "Rog" <Rog@.discussions.microsoft.com> wrote in message
> news:2421FB88-6004-4490-8B66-6F93A2E6CA7D@.microsoft.com...
>
>
|||Thanks Kevin...but I check the SQL Server Agent and it is definitely started
and running. Also for these jobs, there is no end-date. I have taken
several screen shots, but don't know how to upload them.
Cheers...Roger
"Kevin3NF" wrote:

> Check to make sure the SQL Server agent is running
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
> "Rog" <Rog@.discussions.microsoft.com> wrote in message
> news:2421FB88-6004-4490-8B66-6F93A2E6CA7D@.microsoft.com...
>
>
|||Update:
Under Enterprise Mgr> Management > Sql Server Agent > Jobs...
..
I can see the last time all these "FULL Backup / Sunday only" jobs run (ie
Dec 11th) and the next run show 8th of Jan. So it will be interesting to see
on Monday morning if these have started again?
Cheers...Roger

Scheduled job for a backup device stopped working

Hi all...
The are a number of real databases on our SQL Server 2000 and initially I
set out a number of Backup Devices to execute both FULL and DIFFERENTIAL
backups. My concern is with the FULL backups and the DIFFs are working just
fine. I scheduled a number of FULL backup jobs to execute each Sunday only
and at difference times, such as, the 1st database at 4 am, the next at 4:15
am, the next at 4:30 am etcâ?¦each Sunday only. Well I was monitoring them and
like clock work each of these real databases were over written as defined.
The job history shows that a FULL backup for these jobs was performed Nov
13th (when initially defined); the next showed the jobs run at Nov 20th, then
Nov 27th, then Dec 4th, then and Dec 11th. Each of .bak files had the
correct date stamp, but all jobs stopped' I expected, after returning from
holidays to see in the job history a backup for Dec 18, Dec 25, and Jan 1st.
But no, the last run was the 11th of Dec?
The definitions of one particular job (under the Management> SQL Server
Agent > Jobs definition) is as follows:
Name : Auscott Sunday overwrite BU
Under its property definition:
General Tab> enable is checked, Category is Database Maintenance, Owner is sa
Steps Tab> there are 2 Steps with the first having a Type: Transact-SQL
Script (TSQL), and Database: Auscott, and Command:
BACKUP DATABASE [Auscott] TO [Auscott_full_backup] WITH INIT, NOUNLOAD ,
NAME = N'Auscott Sunday overwrite BU', NOSKIP , STATS = 10, DESCRIPTION = N'Sunday scheduled overwrite Backup of AUSCOTT DB', NOFORMAT DECLARE @.i INT
select @.i = position from msdb..backupset where database_name='Auscott'and
type!='F' and backup_set_id=(select max(backup_set_id) from msdb..backupset
where database_name='Auscott')
RESTORE VERIFYONLY FROM [Auscott_full_backup] WITH FILE = @.
Schedules Tab> is defined as Schedules Sunday AUSCOTT job, enabled,
Recurring radio button with a description of â'occurs every 1 week(s) on
Sunday, at 4:15:00 am
To my way of thinking, every thing seemed to be defined correctly using
backup devices and it wrote 5 times, every Sunday, at 4:15am but stopped?
And there was no disck space issues...so I am stumped.
Does anyone have any suggestions?
Cheersâ?¦.Roger SagerSounds like SQL Agent is stopped. Have you checked that?
--
Andrew J. Kelly SQL MVP
"Rog" <Rog@.discussions.microsoft.com> wrote in message
news:2421FB88-6004-4490-8B66-6F93A2E6CA7D@.microsoft.com...
> Hi all...
> The are a number of real databases on our SQL Server 2000 and initially I
> set out a number of Backup Devices to execute both FULL and DIFFERENTIAL
> backups. My concern is with the FULL backups and the DIFFs are working
> just
> fine. I scheduled a number of FULL backup jobs to execute each Sunday
> only
> and at difference times, such as, the 1st database at 4 am, the next at
> 4:15
> am, the next at 4:30 am etc.each Sunday only. Well I was monitoring them
> and
> like clock work each of these real databases were over written as defined.
> The job history shows that a FULL backup for these jobs was performed Nov
> 13th (when initially defined); the next showed the jobs run at Nov 20th,
> then
> Nov 27th, then Dec 4th, then and Dec 11th. Each of .bak files had the
> correct date stamp, but all jobs stopped' I expected, after returning
> from
> holidays to see in the job history a backup for Dec 18, Dec 25, and Jan
> 1st.
> But no, the last run was the 11th of Dec?
> The definitions of one particular job (under the Management> SQL Server
> Agent > Jobs definition) is as follows:
> Name : Auscott Sunday overwrite BU
> Under its property definition:
> General Tab> enable is checked, Category is Database Maintenance, Owner
> is sa
> Steps Tab> there are 2 Steps with the first having a Type: Transact-SQL
> Script (TSQL), and Database: Auscott, and Command:
> BACKUP DATABASE [Auscott] TO [Auscott_full_backup] WITH INIT, NOUNLOAD
> ,
> NAME = N'Auscott Sunday overwrite BU', NOSKIP , STATS = 10, DESCRIPTION
> => N'Sunday scheduled overwrite Backup of AUSCOTT DB', NOFORMAT DECLARE @.i
> INT
> select @.i = position from msdb..backupset where database_name='Auscott'and
> type!='F' and backup_set_id=(select max(backup_set_id) from
> msdb..backupset
> where database_name='Auscott')
> RESTORE VERIFYONLY FROM [Auscott_full_backup] WITH FILE = @.
> Schedules Tab> is defined as Schedules Sunday AUSCOTT job, enabled,
> Recurring radio button with a description of "occurs every 1 week(s) on
> Sunday, at 4:15:00 am
> To my way of thinking, every thing seemed to be defined correctly using
> backup devices and it wrote 5 times, every Sunday, at 4:15am but stopped?
> And there was no disck space issues...so I am stumped.
> Does anyone have any suggestions?
> Cheers..Roger Sager
>|||Check to make sure the SQL Server agent is running
--
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Rog" <Rog@.discussions.microsoft.com> wrote in message
news:2421FB88-6004-4490-8B66-6F93A2E6CA7D@.microsoft.com...
> Hi all...
> The are a number of real databases on our SQL Server 2000 and initially I
> set out a number of Backup Devices to execute both FULL and DIFFERENTIAL
> backups. My concern is with the FULL backups and the DIFFs are working
> just
> fine. I scheduled a number of FULL backup jobs to execute each Sunday
> only
> and at difference times, such as, the 1st database at 4 am, the next at
> 4:15
> am, the next at 4:30 am etc.each Sunday only. Well I was monitoring them
> and
> like clock work each of these real databases were over written as defined.
> The job history shows that a FULL backup for these jobs was performed Nov
> 13th (when initially defined); the next showed the jobs run at Nov 20th,
> then
> Nov 27th, then Dec 4th, then and Dec 11th. Each of .bak files had the
> correct date stamp, but all jobs stopped' I expected, after returning
> from
> holidays to see in the job history a backup for Dec 18, Dec 25, and Jan
> 1st.
> But no, the last run was the 11th of Dec?
> The definitions of one particular job (under the Management> SQL Server
> Agent > Jobs definition) is as follows:
> Name : Auscott Sunday overwrite BU
> Under its property definition:
> General Tab> enable is checked, Category is Database Maintenance, Owner
> is sa
> Steps Tab> there are 2 Steps with the first having a Type: Transact-SQL
> Script (TSQL), and Database: Auscott, and Command:
> BACKUP DATABASE [Auscott] TO [Auscott_full_backup] WITH INIT, NOUNLOAD
> ,
> NAME = N'Auscott Sunday overwrite BU', NOSKIP , STATS = 10, DESCRIPTION
> => N'Sunday scheduled overwrite Backup of AUSCOTT DB', NOFORMAT DECLARE @.i
> INT
> select @.i = position from msdb..backupset where database_name='Auscott'and
> type!='F' and backup_set_id=(select max(backup_set_id) from
> msdb..backupset
> where database_name='Auscott')
> RESTORE VERIFYONLY FROM [Auscott_full_backup] WITH FILE = @.
> Schedules Tab> is defined as Schedules Sunday AUSCOTT job, enabled,
> Recurring radio button with a description of "occurs every 1 week(s) on
> Sunday, at 4:15:00 am
> To my way of thinking, every thing seemed to be defined correctly using
> backup devices and it wrote 5 times, every Sunday, at 4:15am but stopped?
> And there was no disck space issues...so I am stumped.
> Does anyone have any suggestions?
> Cheers..Roger Sager
>|||No.. the SQL Server Agent is running, plus for this scheduled jobs, there is
no end-date.
Roger
"Kevin3NF" wrote:
> Check to make sure the SQL Server agent is running
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
> "Rog" <Rog@.discussions.microsoft.com> wrote in message
> news:2421FB88-6004-4490-8B66-6F93A2E6CA7D@.microsoft.com...
> > Hi all...
> >
> > The are a number of real databases on our SQL Server 2000 and initially I
> > set out a number of Backup Devices to execute both FULL and DIFFERENTIAL
> > backups. My concern is with the FULL backups and the DIFFs are working
> > just
> > fine. I scheduled a number of FULL backup jobs to execute each Sunday
> > only
> > and at difference times, such as, the 1st database at 4 am, the next at
> > 4:15
> > am, the next at 4:30 am etc.each Sunday only. Well I was monitoring them
> > and
> > like clock work each of these real databases were over written as defined.
> > The job history shows that a FULL backup for these jobs was performed Nov
> > 13th (when initially defined); the next showed the jobs run at Nov 20th,
> > then
> > Nov 27th, then Dec 4th, then and Dec 11th. Each of .bak files had the
> > correct date stamp, but all jobs stopped' I expected, after returning
> > from
> > holidays to see in the job history a backup for Dec 18, Dec 25, and Jan
> > 1st.
> > But no, the last run was the 11th of Dec?
> >
> > The definitions of one particular job (under the Management> SQL Server
> > Agent > Jobs definition) is as follows:
> >
> > Name : Auscott Sunday overwrite BU
> > Under its property definition:
> > General Tab> enable is checked, Category is Database Maintenance, Owner
> > is sa
> > Steps Tab> there are 2 Steps with the first having a Type: Transact-SQL
> > Script (TSQL), and Database: Auscott, and Command:
> > BACKUP DATABASE [Auscott] TO [Auscott_full_backup] WITH INIT, NOUNLOAD
> > ,
> > NAME = N'Auscott Sunday overwrite BU', NOSKIP , STATS = 10, DESCRIPTION
> > => > N'Sunday scheduled overwrite Backup of AUSCOTT DB', NOFORMAT DECLARE @.i
> > INT
> > select @.i = position from msdb..backupset where database_name='Auscott'and
> > type!='F' and backup_set_id=(select max(backup_set_id) from
> > msdb..backupset
> > where database_name='Auscott')
> > RESTORE VERIFYONLY FROM [Auscott_full_backup] WITH FILE = @.
> >
> > Schedules Tab> is defined as Schedules Sunday AUSCOTT job, enabled,
> > Recurring radio button with a description of "occurs every 1 week(s) on
> > Sunday, at 4:15:00 am
> >
> > To my way of thinking, every thing seemed to be defined correctly using
> > backup devices and it wrote 5 times, every Sunday, at 4:15am but stopped?
> > And there was no disck space issues...so I am stumped.
> >
> > Does anyone have any suggestions?
> > Cheers..Roger Sager
> >
>
>|||Thanks Kevin...but I check the SQL Server Agent and it is definitely started
and running. Also for these jobs, there is no end-date. I have taken
several screen shots, but don't know how to upload them.
Cheers...Roger
"Kevin3NF" wrote:
> Check to make sure the SQL Server agent is running
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
> "Rog" <Rog@.discussions.microsoft.com> wrote in message
> news:2421FB88-6004-4490-8B66-6F93A2E6CA7D@.microsoft.com...
> > Hi all...
> >
> > The are a number of real databases on our SQL Server 2000 and initially I
> > set out a number of Backup Devices to execute both FULL and DIFFERENTIAL
> > backups. My concern is with the FULL backups and the DIFFs are working
> > just
> > fine. I scheduled a number of FULL backup jobs to execute each Sunday
> > only
> > and at difference times, such as, the 1st database at 4 am, the next at
> > 4:15
> > am, the next at 4:30 am etc.each Sunday only. Well I was monitoring them
> > and
> > like clock work each of these real databases were over written as defined.
> > The job history shows that a FULL backup for these jobs was performed Nov
> > 13th (when initially defined); the next showed the jobs run at Nov 20th,
> > then
> > Nov 27th, then Dec 4th, then and Dec 11th. Each of .bak files had the
> > correct date stamp, but all jobs stopped' I expected, after returning
> > from
> > holidays to see in the job history a backup for Dec 18, Dec 25, and Jan
> > 1st.
> > But no, the last run was the 11th of Dec?
> >
> > The definitions of one particular job (under the Management> SQL Server
> > Agent > Jobs definition) is as follows:
> >
> > Name : Auscott Sunday overwrite BU
> > Under its property definition:
> > General Tab> enable is checked, Category is Database Maintenance, Owner
> > is sa
> > Steps Tab> there are 2 Steps with the first having a Type: Transact-SQL
> > Script (TSQL), and Database: Auscott, and Command:
> > BACKUP DATABASE [Auscott] TO [Auscott_full_backup] WITH INIT, NOUNLOAD
> > ,
> > NAME = N'Auscott Sunday overwrite BU', NOSKIP , STATS = 10, DESCRIPTION
> > => > N'Sunday scheduled overwrite Backup of AUSCOTT DB', NOFORMAT DECLARE @.i
> > INT
> > select @.i = position from msdb..backupset where database_name='Auscott'and
> > type!='F' and backup_set_id=(select max(backup_set_id) from
> > msdb..backupset
> > where database_name='Auscott')
> > RESTORE VERIFYONLY FROM [Auscott_full_backup] WITH FILE = @.
> >
> > Schedules Tab> is defined as Schedules Sunday AUSCOTT job, enabled,
> > Recurring radio button with a description of "occurs every 1 week(s) on
> > Sunday, at 4:15:00 am
> >
> > To my way of thinking, every thing seemed to be defined correctly using
> > backup devices and it wrote 5 times, every Sunday, at 4:15am but stopped?
> > And there was no disck space issues...so I am stumped.
> >
> > Does anyone have any suggestions?
> > Cheers..Roger Sager
> >
>
>|||Update:
Under Enterprise Mgr> Management > Sql Server Agent > Jobs...
.
I can see the last time all these "FULL Backup / Sunday only" jobs run (ie
Dec 11th) and the next run show 8th of Jan. So it will be interesting to see
on Monday morning if these have started again?
Cheers...Roger

Scheduled job for a backup device stopped working

Hi all...
The are a number of real databases on our SQL Server 2000 and initially I
set out a number of Backup Devices to execute both FULL and DIFFERENTIAL
backups. My concern is with the FULL backups and the DIFFs are working just
fine. I scheduled a number of FULL backup jobs to execute each Sunday only
and at difference times, such as, the 1st database at 4 am, the next at 4:15
am, the next at 4:30 am etc…each Sunday only. Well I was monitoring them a
nd
like clock work each of these real databases were over written as defined.
The job history shows that a FULL backup for these jobs was performed Nov
13th (when initially defined); the next showed the jobs run at Nov 20th, the
n
Nov 27th, then Dec 4th, then and Dec 11th. Each of .bak files had the
correct date stamp, but all jobs stopped' I expected, after returning from
holidays to see in the job history a backup for Dec 18, Dec 25, and Jan 1st.
But no, the last run was the 11th of Dec?
The definitions of one particular job (under the Management> SQL Server
Agent > Jobs definition) is as follows:
Name : Auscott Sunday overwrite BU
Under its property definition:
General Tab> enable is checked, Category is Database Maintenance, Owner is
sa
Steps Tab> there are 2 Steps with the first having a Type: Transact-SQL
Script (TSQL), and Database: Auscott, and Command:
BACKUP DATABASE [Auscott] TO [Auscott_full_backup] WITH INIT, NOU
NLOAD ,
NAME = N'Auscott Sunday overwrite BU', NOSKIP , STATS = 10, DESCRIPTION =
N'Sunday scheduled overwrite Backup of AUSCOTT DB', NOFORMAT DECLARE @.i INT
select @.i = position from msdb..backupset where database_name='Auscott'and
type!='F' and backup_set_id=(select max(backup_set_id) from msdb..backupset
where database_name='Auscott')
RESTORE VERIFYONLY FROM [Auscott_full_backup] WITH FILE = @.
Schedules Tab> is defined as Schedules Sunday AUSCOTT job, enabled,
Recurring radio button with a description of “occurs every 1 week(s) on
Sunday, at 4:15:00 am
To my way of thinking, every thing seemed to be defined correctly using
backup devices and it wrote 5 times, every Sunday, at 4:15am but stopped?
And there was no disck space issues...so I am stumped.
Does anyone have any suggestions?
Cheers….Roger SagerSounds like SQL Agent is stopped. Have you checked that?
Andrew J. Kelly SQL MVP
"Rog" <Rog@.discussions.microsoft.com> wrote in message
news:2421FB88-6004-4490-8B66-6F93A2E6CA7D@.microsoft.com...
> Hi all...
> The are a number of real databases on our SQL Server 2000 and initially I
> set out a number of Backup Devices to execute both FULL and DIFFERENTIAL
> backups. My concern is with the FULL backups and the DIFFs are working
> just
> fine. I scheduled a number of FULL backup jobs to execute each Sunday
> only
> and at difference times, such as, the 1st database at 4 am, the next at
> 4:15
> am, the next at 4:30 am etc.each Sunday only. Well I was monitoring them
> and
> like clock work each of these real databases were over written as defined.
> The job history shows that a FULL backup for these jobs was performed Nov
> 13th (when initially defined); the next showed the jobs run at Nov 20th,
> then
> Nov 27th, then Dec 4th, then and Dec 11th. Each of .bak files had the
> correct date stamp, but all jobs stopped' I expected, after returning
> from
> holidays to see in the job history a backup for Dec 18, Dec 25, and Jan
> 1st.
> But no, the last run was the 11th of Dec?
> The definitions of one particular job (under the Management> SQL Server
> Agent > Jobs definition) is as follows:
> Name : Auscott Sunday overwrite BU
> Under its property definition:
> General Tab> enable is checked, Category is Database Maintenance, Owner
> is sa
> Steps Tab> there are 2 Steps with the first having a Type: Transact-SQL
> Script (TSQL), and Database: Auscott, and Command:
> BACKUP DATABASE [Auscott] TO [Auscott_full_backup] WITH INIT, N
OUNLOAD
> ,
> NAME = N'Auscott Sunday overwrite BU', NOSKIP , STATS = 10, DESCRIPTION
> =
> N'Sunday scheduled overwrite Backup of AUSCOTT DB', NOFORMAT DECLARE @.i
> INT
> select @.i = position from msdb..backupset where database_name='Auscott'and
> type!='F' and backup_set_id=(select max(backup_set_id) from
> msdb..backupset
> where database_name='Auscott')
> RESTORE VERIFYONLY FROM [Auscott_full_backup] WITH FILE = @.
> Schedules Tab> is defined as Schedules Sunday AUSCOTT job, enabled,
> Recurring radio button with a description of "occurs every 1 week(s) on
> Sunday, at 4:15:00 am
> To my way of thinking, every thing seemed to be defined correctly using
> backup devices and it wrote 5 times, every Sunday, at 4:15am but stopped?
> And there was no disck space issues...so I am stumped.
> Does anyone have any suggestions?
> Cheers..Roger Sager
>|||Check to make sure the SQL Server agent is running
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Rog" <Rog@.discussions.microsoft.com> wrote in message
news:2421FB88-6004-4490-8B66-6F93A2E6CA7D@.microsoft.com...
> Hi all...
> The are a number of real databases on our SQL Server 2000 and initially I
> set out a number of Backup Devices to execute both FULL and DIFFERENTIAL
> backups. My concern is with the FULL backups and the DIFFs are working
> just
> fine. I scheduled a number of FULL backup jobs to execute each Sunday
> only
> and at difference times, such as, the 1st database at 4 am, the next at
> 4:15
> am, the next at 4:30 am etc.each Sunday only. Well I was monitoring them
> and
> like clock work each of these real databases were over written as defined.
> The job history shows that a FULL backup for these jobs was performed Nov
> 13th (when initially defined); the next showed the jobs run at Nov 20th,
> then
> Nov 27th, then Dec 4th, then and Dec 11th. Each of .bak files had the
> correct date stamp, but all jobs stopped' I expected, after returning
> from
> holidays to see in the job history a backup for Dec 18, Dec 25, and Jan
> 1st.
> But no, the last run was the 11th of Dec?
> The definitions of one particular job (under the Management> SQL Server
> Agent > Jobs definition) is as follows:
> Name : Auscott Sunday overwrite BU
> Under its property definition:
> General Tab> enable is checked, Category is Database Maintenance, Owner
> is sa
> Steps Tab> there are 2 Steps with the first having a Type: Transact-SQL
> Script (TSQL), and Database: Auscott, and Command:
> BACKUP DATABASE [Auscott] TO [Auscott_full_backup] WITH INIT, N
OUNLOAD
> ,
> NAME = N'Auscott Sunday overwrite BU', NOSKIP , STATS = 10, DESCRIPTION
> =
> N'Sunday scheduled overwrite Backup of AUSCOTT DB', NOFORMAT DECLARE @.i
> INT
> select @.i = position from msdb..backupset where database_name='Auscott'and
> type!='F' and backup_set_id=(select max(backup_set_id) from
> msdb..backupset
> where database_name='Auscott')
> RESTORE VERIFYONLY FROM [Auscott_full_backup] WITH FILE = @.
> Schedules Tab> is defined as Schedules Sunday AUSCOTT job, enabled,
> Recurring radio button with a description of "occurs every 1 week(s) on
> Sunday, at 4:15:00 am
> To my way of thinking, every thing seemed to be defined correctly using
> backup devices and it wrote 5 times, every Sunday, at 4:15am but stopped?
> And there was no disck space issues...so I am stumped.
> Does anyone have any suggestions?
> Cheers..Roger Sager
>|||No.. the SQL Server Agent is running, plus for this scheduled jobs, there is
no end-date.
Roger
"Kevin3NF" wrote:

> Check to make sure the SQL Server agent is running
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
> "Rog" <Rog@.discussions.microsoft.com> wrote in message
> news:2421FB88-6004-4490-8B66-6F93A2E6CA7D@.microsoft.com...
>
>|||Thanks Kevin...but I check the SQL Server Agent and it is definitely started
and running. Also for these jobs, there is no end-date. I have taken
several screen shots, but don't know how to upload them.
Cheers...Roger
"Kevin3NF" wrote:

> Check to make sure the SQL Server agent is running
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
> "Rog" <Rog@.discussions.microsoft.com> wrote in message
> news:2421FB88-6004-4490-8B66-6F93A2E6CA7D@.microsoft.com...
>
>|||Update:
Under Enterprise Mgr> Management > Sql Server Agent > Jobs...
.
I can see the last time all these "FULL Backup / Sunday only" jobs run (ie
Dec 11th) and the next run show 8th of Jan. So it will be interesting to see
on Monday morning if these have started again?
Cheers...Roger

Scheduled job for a backup device stopped

Hi all...
The are a number of real databases on our SQL Server 2000 and initially I
set out a number of Backup Devices to execute both FULL and DIFFERENTIAL
backups. My concern is with the FULL backups and the DIFFs are working just
fine. I scheduled a number of FULL backup jobs to execute each Sunday only
and at difference times, such as, the 1st database at 4 am, the next at 4:15
am, the next at 4:30 am etc…each Sunday only. Well I was monitoring them and
like clock work each of these real databases were over written as defined.
The job history shows that a FULL backup for these jobs was performed Nov
13th (when initially defined); the next showed the jobs run at Nov 20th, then
Nov 27th, then Dec 4th, then and Dec 11th. Each of .bak files had the
correct date stamp, but all jobs stopped? I expected, after returning from
holidays to see in the job history a backup for Dec 18, Dec 25, and Jan 1st.
But no, the last run was the 11th of Dec?
The definitions of one particular job (under the Management> SQL Server
Agent > Jobs definition) is as follows:
Name : Auscott Sunday overwrite BU
Under its property definition:
General Tab> enable is checked, Category is Database Maintenance, Owner is sa
Steps Tab> there are 2 Steps with the first having a Type: Transact-SQL
Script (TSQL), and Database: Auscott, and Command:
BACKUP DATABASE [Auscott] TO [Auscott_full_backup] WITH INIT, NOUNLOAD ,
NAME = N'Auscott Sunday overwrite BU', NOSKIP , STATS = 10, DESCRIPTION =
N'Sunday scheduled overwrite Backup of AUSCOTT DB', NOFORMAT DECLARE @.i INT
select @.i = position from msdb..backupset where database_name='Auscott'and
type!='F' and backup_set_id=(select max(backup_set_id) from msdb..backupset
where database_name='Auscott')
RESTORE VERIFYONLY FROM [Auscott_full_backup] WITH FILE = @.
Schedules Tab> is defined as Schedules Sunday AUSCOTT job, enabled,
Recurring radio button with a description of “occurs every 1 week(s) on
Sunday, at 4:15:00 am
To my way of thinking, every thing seemed to be defined correctly using
backup devices and it wrote 5 times, every Sunday, at 4:15am but stopped?
And there was no disck space issues...so I am stumped.
Does anyone have any suggestions?
Cheers….Roger Sager
PS - We are on SQL Server 2000 SP4
Sorry folks...this is a duplicate entry. Please see the other one with many
postings.
Roger Sager
|||Hi ,
Nice job but u can set a database maintinance plan which will delete ur
0ne week old backup files.
If u want to keep those backups then write a job to copy them to other
location on network and delete from the original server so sever will
not run out of disk space.
By the way on which system u are doing backup is't ur production server
if yes then u do ur back on the network derive
So in case if something happens ur still safe.
From
Doller