Scheduling a summary Stored Procedure

I had stored procedure[this read the data from couple of table and summarize
them based on the input paramter] which needs to be executed for every half
hour.I need to pass some input parameter to that proc. I am planning to
schedule this proc using below system procs
sp_add_jobschedule
sp_add_job
I need to pass some input parameter to the stored proc. I need give start
interval and end interval and some configurable values[int 1...int 5) to
filter out columns. These values can be modifiable by the end user
i.e exec my _storedpoc(startinterval, endinterval, int1, int2, int3,
int5...)
How do I pass this input params to my stored proc, when I shceduled .?
Is it the right approch to do this kind of summary procedure ?
Thanks in advance for your thoughts and comments appreciate it
prabhu
If the procedure you need to run have changing parameters' values, what
application supplies the parameters' values? That application should be the
job scheduled (within SQL server or outside).
If you have a few sets of such values that are fed to the same stored proc
to be run at different time, you can create separate jobs, each has its own
schedule and parameter values.
"prabhu" <prabahar.ignatius@.inin.com> wrote in message
news:uvHi57LnEHA.2216@.TK2MSFTNGP10.phx.gbl...
> I had stored procedure[this read the data from couple of table and
summarize
> them based on the input paramter] which needs to be executed for every
half
> hour.I need to pass some input parameter to that proc. I am planning to
> schedule this proc using below system procs
> sp_add_jobschedule
> sp_add_job
> I need to pass some input parameter to the stored proc. I need give start
> interval and end interval and some configurable values[int 1...int 5) to
> filter out columns. These values can be modifiable by the end user
> i.e exec my _storedpoc(startinterval, endinterval, int1, int2, int3,
> int5...)
> How do I pass this input params to my stored proc, when I shceduled .?
> Is it the right approch to do this kind of summary procedure ?
> Thanks in advance for your thoughts and comments appreciate it
> prabhu
>
>
|||Thank for the response Ran.
Most of the time parameters are going to have same value. But I cannot hard
code these values. Instead I need to read it from the file[ or Is there
place I can keep the values for the stored proc parameter.?] and invoke my
summary proc.
So the approach should be, the SP which is feeding the value should be
scheduled which intern call the summary procedure. Let me know if you have
any thoughts...
"Quentin Ran" <xyz@.abc.com> wrote in message
news:ezt3LrOnEHA.536@.TK2MSFTNGP11.phx.gbl...
> If the procedure you need to run have changing parameters' values, what
> application supplies the parameters' values? That application should be
the
> job scheduled (within SQL server or outside).
> If you have a few sets of such values that are fed to the same stored proc
> to be run at different time, you can create separate jobs, each has its
own[vbcol=seagreen]
> schedule and parameter values.
>
> "prabhu" <> wrote in message
> news:uvHi57LnEHA.2216@.TK2MSFTNGP10.phx.gbl...
> summarize
> half
start
>
|||Or rather, you want to set up a table which holds the parameter values.
Your job will query the table to construct the code.
"prabhu" <prabahar.ignatius@.inin.com> wrote in message
news:OQk2W3OnEHA.3324@.TK2MSFTNGP15.phx.gbl...
> Thank for the response Ran.
> Most of the time parameters are going to have same value. But I cannot
hard
> code these values. Instead I need to read it from the file[ or Is there
> place I can keep the values for the stored proc parameter.?] and invoke
my[vbcol=seagreen]
> summary proc.
> So the approach should be, the SP which is feeding the value should be
> scheduled which intern call the summary procedure. Let me know if you have
> any thoughts...
>
> "Quentin Ran" <xyz@.abc.com> wrote in message
> news:ezt3LrOnEHA.536@.TK2MSFTNGP11.phx.gbl...
> the
proc[vbcol=seagreen]
> own
to[vbcol=seagreen]
> start
to
>

Scheduling a summary Stored Procedure

I had stored procedure[this read the data from couple of table and summarize
them based on the input paramter] which needs to be executed for every half
hour.I need to pass some input parameter to that proc. I am planning to
schedule this proc using below system procs
sp_add_jobschedule
sp_add_job
I need to pass some input parameter to the stored proc. I need give start
interval and end interval and some configurable values[int 1...int 5) to
filter out columns. These values can be modifiable by the end user
i.e exec my _storedpoc(startinterval, endinterval, int1, int2, int3,
int5...)
How do I pass this input params to my stored proc, when I shceduled .?
Is it the right approch to do this kind of summary procedure ?
Thanks in advance for your thoughts and comments appreciate it
prabhuIf the procedure you need to run have changing parameters' values, what
application supplies the parameters' values? That application should be the
job scheduled (within SQL server or outside).
If you have a few sets of such values that are fed to the same stored proc
to be run at different time, you can create separate jobs, each has its own
schedule and parameter values.
"prabhu" <prabahar.ignatius@.inin.com> wrote in message
news:uvHi57LnEHA.2216@.TK2MSFTNGP10.phx.gbl...
> I had stored procedure[this read the data from couple of table and
summarize
> them based on the input paramter] which needs to be executed for every
half
> hour.I need to pass some input parameter to that proc. I am planning to
> schedule this proc using below system procs
> sp_add_jobschedule
> sp_add_job
> I need to pass some input parameter to the stored proc. I need give start
> interval and end interval and some configurable values[int 1...int 5) to
> filter out columns. These values can be modifiable by the end user
> i.e exec my _storedpoc(startinterval, endinterval, int1, int2, int3,
> int5...)
> How do I pass this input params to my stored proc, when I shceduled .?
> Is it the right approch to do this kind of summary procedure ?
> Thanks in advance for your thoughts and comments appreciate it
> prabhu
>
>|||Thank for the response Ran.
Most of the time parameters are going to have same value. But I cannot hard
code these values. Instead I need to read it from the file[ or Is there
place I can keep the values for the stored proc parameter.?] and invoke my
summary proc.
So the approach should be, the SP which is feeding the value should be
scheduled which intern call the summary procedure. Let me know if you have
any thoughts...
"Quentin Ran" <xyz@.abc.com> wrote in message
news:ezt3LrOnEHA.536@.TK2MSFTNGP11.phx.gbl...
> If the procedure you need to run have changing parameters' values, what
> application supplies the parameters' values? That application should be
the
> job scheduled (within SQL server or outside).
> If you have a few sets of such values that are fed to the same stored proc
> to be run at different time, you can create separate jobs, each has its
own
> schedule and parameter values.
>
> "prabhu" <> wrote in message
> news:uvHi57LnEHA.2216@.TK2MSFTNGP10.phx.gbl...
> > I had stored procedure[this read the data from couple of table and
> summarize
> > them based on the input paramter] which needs to be executed for every
> half
> > hour.I need to pass some input parameter to that proc. I am planning to
> > schedule this proc using below system procs
> > sp_add_jobschedule
> > sp_add_job
> > I need to pass some input parameter to the stored proc. I need give
start
> > interval and end interval and some configurable values[int 1...int 5) to
> > filter out columns. These values can be modifiable by the end user
> > i.e exec my _storedpoc(startinterval, endinterval, int1, int2, int3,
> > int5...)
> > How do I pass this input params to my stored proc, when I shceduled .?
> > Is it the right approch to do this kind of summary procedure ?
> > Thanks in advance for your thoughts and comments appreciate it
> >
> > prabhu
> >
> >
> >
> >
>|||Or rather, you want to set up a table which holds the parameter values.
Your job will query the table to construct the code.
"prabhu" <prabahar.ignatius@.inin.com> wrote in message
news:OQk2W3OnEHA.3324@.TK2MSFTNGP15.phx.gbl...
> Thank for the response Ran.
> Most of the time parameters are going to have same value. But I cannot
hard
> code these values. Instead I need to read it from the file[ or Is there
> place I can keep the values for the stored proc parameter.?] and invoke
my
> summary proc.
> So the approach should be, the SP which is feeding the value should be
> scheduled which intern call the summary procedure. Let me know if you have
> any thoughts...
>
> "Quentin Ran" <xyz@.abc.com> wrote in message
> news:ezt3LrOnEHA.536@.TK2MSFTNGP11.phx.gbl...
> > If the procedure you need to run have changing parameters' values, what
> > application supplies the parameters' values? That application should be
> the
> > job scheduled (within SQL server or outside).
> >
> > If you have a few sets of such values that are fed to the same stored
proc
> > to be run at different time, you can create separate jobs, each has its
> own
> > schedule and parameter values.
> >
> >
> >
> > "prabhu" <> wrote in message
> > news:uvHi57LnEHA.2216@.TK2MSFTNGP10.phx.gbl...
> > > I had stored procedure[this read the data from couple of table and
> > summarize
> > > them based on the input paramter] which needs to be executed for every
> > half
> > > hour.I need to pass some input parameter to that proc. I am planning
to
> > > schedule this proc using below system procs
> > > sp_add_jobschedule
> > > sp_add_job
> > > I need to pass some input parameter to the stored proc. I need give
> start
> > > interval and end interval and some configurable values[int 1...int 5)
to
> > > filter out columns. These values can be modifiable by the end user
> > > i.e exec my _storedpoc(startinterval, endinterval, int1, int2, int3,
> > > int5...)
> > > How do I pass this input params to my stored proc, when I shceduled .?
> > > Is it the right approch to do this kind of summary procedure ?
> > > Thanks in advance for your thoughts and comments appreciate it
> > >
> > > prabhu
> > >
> > >
> > >
> > >
> >
> >
>

Scheduling a query to be executed at given time in SQL Server 2005

Hi friend!

I want to schedule a query or procedure running at given time regularly eg: at 12AM daily. Please tell me how to do that in sql server 2005.

We use SQL server 2005 developer edition.

Thanks in advance.

SS2005 has a scheduller, SS Agent. Make sure it is installed and the service is up and running. You can get access to it through SSManagement Studio. BTW, this is a SSIS forum; if you have further question I will move this thread to a more appropiate forum.

Scheduled DTS always fails

I have a DTS that runs fine when executed at the package level. However, it
always fails when it runs as a scheduled job through the SQL Server Agent.
It always fails at ~93 seconds .
Anybody else experiencing this?
Here is the text for the failed scheduled DTS:
The execution of the following DTS Package succeeded:
Package Name: ORDER_HISTORY
Package Description: (null)
Package ID: {64B36A3E-7E07-46B5-BE7B-6DED729B7F70}
Package Version: {7A9368AF-3407-4708-9AFB-3CAFAD5ADB12}
Package Execution Lineage: {530DAB60-7837-406A-BDB3-37E577D79EE4}
Executed On: MSCSQL
Executed By: Administrator
Execution Started: 11/10/04 3:33:22 PM
Execution Completed: 11/10/04 3:34:55 PM
Total Execution Time: 92.984 seconds
Package Steps execution information:
Step 'Create Table [backend].[dbo].[ORDER_HISTORY] Step' succeeded
Step Execution Started: 11/10/04 3:33:22 PM
Step Execution Completed: 11/10/04 3:33:22 PM
Total Step Execution Time: 0.047 seconds
Progress count in Step: 0
Step 'Copy Data from ORDER_HISTORY to [backend].[dbo].[ORDER_HISTORY] Step'
failed
Step Error Source: Microsoft OLE DB Provider for ODBC Drivers
Step Error Description:[TOD][ODBC][Unknown]CONFIG: Expected a CONFIG call
Step Error code: 80074005
Step Error Help File:
Step Error Help Context ID:0
Step Execution Started: 11/10/04 3:33:22 PM
Step Execution Completed: 11/10/04 3:34:55 PM
Total Step Execution Time: 92.891 seconds
Progress count in Step: 72000
Step 'DTSStep_DTSExecuteSQLTask_1' was not executed
Step 'DTSStep_DTSExecuteSQLTask_2' was not executed
************************************************** **************************
****************
Here is the DTS log for the successful manually run DTS:
The execution of the following DTS Package succeeded:
Package Name: ORDER_HISTORY
Package Description: (null)
Package ID: {64B36A3E-7E07-46B5-BE7B-6DED729B7F70}
Package Version: {7A9368AF-3407-4708-9AFB-3CAFAD5ADB12}
Package Execution Lineage: {578A9ED8-A483-4D6B-A169-EB952D5AF27B}
Executed On: MSCSQL
Executed By: Administrator
Execution Started: 11/10/04 3:28:54 PM
Execution Completed: 11/10/04 3:32:35 PM
Total Execution Time: 220.906 seconds
Package Steps execution information:
Step 'Create Table [backend].[dbo].[ORDER_HISTORY] Step' succeeded
Step Execution Started: 11/10/04 3:28:54 PM
Step Execution Completed: 11/10/04 3:28:54 PM
Total Step Execution Time: 0.078 seconds
Progress count in Step: 0
Step 'Copy Data from ORDER_HISTORY to [backend].[dbo].[ORDER_HISTORY] Step'
succeeded
Step Execution Started: 11/10/04 3:28:54 PM
Step Execution Completed: 11/10/04 3:32:34 PM
Total Step Execution Time: 220.688 seconds
Progress count in Step: 118744
Step 'DTSStep_DTSExecuteSQLTask_1' succeeded
Step Execution Started: 11/10/04 3:32:34 PM
Step Execution Completed: 11/10/04 3:32:34 PM
Total Step Execution Time: 0.078 seconds
Progress count in Step: 0
Step 'DTSStep_DTSExecuteSQLTask_2' succeeded
Step Execution Started: 11/10/04 3:32:34 PM
Step Execution Completed: 11/10/04 3:32:35 PM
Total Step Execution Time: 0.016 seconds
Progress count in Step: 0
Michael,
DTS Packages run in the context of the calling process. You should check
permissions of the job, and also check to see if the connections are valid
for the job user. For example, if you run the package from Enterprise
Manager on another machine than the server, the connections may be valid,
but run from the server they may fail.
Jon Jahren
"Michael D. McGill" <mcgillmd@.hotmail.com> wrote in message
news:#4wQAV2xEHA.1076@.TK2MSFTNGP10.phx.gbl...
> I have a DTS that runs fine when executed at the package level. However,
it
> always fails when it runs as a scheduled job through the SQL Server Agent.
> It always fails at ~93 seconds .
> Anybody else experiencing this?
>
> Here is the text for the failed scheduled DTS:
> The execution of the following DTS Package succeeded:
> Package Name: ORDER_HISTORY
> Package Description: (null)
> Package ID: {64B36A3E-7E07-46B5-BE7B-6DED729B7F70}
> Package Version: {7A9368AF-3407-4708-9AFB-3CAFAD5ADB12}
> Package Execution Lineage: {530DAB60-7837-406A-BDB3-37E577D79EE4}
> Executed On: MSCSQL
> Executed By: Administrator
> Execution Started: 11/10/04 3:33:22 PM
> Execution Completed: 11/10/04 3:34:55 PM
> Total Execution Time: 92.984 seconds
> Package Steps execution information:
>
> Step 'Create Table [backend].[dbo].[ORDER_HISTORY] Step' succeeded
> Step Execution Started: 11/10/04 3:33:22 PM
> Step Execution Completed: 11/10/04 3:33:22 PM
> Total Step Execution Time: 0.047 seconds
> Progress count in Step: 0
> Step 'Copy Data from ORDER_HISTORY to [backend].[dbo].[ORDER_HISTORY]
Step'
> failed
> Step Error Source: Microsoft OLE DB Provider for ODBC Drivers
> Step Error Description:[TOD][ODBC][Unknown]CONFIG: Expected a CONFIG call
> Step Error code: 80074005
> Step Error Help File:
> Step Error Help Context ID:0
> Step Execution Started: 11/10/04 3:33:22 PM
> Step Execution Completed: 11/10/04 3:34:55 PM
> Total Step Execution Time: 92.891 seconds
> Progress count in Step: 72000
> Step 'DTSStep_DTSExecuteSQLTask_1' was not executed
> Step 'DTSStep_DTSExecuteSQLTask_2' was not executed
>
************************************************** **************************
> ****************
> Here is the DTS log for the successful manually run DTS:
> The execution of the following DTS Package succeeded:
> Package Name: ORDER_HISTORY
> Package Description: (null)
> Package ID: {64B36A3E-7E07-46B5-BE7B-6DED729B7F70}
> Package Version: {7A9368AF-3407-4708-9AFB-3CAFAD5ADB12}
> Package Execution Lineage: {578A9ED8-A483-4D6B-A169-EB952D5AF27B}
> Executed On: MSCSQL
> Executed By: Administrator
> Execution Started: 11/10/04 3:28:54 PM
> Execution Completed: 11/10/04 3:32:35 PM
> Total Execution Time: 220.906 seconds
> Package Steps execution information:
>
> Step 'Create Table [backend].[dbo].[ORDER_HISTORY] Step' succeeded
> Step Execution Started: 11/10/04 3:28:54 PM
> Step Execution Completed: 11/10/04 3:28:54 PM
> Total Step Execution Time: 0.078 seconds
> Progress count in Step: 0
> Step 'Copy Data from ORDER_HISTORY to [backend].[dbo].[ORDER_HISTORY]
Step'
> succeeded
> Step Execution Started: 11/10/04 3:28:54 PM
> Step Execution Completed: 11/10/04 3:32:34 PM
> Total Step Execution Time: 220.688 seconds
> Progress count in Step: 118744
> Step 'DTSStep_DTSExecuteSQLTask_1' succeeded
> Step Execution Started: 11/10/04 3:32:34 PM
> Step Execution Completed: 11/10/04 3:32:34 PM
> Total Step Execution Time: 0.078 seconds
> Progress count in Step: 0
> Step 'DTSStep_DTSExecuteSQLTask_2' succeeded
> Step Execution Started: 11/10/04 3:32:34 PM
> Step Execution Completed: 11/10/04 3:32:35 PM
> Total Step Execution Time: 0.016 seconds
> Progress count in Step: 0
>
|||Check the job owner, too. Jobs owned by users not in the sa role will not
run in the context of the sql server service.
How to run a dts package as a scheduled job:
http://support.microsoft.com/default...b;en-us;269074
"Jon Jahren" <jon.jahren.fightspam@.sqlkompetanse.no> wrote in message
news:%23C0Nt18xEHA.1308@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Michael,
> DTS Packages run in the context of the calling process. You should check
> permissions of the job, and also check to see if the connections are valid
> for the job user. For example, if you run the package from Enterprise
> Manager on another machine than the server, the connections may be valid,
> but run from the server they may fail.
> Jon Jahren
> "Michael D. McGill" <mcgillmd@.hotmail.com> wrote in message
> news:#4wQAV2xEHA.1076@.TK2MSFTNGP10.phx.gbl...
> it
Agent.[vbcol=seagreen]
> Step'
call
>
************************************************** **************************
> Step'
>

Scheduled DTS always fails

I have a DTS that runs fine when executed at the package level. However, it
always fails when it runs as a scheduled job through the SQL Server Agent.
It always fails at ~93 seconds .
Anybody else experiencing this?
Here is the text for the failed scheduled DTS:
The execution of the following DTS Package succeeded:
Package Name: ORDER_HISTORY
Package Description: (null)
Package ID: {64B36A3E-7E07-46B5-BE7B-6DED729B7F70}
Package Version: {7A9368AF-3407-4708-9AFB-3CAFAD5ADB12}
Package Execution Lineage: {530DAB60-7837-406A-BDB3-37E577D79EE4}
Executed On: MSCSQL
Executed By: Administrator
Execution Started: 11/10/04 3:33:22 PM
Execution Completed: 11/10/04 3:34:55 PM
Total Execution Time: 92.984 seconds
Package Steps execution information:
Step 'Create Table [backend].[dbo].[ORDER_HISTORY] Step' succeeded
Step Execution Started: 11/10/04 3:33:22 PM
Step Execution Completed: 11/10/04 3:33:22 PM
Total Step Execution Time: 0.047 seconds
Progress count in Step: 0
Step 'Copy Data from ORDER_HISTORY to [backend].[dbo].[ORDER_HISTORY] Step'
failed
Step Error Source: Microsoft OLE DB Provider for ODBC Drivers
Step Error Description:[TOD][ODBC][Unknown]CONFIG: Expected a CONFIG call
Step Error code: 80074005
Step Error Help File:
Step Error Help Context ID:0
Step Execution Started: 11/10/04 3:33:22 PM
Step Execution Completed: 11/10/04 3:34:55 PM
Total Step Execution Time: 92.891 seconds
Progress count in Step: 72000
Step 'DTSStep_DTSExecuteSQLTask_1' was not executed
Step 'DTSStep_DTSExecuteSQLTask_2' was not executed
************************************************** **************************
****************
Here is the DTS log for the successful manually run DTS:
The execution of the following DTS Package succeeded:
Package Name: ORDER_HISTORY
Package Description: (null)
Package ID: {64B36A3E-7E07-46B5-BE7B-6DED729B7F70}
Package Version: {7A9368AF-3407-4708-9AFB-3CAFAD5ADB12}
Package Execution Lineage: {578A9ED8-A483-4D6B-A169-EB952D5AF27B}
Executed On: MSCSQL
Executed By: Administrator
Execution Started: 11/10/04 3:28:54 PM
Execution Completed: 11/10/04 3:32:35 PM
Total Execution Time: 220.906 seconds
Package Steps execution information:
Step 'Create Table [backend].[dbo].[ORDER_HISTORY] Step' succeeded
Step Execution Started: 11/10/04 3:28:54 PM
Step Execution Completed: 11/10/04 3:28:54 PM
Total Step Execution Time: 0.078 seconds
Progress count in Step: 0
Step 'Copy Data from ORDER_HISTORY to [backend].[dbo].[ORDER_HISTORY] Step'
succeeded
Step Execution Started: 11/10/04 3:28:54 PM
Step Execution Completed: 11/10/04 3:32:34 PM
Total Step Execution Time: 220.688 seconds
Progress count in Step: 118744
Step 'DTSStep_DTSExecuteSQLTask_1' succeeded
Step Execution Started: 11/10/04 3:32:34 PM
Step Execution Completed: 11/10/04 3:32:34 PM
Total Step Execution Time: 0.078 seconds
Progress count in Step: 0
Step 'DTSStep_DTSExecuteSQLTask_2' succeeded
Step Execution Started: 11/10/04 3:32:34 PM
Step Execution Completed: 11/10/04 3:32:35 PM
Total Step Execution Time: 0.016 seconds
Progress count in Step: 0
Michael,
DTS Packages run in the context of the calling process. You should check
permissions of the job, and also check to see if the connections are valid
for the job user. For example, if you run the package from Enterprise
Manager on another machine than the server, the connections may be valid,
but run from the server they may fail.
Jon Jahren
"Michael D. McGill" <mcgillmd@.hotmail.com> wrote in message
news:#4wQAV2xEHA.1076@.TK2MSFTNGP10.phx.gbl...
> I have a DTS that runs fine when executed at the package level. However,
it
> always fails when it runs as a scheduled job through the SQL Server Agent.
> It always fails at ~93 seconds .
> Anybody else experiencing this?
>
> Here is the text for the failed scheduled DTS:
> The execution of the following DTS Package succeeded:
> Package Name: ORDER_HISTORY
> Package Description: (null)
> Package ID: {64B36A3E-7E07-46B5-BE7B-6DED729B7F70}
> Package Version: {7A9368AF-3407-4708-9AFB-3CAFAD5ADB12}
> Package Execution Lineage: {530DAB60-7837-406A-BDB3-37E577D79EE4}
> Executed On: MSCSQL
> Executed By: Administrator
> Execution Started: 11/10/04 3:33:22 PM
> Execution Completed: 11/10/04 3:34:55 PM
> Total Execution Time: 92.984 seconds
> Package Steps execution information:
>
> Step 'Create Table [backend].[dbo].[ORDER_HISTORY] Step' succeeded
> Step Execution Started: 11/10/04 3:33:22 PM
> Step Execution Completed: 11/10/04 3:33:22 PM
> Total Step Execution Time: 0.047 seconds
> Progress count in Step: 0
> Step 'Copy Data from ORDER_HISTORY to [backend].[dbo].[ORDER_HISTORY]
Step'
> failed
> Step Error Source: Microsoft OLE DB Provider for ODBC Drivers
> Step Error Description:[TOD][ODBC][Unknown]CONFIG: Expected a CONFIG call
> Step Error code: 80074005
> Step Error Help File:
> Step Error Help Context ID:0
> Step Execution Started: 11/10/04 3:33:22 PM
> Step Execution Completed: 11/10/04 3:34:55 PM
> Total Step Execution Time: 92.891 seconds
> Progress count in Step: 72000
> Step 'DTSStep_DTSExecuteSQLTask_1' was not executed
> Step 'DTSStep_DTSExecuteSQLTask_2' was not executed
>
************************************************** **************************
> ****************
> Here is the DTS log for the successful manually run DTS:
> The execution of the following DTS Package succeeded:
> Package Name: ORDER_HISTORY
> Package Description: (null)
> Package ID: {64B36A3E-7E07-46B5-BE7B-6DED729B7F70}
> Package Version: {7A9368AF-3407-4708-9AFB-3CAFAD5ADB12}
> Package Execution Lineage: {578A9ED8-A483-4D6B-A169-EB952D5AF27B}
> Executed On: MSCSQL
> Executed By: Administrator
> Execution Started: 11/10/04 3:28:54 PM
> Execution Completed: 11/10/04 3:32:35 PM
> Total Execution Time: 220.906 seconds
> Package Steps execution information:
>
> Step 'Create Table [backend].[dbo].[ORDER_HISTORY] Step' succeeded
> Step Execution Started: 11/10/04 3:28:54 PM
> Step Execution Completed: 11/10/04 3:28:54 PM
> Total Step Execution Time: 0.078 seconds
> Progress count in Step: 0
> Step 'Copy Data from ORDER_HISTORY to [backend].[dbo].[ORDER_HISTORY]
Step'
> succeeded
> Step Execution Started: 11/10/04 3:28:54 PM
> Step Execution Completed: 11/10/04 3:32:34 PM
> Total Step Execution Time: 220.688 seconds
> Progress count in Step: 118744
> Step 'DTSStep_DTSExecuteSQLTask_1' succeeded
> Step Execution Started: 11/10/04 3:32:34 PM
> Step Execution Completed: 11/10/04 3:32:34 PM
> Total Step Execution Time: 0.078 seconds
> Progress count in Step: 0
> Step 'DTSStep_DTSExecuteSQLTask_2' succeeded
> Step Execution Started: 11/10/04 3:32:34 PM
> Step Execution Completed: 11/10/04 3:32:35 PM
> Total Step Execution Time: 0.016 seconds
> Progress count in Step: 0
>
|||Check the job owner, too. Jobs owned by users not in the sa role will not
run in the context of the sql server service.
How to run a dts package as a scheduled job:
http://support.microsoft.com/default...b;en-us;269074
"Jon Jahren" <jon.jahren.fightspam@.sqlkompetanse.no> wrote in message
news:%23C0Nt18xEHA.1308@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Michael,
> DTS Packages run in the context of the calling process. You should check
> permissions of the job, and also check to see if the connections are valid
> for the job user. For example, if you run the package from Enterprise
> Manager on another machine than the server, the connections may be valid,
> but run from the server they may fail.
> Jon Jahren
> "Michael D. McGill" <mcgillmd@.hotmail.com> wrote in message
> news:#4wQAV2xEHA.1076@.TK2MSFTNGP10.phx.gbl...
> it
Agent.[vbcol=seagreen]
> Step'
call
>
************************************************** **************************
> Step'
>

Scheduled DTS always fails

I have a DTS that runs fine when executed at the package level. However, it
always fails when it runs as a scheduled job through the SQL Server Agent.
It always fails at ~93 seconds .
Anybody else experiencing this?
Here is the text for the failed scheduled DTS:
The execution of the following DTS Package succeeded:
Package Name: ORDER_HISTORY
Package Description: (null)
Package ID: {64B36A3E-7E07-46B5-BE7B-6DED729B7F70}
Package Version: {7A9368AF-3407-4708-9AFB-3CAFAD5ADB12}
Package Execution Lineage: {530DAB60-7837-406A-BDB3-37E577D79EE4}
Executed On: MSCSQL
Executed By: Administrator
Execution Started: 11/10/04 3:33:22 PM
Execution Completed: 11/10/04 3:34:55 PM
Total Execution Time: 92.984 seconds
Package Steps execution information:
Step 'Create Table [backend].[dbo].[ORDER_HISTORY] Step' succeeded
Step Execution Started: 11/10/04 3:33:22 PM
Step Execution Completed: 11/10/04 3:33:22 PM
Total Step Execution Time: 0.047 seconds
Progress count in Step: 0
Step 'Copy Data from ORDER_HISTORY to [backend].[dbo].[ORDER_HISTORY] Step'
failed
Step Error Source: Microsoft OLE DB Provider for ODBC Drivers
Step Error Description:[TOD][ODBC][Unknown]CONFIG: Expected a CONFIG call
Step Error code: 80074005
Step Error Help File:
Step Error Help Context ID:0
Step Execution Started: 11/10/04 3:33:22 PM
Step Execution Completed: 11/10/04 3:34:55 PM
Total Step Execution Time: 92.891 seconds
Progress count in Step: 72000
Step 'DTSStep_DTSExecuteSQLTask_1' was not executed
Step 'DTSStep_DTSExecuteSQLTask_2' was not executed
****************************************************************************
****************
Here is the DTS log for the successful manually run DTS:
The execution of the following DTS Package succeeded:
Package Name: ORDER_HISTORY
Package Description: (null)
Package ID: {64B36A3E-7E07-46B5-BE7B-6DED729B7F70}
Package Version: {7A9368AF-3407-4708-9AFB-3CAFAD5ADB12}
Package Execution Lineage: {578A9ED8-A483-4D6B-A169-EB952D5AF27B}
Executed On: MSCSQL
Executed By: Administrator
Execution Started: 11/10/04 3:28:54 PM
Execution Completed: 11/10/04 3:32:35 PM
Total Execution Time: 220.906 seconds
Package Steps execution information:
Step 'Create Table [backend].[dbo].[ORDER_HISTORY] Step' succeeded
Step Execution Started: 11/10/04 3:28:54 PM
Step Execution Completed: 11/10/04 3:28:54 PM
Total Step Execution Time: 0.078 seconds
Progress count in Step: 0
Step 'Copy Data from ORDER_HISTORY to [backend].[dbo].[ORDER_HISTORY] Step'
succeeded
Step Execution Started: 11/10/04 3:28:54 PM
Step Execution Completed: 11/10/04 3:32:34 PM
Total Step Execution Time: 220.688 seconds
Progress count in Step: 118744
Step 'DTSStep_DTSExecuteSQLTask_1' succeeded
Step Execution Started: 11/10/04 3:32:34 PM
Step Execution Completed: 11/10/04 3:32:34 PM
Total Step Execution Time: 0.078 seconds
Progress count in Step: 0
Step 'DTSStep_DTSExecuteSQLTask_2' succeeded
Step Execution Started: 11/10/04 3:32:34 PM
Step Execution Completed: 11/10/04 3:32:35 PM
Total Step Execution Time: 0.016 seconds
Progress count in Step: 0Michael,
DTS Packages run in the context of the calling process. You should check
permissions of the job, and also check to see if the connections are valid
for the job user. For example, if you run the package from Enterprise
Manager on another machine than the server, the connections may be valid,
but run from the server they may fail.
Jon Jahren
"Michael D. McGill" <mcgillmd@.hotmail.com> wrote in message
news:#4wQAV2xEHA.1076@.TK2MSFTNGP10.phx.gbl...
> I have a DTS that runs fine when executed at the package level. However,
it
> always fails when it runs as a scheduled job through the SQL Server Agent.
> It always fails at ~93 seconds .
> Anybody else experiencing this?
>
> Here is the text for the failed scheduled DTS:
> The execution of the following DTS Package succeeded:
> Package Name: ORDER_HISTORY
> Package Description: (null)
> Package ID: {64B36A3E-7E07-46B5-BE7B-6DED729B7F70}
> Package Version: {7A9368AF-3407-4708-9AFB-3CAFAD5ADB12}
> Package Execution Lineage: {530DAB60-7837-406A-BDB3-37E577D79EE4}
> Executed On: MSCSQL
> Executed By: Administrator
> Execution Started: 11/10/04 3:33:22 PM
> Execution Completed: 11/10/04 3:34:55 PM
> Total Execution Time: 92.984 seconds
> Package Steps execution information:
>
> Step 'Create Table [backend].[dbo].[ORDER_HISTORY] Step' succeeded
> Step Execution Started: 11/10/04 3:33:22 PM
> Step Execution Completed: 11/10/04 3:33:22 PM
> Total Step Execution Time: 0.047 seconds
> Progress count in Step: 0
> Step 'Copy Data from ORDER_HISTORY to [backend].[dbo].[ORDER_HISTORY]
Step'
> failed
> Step Error Source: Microsoft OLE DB Provider for ODBC Drivers
> Step Error Description:[TOD][ODBC][Unknown]CONFIG: Expected a CONFIG call
> Step Error code: 80074005
> Step Error Help File:
> Step Error Help Context ID:0
> Step Execution Started: 11/10/04 3:33:22 PM
> Step Execution Completed: 11/10/04 3:34:55 PM
> Total Step Execution Time: 92.891 seconds
> Progress count in Step: 72000
> Step 'DTSStep_DTSExecuteSQLTask_1' was not executed
> Step 'DTSStep_DTSExecuteSQLTask_2' was not executed
>
****************************************************************************
> ****************
> Here is the DTS log for the successful manually run DTS:
> The execution of the following DTS Package succeeded:
> Package Name: ORDER_HISTORY
> Package Description: (null)
> Package ID: {64B36A3E-7E07-46B5-BE7B-6DED729B7F70}
> Package Version: {7A9368AF-3407-4708-9AFB-3CAFAD5ADB12}
> Package Execution Lineage: {578A9ED8-A483-4D6B-A169-EB952D5AF27B}
> Executed On: MSCSQL
> Executed By: Administrator
> Execution Started: 11/10/04 3:28:54 PM
> Execution Completed: 11/10/04 3:32:35 PM
> Total Execution Time: 220.906 seconds
> Package Steps execution information:
>
> Step 'Create Table [backend].[dbo].[ORDER_HISTORY] Step' succeeded
> Step Execution Started: 11/10/04 3:28:54 PM
> Step Execution Completed: 11/10/04 3:28:54 PM
> Total Step Execution Time: 0.078 seconds
> Progress count in Step: 0
> Step 'Copy Data from ORDER_HISTORY to [backend].[dbo].[ORDER_HISTORY]
Step'
> succeeded
> Step Execution Started: 11/10/04 3:28:54 PM
> Step Execution Completed: 11/10/04 3:32:34 PM
> Total Step Execution Time: 220.688 seconds
> Progress count in Step: 118744
> Step 'DTSStep_DTSExecuteSQLTask_1' succeeded
> Step Execution Started: 11/10/04 3:32:34 PM
> Step Execution Completed: 11/10/04 3:32:34 PM
> Total Step Execution Time: 0.078 seconds
> Progress count in Step: 0
> Step 'DTSStep_DTSExecuteSQLTask_2' succeeded
> Step Execution Started: 11/10/04 3:32:34 PM
> Step Execution Completed: 11/10/04 3:32:35 PM
> Total Step Execution Time: 0.016 seconds
> Progress count in Step: 0
>|||Check the job owner, too. Jobs owned by users not in the sa role will not
run in the context of the sql server service.
How to run a dts package as a scheduled job:
http://support.microsoft.com/default.aspx?scid=kb;en-us;269074
"Jon Jahren" <jon.jahren.fightspam@.sqlkompetanse.no> wrote in message
news:%23C0Nt18xEHA.1308@.TK2MSFTNGP09.phx.gbl...
> Michael,
> DTS Packages run in the context of the calling process. You should check
> permissions of the job, and also check to see if the connections are valid
> for the job user. For example, if you run the package from Enterprise
> Manager on another machine than the server, the connections may be valid,
> but run from the server they may fail.
> Jon Jahren
> "Michael D. McGill" <mcgillmd@.hotmail.com> wrote in message
> news:#4wQAV2xEHA.1076@.TK2MSFTNGP10.phx.gbl...
> > I have a DTS that runs fine when executed at the package level. However,
> it
> > always fails when it runs as a scheduled job through the SQL Server
Agent.
> >
> > It always fails at ~93 seconds .
> >
> > Anybody else experiencing this?
> >
> >
> > Here is the text for the failed scheduled DTS:
> >
> > The execution of the following DTS Package succeeded:
> >
> > Package Name: ORDER_HISTORY
> > Package Description: (null)
> > Package ID: {64B36A3E-7E07-46B5-BE7B-6DED729B7F70}
> > Package Version: {7A9368AF-3407-4708-9AFB-3CAFAD5ADB12}
> > Package Execution Lineage: {530DAB60-7837-406A-BDB3-37E577D79EE4}
> > Executed On: MSCSQL
> > Executed By: Administrator
> > Execution Started: 11/10/04 3:33:22 PM
> > Execution Completed: 11/10/04 3:34:55 PM
> > Total Execution Time: 92.984 seconds
> >
> > Package Steps execution information:
> >
> >
> > Step 'Create Table [backend].[dbo].[ORDER_HISTORY] Step' succeeded
> > Step Execution Started: 11/10/04 3:33:22 PM
> > Step Execution Completed: 11/10/04 3:33:22 PM
> > Total Step Execution Time: 0.047 seconds
> > Progress count in Step: 0
> >
> > Step 'Copy Data from ORDER_HISTORY to [backend].[dbo].[ORDER_HISTORY]
> Step'
> > failed
> >
> > Step Error Source: Microsoft OLE DB Provider for ODBC Drivers
> > Step Error Description:[TOD][ODBC][Unknown]CONFIG: Expected a CONFIG
call
> > Step Error code: 80074005
> > Step Error Help File:
> > Step Error Help Context ID:0
> >
> > Step Execution Started: 11/10/04 3:33:22 PM
> > Step Execution Completed: 11/10/04 3:34:55 PM
> > Total Step Execution Time: 92.891 seconds
> > Progress count in Step: 72000
> >
> > Step 'DTSStep_DTSExecuteSQLTask_1' was not executed
> >
> > Step 'DTSStep_DTSExecuteSQLTask_2' was not executed
> >
>
****************************************************************************
> > ****************
> >
> > Here is the DTS log for the successful manually run DTS:
> >
> > The execution of the following DTS Package succeeded:
> >
> > Package Name: ORDER_HISTORY
> > Package Description: (null)
> > Package ID: {64B36A3E-7E07-46B5-BE7B-6DED729B7F70}
> > Package Version: {7A9368AF-3407-4708-9AFB-3CAFAD5ADB12}
> > Package Execution Lineage: {578A9ED8-A483-4D6B-A169-EB952D5AF27B}
> > Executed On: MSCSQL
> > Executed By: Administrator
> > Execution Started: 11/10/04 3:28:54 PM
> > Execution Completed: 11/10/04 3:32:35 PM
> > Total Execution Time: 220.906 seconds
> >
> > Package Steps execution information:
> >
> >
> > Step 'Create Table [backend].[dbo].[ORDER_HISTORY] Step' succeeded
> > Step Execution Started: 11/10/04 3:28:54 PM
> > Step Execution Completed: 11/10/04 3:28:54 PM
> > Total Step Execution Time: 0.078 seconds
> > Progress count in Step: 0
> >
> > Step 'Copy Data from ORDER_HISTORY to [backend].[dbo].[ORDER_HISTORY]
> Step'
> > succeeded
> > Step Execution Started: 11/10/04 3:28:54 PM
> > Step Execution Completed: 11/10/04 3:32:34 PM
> > Total Step Execution Time: 220.688 seconds
> > Progress count in Step: 118744
> >
> > Step 'DTSStep_DTSExecuteSQLTask_1' succeeded
> > Step Execution Started: 11/10/04 3:32:34 PM
> > Step Execution Completed: 11/10/04 3:32:34 PM
> > Total Step Execution Time: 0.078 seconds
> > Progress count in Step: 0
> >
> > Step 'DTSStep_DTSExecuteSQLTask_2' succeeded
> > Step Execution Started: 11/10/04 3:32:34 PM
> > Step Execution Completed: 11/10/04 3:32:35 PM
> > Total Step Execution Time: 0.016 seconds
> > Progress count in Step: 0
> >
> >
>

Scheduled DTS always fails

I have a DTS that runs fine when executed at the package level. However, it
always fails when it runs as a scheduled job through the SQL Server Agent.
It always fails at ~93 seconds .
Anybody else experiencing this?
Here is the text for the failed scheduled DTS:
The execution of the following DTS Package succeeded:
Package Name: ORDER_HISTORY
Package Description: (null)
Package ID: {64B36A3E-7E07-46B5-BE7B-6DED729B7F70}
Package Version: {7A9368AF-3407-4708-9AFB-3CAFAD5ADB12}
Package Execution Lineage: {530DAB60-7837-406A-BDB3-37E577D79EE4}
Executed On: MSCSQL
Executed By: Administrator
Execution Started: 11/10/04 3:33:22 PM
Execution Completed: 11/10/04 3:34:55 PM
Total Execution Time: 92.984 seconds
Package Steps execution information:
Step 'Create Table [backend].[dbo].[ORDER_HISTORY] Step' succeed
ed
Step Execution Started: 11/10/04 3:33:22 PM
Step Execution Completed: 11/10/04 3:33:22 PM
Total Step Execution Time: 0.047 seconds
Progress count in Step: 0
Step 'Copy Data from ORDER_HISTORY to [backend].[dbo].[ORDER_HIS
TORY] Step'
failed
Step Error Source: Microsoft OLE DB Provider for ODBC Drivers
Step Error Description:[TOD][ODBC][Unknown]CONFIG: Expected a CO
NFIG call
Step Error code: 80074005
Step Error Help File:
Step Error Help Context ID:0
Step Execution Started: 11/10/04 3:33:22 PM
Step Execution Completed: 11/10/04 3:34:55 PM
Total Step Execution Time: 92.891 seconds
Progress count in Step: 72000
Step 'DTSStep_DTSExecuteSQLTask_1' was not executed
Step 'DTSStep_DTSExecuteSQLTask_2' was not executed
****************************************
************************************
****************
Here is the DTS log for the successful manually run DTS:
The execution of the following DTS Package succeeded:
Package Name: ORDER_HISTORY
Package Description: (null)
Package ID: {64B36A3E-7E07-46B5-BE7B-6DED729B7F70}
Package Version: {7A9368AF-3407-4708-9AFB-3CAFAD5ADB12}
Package Execution Lineage: {578A9ED8-A483-4D6B-A169-EB952D5AF27B}
Executed On: MSCSQL
Executed By: Administrator
Execution Started: 11/10/04 3:28:54 PM
Execution Completed: 11/10/04 3:32:35 PM
Total Execution Time: 220.906 seconds
Package Steps execution information:
Step 'Create Table [backend].[dbo].[ORDER_HISTORY] Step' succeed
ed
Step Execution Started: 11/10/04 3:28:54 PM
Step Execution Completed: 11/10/04 3:28:54 PM
Total Step Execution Time: 0.078 seconds
Progress count in Step: 0
Step 'Copy Data from ORDER_HISTORY to [backend].[dbo].[ORDER_HIS
TORY] Step'
succeeded
Step Execution Started: 11/10/04 3:28:54 PM
Step Execution Completed: 11/10/04 3:32:34 PM
Total Step Execution Time: 220.688 seconds
Progress count in Step: 118744
Step 'DTSStep_DTSExecuteSQLTask_1' succeeded
Step Execution Started: 11/10/04 3:32:34 PM
Step Execution Completed: 11/10/04 3:32:34 PM
Total Step Execution Time: 0.078 seconds
Progress count in Step: 0
Step 'DTSStep_DTSExecuteSQLTask_2' succeeded
Step Execution Started: 11/10/04 3:32:34 PM
Step Execution Completed: 11/10/04 3:32:35 PM
Total Step Execution Time: 0.016 seconds
Progress count in Step: 0Michael,
DTS Packages run in the context of the calling process. You should check
permissions of the job, and also check to see if the connections are valid
for the job user. For example, if you run the package from Enterprise
Manager on another machine than the server, the connections may be valid,
but run from the server they may fail.
Jon Jahren
"Michael D. McGill" <mcgillmd@.hotmail.com> wrote in message
news:#4wQAV2xEHA.1076@.TK2MSFTNGP10.phx.gbl...
> I have a DTS that runs fine when executed at the package level. However,
it
> always fails when it runs as a scheduled job through the SQL Server Agent.
> It always fails at ~93 seconds .
> Anybody else experiencing this?
>
> Here is the text for the failed scheduled DTS:
> The execution of the following DTS Package succeeded:
> Package Name: ORDER_HISTORY
> Package Description: (null)
> Package ID: {64B36A3E-7E07-46B5-BE7B-6DED729B7F70}
> Package Version: {7A9368AF-3407-4708-9AFB-3CAFAD5ADB12}
> Package Execution Lineage: {530DAB60-7837-406A-BDB3-37E577D79EE4}
> Executed On: MSCSQL
> Executed By: Administrator
> Execution Started: 11/10/04 3:33:22 PM
> Execution Completed: 11/10/04 3:34:55 PM
> Total Execution Time: 92.984 seconds
> Package Steps execution information:
>
> Step 'Create Table [backend].[dbo].[ORDER_HISTORY] Step' succe
eded
> Step Execution Started: 11/10/04 3:33:22 PM
> Step Execution Completed: 11/10/04 3:33:22 PM
> Total Step Execution Time: 0.047 seconds
> Progress count in Step: 0
> Step 'Copy Data from ORDER_HISTORY to [backend].[dbo].[ORDER_HISTORY][
/vbcol]
Step'[vbcol=seagreen]
> failed
> Step Error Source: Microsoft OLE DB Provider for ODBC Drivers
> Step Error Description:[TOD][ODBC][Unknown]CONFIG: Expected a
CONFIG call
> Step Error code: 80074005
> Step Error Help File:
> Step Error Help Context ID:0
> Step Execution Started: 11/10/04 3:33:22 PM
> Step Execution Completed: 11/10/04 3:34:55 PM
> Total Step Execution Time: 92.891 seconds
> Progress count in Step: 72000
> Step 'DTSStep_DTSExecuteSQLTask_1' was not executed
> Step 'DTSStep_DTSExecuteSQLTask_2' was not executed
>
****************************************
************************************[vbc
ol=seagreen]
> ****************
> Here is the DTS log for the successful manually run DTS:
> The execution of the following DTS Package succeeded:
> Package Name: ORDER_HISTORY
> Package Description: (null)
> Package ID: {64B36A3E-7E07-46B5-BE7B-6DED729B7F70}
> Package Version: {7A9368AF-3407-4708-9AFB-3CAFAD5ADB12}
> Package Execution Lineage: {578A9ED8-A483-4D6B-A169-EB952D5AF27B}
> Executed On: MSCSQL
> Executed By: Administrator
> Execution Started: 11/10/04 3:28:54 PM
> Execution Completed: 11/10/04 3:32:35 PM
> Total Execution Time: 220.906 seconds
> Package Steps execution information:
>
> Step 'Create Table [backend].[dbo].[ORDER_HISTORY] Step' succe
eded
> Step Execution Started: 11/10/04 3:28:54 PM
> Step Execution Completed: 11/10/04 3:28:54 PM
> Total Step Execution Time: 0.078 seconds
> Progress count in Step: 0
> Step 'Copy Data from ORDER_HISTORY to [backend].[dbo].[ORDER_HISTORY][
/vbcol]
Step'
> succeeded
> Step Execution Started: 11/10/04 3:28:54 PM
> Step Execution Completed: 11/10/04 3:32:34 PM
> Total Step Execution Time: 220.688 seconds
> Progress count in Step: 118744
> Step 'DTSStep_DTSExecuteSQLTask_1' succeeded
> Step Execution Started: 11/10/04 3:32:34 PM
> Step Execution Completed: 11/10/04 3:32:34 PM
> Total Step Execution Time: 0.078 seconds
> Progress count in Step: 0
> Step 'DTSStep_DTSExecuteSQLTask_2' succeeded
> Step Execution Started: 11/10/04 3:32:34 PM
> Step Execution Completed: 11/10/04 3:32:35 PM
> Total Step Execution Time: 0.016 seconds
> Progress count in Step: 0
>|||Check the job owner, too. Jobs owned by users not in the sa role will not
run in the context of the sql server service.
How to run a dts package as a scheduled job:
http://support.microsoft.com/defaul...kb;en-us;269074
"Jon Jahren" <jon.jahren.fightspam@.sqlkompetanse.no> wrote in message
news:%23C0Nt18xEHA.1308@.TK2MSFTNGP09.phx.gbl...
> Michael,
> DTS Packages run in the context of the calling process. You should check
> permissions of the job, and also check to see if the connections are valid
> for the job user. For example, if you run the package from Enterprise
> Manager on another machine than the server, the connections may be valid,
> but run from the server they may fail.
> Jon Jahren
> "Michael D. McGill" <mcgillmd@.hotmail.com> wrote in message
> news:#4wQAV2xEHA.1076@.TK2MSFTNGP10.phx.gbl...
> it
Agent.
> Step'
call[vbcol=seagreen]
>
****************************************
************************************[vbc
ol=seagreen]
> Step'
>

Scheduled DB Backup Never Executed, Why? Why?

Howdy folks,
I am running win 2000 server + SP3 and SQL Server 7 with
SP3. I used Enterprise Manager to schedule weekly local
disk backup but it never executed. How do I know? I
browse throught the local disk, sql server log and could
not find any indications at all.
In Enterprise Manager->Management->Sql Server Log (no new
logs)
In Enterprise Manager->select the db->all task->backup db
1) On General Tab
Backup Portion -> DB Complete
Destinatin Portion -> Add and navigated to default
location, C:\MSSQL\BACKUP\AprilBackup.bak
Overwrite Portion -> overwrite existing media
Schedule -> recurring and entered the desinated day & hour
2) On Option Tab
I selected "Verify Backup upon completion"
I scheduled to run on Every Thursday at 4:00am but for the
past 4 weeks, no scheduled backup had ever executed.
Why? Can anyone help me, please.
Vito Corleone
President
Export & Import Oliver Oil Co.
Vito,
Check if sqlagent is running.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Vito Corleone" <anonymous@.discussions.microsoft.com> wrote in message
news:13fa01c4265a$edae9410$a301280a@.phx.gbl...
> Howdy folks,
> I am running win 2000 server + SP3 and SQL Server 7 with
> SP3. I used Enterprise Manager to schedule weekly local
> disk backup but it never executed. How do I know? I
> browse throught the local disk, sql server log and could
> not find any indications at all.
> In Enterprise Manager->Management->Sql Server Log (no new
> logs)
> In Enterprise Manager->select the db->all task->backup db
> 1) On General Tab
> Backup Portion -> DB Complete
> Destinatin Portion -> Add and navigated to default
> location, C:\MSSQL\BACKUP\AprilBackup.bak
> Overwrite Portion -> overwrite existing media
> Schedule -> recurring and entered the desinated day & hour
> 2) On Option Tab
> I selected "Verify Backup upon completion"
> I scheduled to run on Every Thursday at 4:00am but for the
> past 4 weeks, no scheduled backup had ever executed.
> Why? Can anyone help me, please.
> Vito Corleone
> President
> Export & Import Oliver Oil Co.
|||I'm sure you have verified this, but have you checked to make sure that the job is enabled. In EM go to Management - Sql Server Agent - Jobs. Make sure that the job in question has a yes in the enabled column.
|||Hi,
As Dinesh posted.. Please check whether your "SQL Agent" service in SQL
Server machine is
running. If stopped "start" the service and verify whether the job gets
executed.
Incase if the service failed to start, go to Control Panel -- Services-- SQL
Agent Log ON window.. Re- enter the
OS user name and password (if it is not starting in Local system account).
Enter the same OS User you used to start MSSQL
Server service.This will probably solve your issue
Thanks
Hari
MCDBA
"Vito Corleone" <anonymous@.discussions.microsoft.com> wrote in message
news:13fa01c4265a$edae9410$a301280a@.phx.gbl...
> Howdy folks,
> I am running win 2000 server + SP3 and SQL Server 7 with
> SP3. I used Enterprise Manager to schedule weekly local
> disk backup but it never executed. How do I know? I
> browse throught the local disk, sql server log and could
> not find any indications at all.
> In Enterprise Manager->Management->Sql Server Log (no new
> logs)
> In Enterprise Manager->select the db->all task->backup db
> 1) On General Tab
> Backup Portion -> DB Complete
> Destinatin Portion -> Add and navigated to default
> location, C:\MSSQL\BACKUP\AprilBackup.bak
> Overwrite Portion -> overwrite existing media
> Schedule -> recurring and entered the desinated day & hour
> 2) On Option Tab
> I selected "Verify Backup upon completion"
> I scheduled to run on Every Thursday at 4:00am but for the
> past 4 weeks, no scheduled backup had ever executed.
> Why? Can anyone help me, please.
> Vito Corleone
> President
> Export & Import Oliver Oil Co.

Scheduled DB Backup Never Executed, Why? Why?

Howdy folks,
I am running win 2000 server + SP3 and SQL Server 7 with
SP3. I used Enterprise Manager to schedule weekly local
disk backup but it never executed. How do I know? I
browse throught the local disk, sql server log and could
not find any indications at all.
In Enterprise Manager->Management->Sql Server Log (no new
logs)
In Enterprise Manager->select the db->all task->backup db
1) On General Tab
Backup Portion -> DB Complete
Destinatin Portion -> Add and navigated to default
location, C:\MSSQL\BACKUP\AprilBackup.bak
Overwrite Portion -> overwrite existing media
Schedule -> recurring and entered the desinated day & hour
2) On Option Tab
I selected "Verify Backup upon completion"
I scheduled to run on Every Thursday at 4:00am but for the
past 4 weeks, no scheduled backup had ever executed.
Why? Can anyone help me, please.
Vito Corleone
President
Export & Import Oliver Oil Co.Vito,
Check if sqlagent is running.
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Vito Corleone" <anonymous@.discussions.microsoft.com> wrote in message
news:13fa01c4265a$edae9410$a301280a@.phx.gbl...
> Howdy folks,
> I am running win 2000 server + SP3 and SQL Server 7 with
> SP3. I used Enterprise Manager to schedule weekly local
> disk backup but it never executed. How do I know? I
> browse throught the local disk, sql server log and could
> not find any indications at all.
> In Enterprise Manager->Management->Sql Server Log (no new
> logs)
> In Enterprise Manager->select the db->all task->backup db
> 1) On General Tab
> Backup Portion -> DB Complete
> Destinatin Portion -> Add and navigated to default
> location, C:\MSSQL\BACKUP\AprilBackup.bak
> Overwrite Portion -> overwrite existing media
> Schedule -> recurring and entered the desinated day & hour
> 2) On Option Tab
> I selected "Verify Backup upon completion"
> I scheduled to run on Every Thursday at 4:00am but for the
> past 4 weeks, no scheduled backup had ever executed.
> Why? Can anyone help me, please.
> Vito Corleone
> President
> Export & Import Oliver Oil Co.|||I'm sure you have verified this, but have you checked to make sure that the
job is enabled. In EM go to Management - Sql Server Agent - Jobs. Make sure
that the job in question has a yes in the enabled column.|||Hi,
As Dinesh posted.. Please check whether your "SQL Agent" service in SQL
Server machine is
running. If stopped "start" the service and verify whether the job gets
executed.
Incase if the service failed to start, go to Control Panel -- Services-- SQL
Agent Log ON window.. Re- enter the
OS user name and password (if it is not starting in Local system account).
Enter the same OS User you used to start MSSQL
Server service.This will probably solve your issue
Thanks
Hari
MCDBA
"Vito Corleone" <anonymous@.discussions.microsoft.com> wrote in message
news:13fa01c4265a$edae9410$a301280a@.phx.gbl...
> Howdy folks,
> I am running win 2000 server + SP3 and SQL Server 7 with
> SP3. I used Enterprise Manager to schedule weekly local
> disk backup but it never executed. How do I know? I
> browse throught the local disk, sql server log and could
> not find any indications at all.
> In Enterprise Manager->Management->Sql Server Log (no new
> logs)
> In Enterprise Manager->select the db->all task->backup db
> 1) On General Tab
> Backup Portion -> DB Complete
> Destinatin Portion -> Add and navigated to default
> location, C:\MSSQL\BACKUP\AprilBackup.bak
> Overwrite Portion -> overwrite existing media
> Schedule -> recurring and entered the desinated day & hour
> 2) On Option Tab
> I selected "Verify Backup upon completion"
> I scheduled to run on Every Thursday at 4:00am but for the
> past 4 weeks, no scheduled backup had ever executed.
> Why? Can anyone help me, please.
> Vito Corleone
> President
> Export & Import Oliver Oil Co.

Scheduled DB Backup Never Executed, Why? Why?

Howdy folks,
I am running win 2000 server + SP3 and SQL Server 7 with
SP3. I used Enterprise Manager to schedule weekly local
disk backup but it never executed. How do I know? I
browse throught the local disk, sql server log and could
not find any indications at all.
In Enterprise Manager->Management->Sql Server Log (no new
logs)
In Enterprise Manager->select the db->all task->backup db
1) On General Tab
Backup Portion -> DB Complete
Destinatin Portion -> Add and navigated to default
location, C:\MSSQL\BACKUP\AprilBackup.bak
Overwrite Portion -> overwrite existing media
Schedule -> recurring and entered the desinated day & hour
2) On Option Tab
I selected "Verify Backup upon completion"
I scheduled to run on Every Thursday at 4:00am but for the
past 4 weeks, no scheduled backup had ever executed.
Why? Can anyone help me, please.
Vito Corleone
President
Export & Import Oliver Oil Co.Vito,
Check if sqlagent is running.
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Vito Corleone" <anonymous@.discussions.microsoft.com> wrote in message
news:13fa01c4265a$edae9410$a301280a@.phx.gbl...
> Howdy folks,
> I am running win 2000 server + SP3 and SQL Server 7 with
> SP3. I used Enterprise Manager to schedule weekly local
> disk backup but it never executed. How do I know? I
> browse throught the local disk, sql server log and could
> not find any indications at all.
> In Enterprise Manager->Management->Sql Server Log (no new
> logs)
> In Enterprise Manager->select the db->all task->backup db
> 1) On General Tab
> Backup Portion -> DB Complete
> Destinatin Portion -> Add and navigated to default
> location, C:\MSSQL\BACKUP\AprilBackup.bak
> Overwrite Portion -> overwrite existing media
> Schedule -> recurring and entered the desinated day & hour
> 2) On Option Tab
> I selected "Verify Backup upon completion"
> I scheduled to run on Every Thursday at 4:00am but for the
> past 4 weeks, no scheduled backup had ever executed.
> Why? Can anyone help me, please.
> Vito Corleone
> President
> Export & Import Oliver Oil Co.|||I'm sure you have verified this, but have you checked to make sure that the job is enabled. In EM go to Management - Sql Server Agent - Jobs. Make sure that the job in question has a yes in the enabled column.|||Hi,
As Dinesh posted.. Please check whether your "SQL Agent" service in SQL
Server machine is
running. If stopped "start" the service and verify whether the job gets
executed.
Incase if the service failed to start, go to Control Panel -- Services-- SQL
Agent Log ON window.. Re- enter the
OS user name and password (if it is not starting in Local system account).
Enter the same OS User you used to start MSSQL
Server service.This will probably solve your issue
Thanks
Hari
MCDBA
"Vito Corleone" <anonymous@.discussions.microsoft.com> wrote in message
news:13fa01c4265a$edae9410$a301280a@.phx.gbl...
> Howdy folks,
> I am running win 2000 server + SP3 and SQL Server 7 with
> SP3. I used Enterprise Manager to schedule weekly local
> disk backup but it never executed. How do I know? I
> browse throught the local disk, sql server log and could
> not find any indications at all.
> In Enterprise Manager->Management->Sql Server Log (no new
> logs)
> In Enterprise Manager->select the db->all task->backup db
> 1) On General Tab
> Backup Portion -> DB Complete
> Destinatin Portion -> Add and navigated to default
> location, C:\MSSQL\BACKUP\AprilBackup.bak
> Overwrite Portion -> overwrite existing media
> Schedule -> recurring and entered the desinated day & hour
> 2) On Option Tab
> I selected "Verify Backup upon completion"
> I scheduled to run on Every Thursday at 4:00am but for the
> past 4 weeks, no scheduled backup had ever executed.
> Why? Can anyone help me, please.
> Vito Corleone
> President
> Export & Import Oliver Oil Co.

SCHEDULE DTS PACKAGE ERROR

I am having trouble scheduling a DTS package.
The error I receive is:
Executed as user: MAGIC-SQL-02\SYSTEM. DTSRun: Loading...
Error: -2147467259 (80004005); Provider Error: 17 (11) Error
string: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied. Error source: Microsoft OLE DB Provider for SQL Server
Help file: Help context: 0. Process Exit Code 1. The step failed.
Any idea why
TIA
GrantCheck the SQL Server Agent startup account. It appears the system account
is being used. NOt sure which SQL Server is causing the SQL Server does not
exist or access denied error, but if it is a remote SQL Server then the
system account will not have access to it. Change teh SQL Server Agent
startup account to a domain account that has access to all SQL Servers
accessed by the package.
Rand
This posting is provided "as is" with no warranties and confers no rights.