Job with stored proc succeeds with sqlstate 01000

I have a stored procedure that I am executing through the sql server
job scheduler, it executes properly but after each line in the log file
there is a sqlstate message.
procedure name p_document_purge [SQLSTATE 01000]
Archiving records [SQLSTATE 01000]
51 rows archived [SQLSTATE 01000]
Purging duplicate records [SQLSTATE 01000]
51 rows purged [SQLSTATE 01000]
Purge completed successfully [SQLSTATE 01000]
Does anyone know what might cause this? The @.@.ERROR during the
procedure is always 0 or it would rollback the entire transaction. Also
If I run the proc from query analyzer I do not get any negative
feedback regarding it. I tried looking in the documentation, but this
is listed as a general error which doesn't really help.
Thanks
BillPrint statements in the stored procedure can result in the
sqlstate message.
-Sue
.
On 23 Feb 2006 06:30:49 -0800, william_dudek@.yahoo.com
wrote:

>I have a stored procedure that I am executing through the sql server
>job scheduler, it executes properly but after each line in the log file
>there is a sqlstate message.
>procedure name p_document_purge [SQLSTATE 01000]
>Archiving records [SQLSTATE 01000]
>51 rows archived [SQLSTATE 01000]
>Purging duplicate records [SQLSTATE 01000]
>51 rows purged [SQLSTATE 01000]
>Purge completed successfully [SQLSTATE 01000]
>Does anyone know what might cause this? The @.@.ERROR during the
>procedure is always 0 or it would rollback the entire transaction. Also
>If I run the proc from query analyzer I do not get any negative
>feedback regarding it. I tried looking in the documentation, but this
>is listed as a general error which doesn't really help.
>Thanks
>Bill

Job with stored proc succeeds with sqlstate 01000

I have a stored procedure that I am executing through the sql server
job scheduler, it executes properly but after each line in the log file
there is a sqlstate message.
procedure name p_document_purge [SQLSTATE 01000]
Archiving records [SQLSTATE 01000]
51 rows archived [SQLSTATE 01000]
Purging duplicate records [SQLSTATE 01000]
51 rows purged [SQLSTATE 01000]
Purge completed successfully [SQLSTATE 01000]
Does anyone know what might cause this? The @.@.ERROR during the
procedure is always 0 or it would rollback the entire transaction. Also
If I run the proc from query analyzer I do not get any negative
feedback regarding it. I tried looking in the documentation, but this
is listed as a general error which doesn't really help.
Thanks
BillPrint statements in the stored procedure can result in the
sqlstate message.
-Sue
.
On 23 Feb 2006 06:30:49 -0800, william_dudek@.yahoo.com
wrote:
>I have a stored procedure that I am executing through the sql server
>job scheduler, it executes properly but after each line in the log file
>there is a sqlstate message.
>procedure name p_document_purge [SQLSTATE 01000]
>Archiving records [SQLSTATE 01000]
>51 rows archived [SQLSTATE 01000]
>Purging duplicate records [SQLSTATE 01000]
>51 rows purged [SQLSTATE 01000]
>Purge completed successfully [SQLSTATE 01000]
>Does anyone know what might cause this? The @.@.ERROR during the
>procedure is always 0 or it would rollback the entire transaction. Also
>If I run the proc from query analyzer I do not get any negative
>feedback regarding it. I tried looking in the documentation, but this
>is listed as a general error which doesn't really help.
>Thanks
>Bill

Job with stored proc succeeds with sqlstate 01000

I have a stored procedure that I am executing through the sql server
job scheduler, it executes properly but after each line in the log file
there is a sqlstate message.
procedure name p_document_purge [SQLSTATE 01000]
Archiving records [SQLSTATE 01000]
51 rows archived [SQLSTATE 01000]
Purging duplicate records [SQLSTATE 01000]
51 rows purged [SQLSTATE 01000]
Purge completed successfully [SQLSTATE 01000]
Does anyone know what might cause this? The @.@.ERROR during the
procedure is always 0 or it would rollback the entire transaction. Also
If I run the proc from query analyzer I do not get any negative
feedback regarding it. I tried looking in the documentation, but this
is listed as a general error which doesn't really help.
Thanks
Bill
Print statements in the stored procedure can result in the
sqlstate message.
-Sue
..
On 23 Feb 2006 06:30:49 -0800, william_dudek@.yahoo.com
wrote:

>I have a stored procedure that I am executing through the sql server
>job scheduler, it executes properly but after each line in the log file
>there is a sqlstate message.
>procedure name p_document_purge [SQLSTATE 01000]
>Archiving records [SQLSTATE 01000]
>51 rows archived [SQLSTATE 01000]
>Purging duplicate records [SQLSTATE 01000]
>51 rows purged [SQLSTATE 01000]
>Purge completed successfully [SQLSTATE 01000]
>Does anyone know what might cause this? The @.@.ERROR during the
>procedure is always 0 or it would rollback the entire transaction. Also
>If I run the proc from query analyzer I do not get any negative
>feedback regarding it. I tried looking in the documentation, but this
>is listed as a general error which doesn't really help.
>Thanks
>Bill
sql

Job Scheduler Question - 2005

I have a scheduled job for a DTS package and was reviewing the history, but
it only keeps 50 events listed in the history. Is there any way to expand
this or a query that can be used to extract more history about the executed
jobs?
Yes I am talking about the history and know how to access it. I was asking if
there was a way to expand the number of executions or having a way to look
past the list of 50.
"Tibor Karaszi" wrote:

> Are you talking of how many executions it has history for? If so, Right-click Agent, Properties,
> History.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Big Ern" <BigErn@.discussions.microsoft.com> wrote in message
> news:9528FF37-5BD1-4CA5-AFC5-B7EC2F3D0AE0@.microsoft.com...
>
>

Job scheduler in SQL server

Hi,

I have to genearte an autoamtic email in sql server

could any body guide me for how to schedule job and how to generate automatic email.

Thankyou in Advance.

regards,

Raja.

check this

http://classicasp.aspfaq.com/email/how-do-i-send-e-mail-from-sql-server.html

Job Scheduler fails and Managing Tempdb

Hello,
I have two issues, hoping someone can help.
Issue 1. I have various DTS packages that copy data from Progress
Database to Sql Data Warehouse. The ODBC Connection is stable and
packages have been auto scheduled by creating a job that is managed by
the SQL Agent service to run daily at night. The packages work fine
only in two cases, when running manually by using the DTSRun.exe
command line utility and when the job is manually run in the SQL Agent
service. Auto run is alwayz showing a status failer, I'm now using
windows scheduler and my packs are now always a success.
My question is why is SQL Agent not reliable? I'm 100% sure that there
is absolutely nothing wrong with the packets as they run error free
when manually ran.
Issue 2. My data warehouse is 28 G in size this makes the tempdb to
grow bigger everyday. To downsize it I stop and start the sql service
manually, can you please assist me with a batch command to auto start
and stop the service?
Thanking you in advance
Babalwa
1) This most likely is a permissions issue. Check that the account that SQL
Agent is running under has the appropriate permissions to execute everything
in your DTS package. It can be running under the LocalSystem account, which
doesn't have any permissions outside the local computer.
2) It's not much use shrinking tempdb, as it will grow again when you use
the server. And when tempdb auto grows that will only slow down your server.
You can check however if there are any transaction that stay open in tempdb
for a long time, cause extra space to be used, and prevent reuse of the
transaction log. Use DBCC OPENTRAN ('tempdb') to see if you have any old
transactions.
Otherwise the size of tempdb is something you have to live with, with your
current setup. Check if you can either change your applications and
databases, so tempdb is needed less, or you might have to get more harddisk
space.
Jacco Schalkwijk
SQL Server MVP
"Babalwa Magwentshu" <babalwa@.hotmail.com> wrote in message
news:5999368f.0407280128.75bd9322@.posting.google.c om...
> Hello,
> I have two issues, hoping someone can help.
> Issue 1. I have various DTS packages that copy data from Progress
> Database to Sql Data Warehouse. The ODBC Connection is stable and
> packages have been auto scheduled by creating a job that is managed by
> the SQL Agent service to run daily at night. The packages work fine
> only in two cases, when running manually by using the DTSRun.exe
> command line utility and when the job is manually run in the SQL Agent
> service. Auto run is alwayz showing a status failer, I'm now using
> windows scheduler and my packs are now always a success.
> My question is why is SQL Agent not reliable? I'm 100% sure that there
> is absolutely nothing wrong with the packets as they run error free
> when manually ran.
> Issue 2. My data warehouse is 28 G in size this makes the tempdb to
> grow bigger everyday. To downsize it I stop and start the sql service
> manually, can you please assist me with a batch command to auto start
> and stop the service?
> Thanking you in advance
> Babalwa
|||Thank you for your response Jacco,
Let me briefly expand on the issue, I am the domain administrator and
have designed the data warehouse packets and it's schedules under my
administrative password. I have checked the permissions, security
won't be the issue. Correct me if I'm wrong, this is how I understand
the security concept - for packages created under a Microsoft Windows
NT 4.0 or Microsoft Windows 2000 account, the job runs under the
security context of the account that started SQL Server Agent.
Thank you again,
babalwa@.hotmail.com (Babalwa Magwentshu) wrote in message news:<5999368f.0407280128.75bd9322@.posting.google. com>...
> Hello,
> I have two issues, hoping someone can help.
> Issue 1. I have various DTS packages that copy data from Progress
> Database to Sql Data Warehouse. The ODBC Connection is stable and
> packages have been auto scheduled by creating a job that is managed by
> the SQL Agent service to run daily at night. The packages work fine
> only in two cases, when running manually by using the DTSRun.exe
> command line utility and when the job is manually run in the SQL Agent
> service. Auto run is alwayz showing a status failer, I'm now using
> windows scheduler and my packs are now always a success.
> My question is why is SQL Agent not reliable? I'm 100% sure that there
> is absolutely nothing wrong with the packets as they run error free
> when manually ran.
> Issue 2. My data warehouse is 28 G in size this makes the tempdb to
> grow bigger everyday. To downsize it I stop and start the sql service
> manually, can you please assist me with a batch command to auto start
> and stop the service?
> Thanking you in advance
> Babalwa

Job Scheduler fails and Managing Tempdb

Hello,
I have two issues, hoping someone can help.
Issue 1. I have various DTS packages that copy data from Progress
Database to Sql Data Warehouse. The ODBC Connection is stable and
packages have been auto scheduled by creating a job that is managed by
the SQL Agent service to run daily at night. The packages work fine
only in two cases, when running manually by using the DTSRun.exe
command line utility and when the job is manually run in the SQL Agent
service. Auto run is alwayz showing a status failer, I'm now using
windows scheduler and my packs are now always a success.
My question is why is SQL Agent not reliable? I'm 100% sure that there
is absolutely nothing wrong with the packets as they run error free
when manually ran.
Issue 2. My data warehouse is 28 G in size this makes the tempdb to
grow bigger everyday. To downsize it I stop and start the sql service
manually, can you please assist me with a batch command to auto start
and stop the service?
Thanking you in advance
Babalwa1) This most likely is a permissions issue. Check that the account that SQL
Agent is running under has the appropriate permissions to execute everything
in your DTS package. It can be running under the LocalSystem account, which
doesn't have any permissions outside the local computer.
2) It's not much use shrinking tempdb, as it will grow again when you use
the server. And when tempdb auto grows that will only slow down your server.
You can check however if there are any transaction that stay open in tempdb
for a long time, cause extra space to be used, and prevent reuse of the
transaction log. Use DBCC OPENTRAN ('tempdb') to see if you have any old
transactions.
Otherwise the size of tempdb is something you have to live with, with your
current setup. Check if you can either change your applications and
databases, so tempdb is needed less, or you might have to get more harddisk
space.
Jacco Schalkwijk
SQL Server MVP
"Babalwa Magwentshu" <babalwa@.hotmail.com> wrote in message
news:5999368f.0407280128.75bd9322@.posting.google.com...
> Hello,
> I have two issues, hoping someone can help.
> Issue 1. I have various DTS packages that copy data from Progress
> Database to Sql Data Warehouse. The ODBC Connection is stable and
> packages have been auto scheduled by creating a job that is managed by
> the SQL Agent service to run daily at night. The packages work fine
> only in two cases, when running manually by using the DTSRun.exe
> command line utility and when the job is manually run in the SQL Agent
> service. Auto run is alwayz showing a status failer, I'm now using
> windows scheduler and my packs are now always a success.
> My question is why is SQL Agent not reliable? I'm 100% sure that there
> is absolutely nothing wrong with the packets as they run error free
> when manually ran.
> Issue 2. My data warehouse is 28 G in size this makes the tempdb to
> grow bigger everyday. To downsize it I stop and start the sql service
> manually, can you please assist me with a batch command to auto start
> and stop the service?
> Thanking you in advance
> Babalwa|||Thank you for your response Jacco,
Let me briefly expand on the issue, I am the domain administrator and
have designed the data warehouse packets and it's schedules under my
administrative password. I have checked the permissions, security
won't be the issue. Correct me if I'm wrong, this is how I understand
the security concept - for packages created under a Microsoft Windows
NT 4.0 or Microsoft Windows 2000 account, the job runs under the
security context of the account that started SQL Server Agent.
Thank you again,
babalwa@.hotmail.com (Babalwa Magwentshu) wrote in message news:<5999368f.0407280128.75bd9322
@.posting.google.com>...
> Hello,
> I have two issues, hoping someone can help.
> Issue 1. I have various DTS packages that copy data from Progress
> Database to Sql Data Warehouse. The ODBC Connection is stable and
> packages have been auto scheduled by creating a job that is managed by
> the SQL Agent service to run daily at night. The packages work fine
> only in two cases, when running manually by using the DTSRun.exe
> command line utility and when the job is manually run in the SQL Agent
> service. Auto run is alwayz showing a status failer, I'm now using
> windows scheduler and my packs are now always a success.
> My question is why is SQL Agent not reliable? I'm 100% sure that there
> is absolutely nothing wrong with the packets as they run error free
> when manually ran.
> Issue 2. My data warehouse is 28 G in size this makes the tempdb to
> grow bigger everyday. To downsize it I stop and start the sql service
> manually, can you please assist me with a batch command to auto start
> and stop the service?
> Thanking you in advance
> Babalwasql

Job Scheduler

Hi all
When I run a stored procedure using the job scheduler in
SQL 2000 it takes more time to complete comparing when I
run it in the Query analyser.
Is there any reason behind this?
Example
I am running a stored Procedure for generating a report
every one minute using a job scheduler.
It takes 13 seconds to complete.
Whereas when I run the same SP in Query Analyser it takes
only 2 sec or 3 seconds.
Please clarify.
Thanks in advance
AnandThis could be the problem:
http://support.microsoft.com/defaul...730&Product=sql
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Anand" <gurusanand@.yahoo.com> wrote in message
news:024101c3db49$baff3990$a001280a@.phx.gbl...
Hi all
When I run a stored procedure using the job scheduler in
SQL 2000 it takes more time to complete comparing when I
run it in the Query analyser.
Is there any reason behind this?
Example
I am running a stored Procedure for generating a report
every one minute using a job scheduler.
It takes 13 seconds to complete.
Whereas when I run the same SP in Query Analyser it takes
only 2 sec or 3 seconds.
Please clarify.
Thanks in advance
Anand

Job scheduler

Hi all
In which table in msdb Database the Executing status of
the job is stored. I need the table name - which holds the
information like
1. Job started.
2. Job executing
3. Job completed info.
The above status may be in the same field of the table
Thanks in advance
Anand.Hi,
Data will be stored in SYSJOBHISTORY table of MSDB database
Column name is : RUN_STATUS
The column hols the below status,
0 = Failed
1 = Succeeded
2 = Retry
3 = Canceled
4 = In progress
Since querying the system table is not advisible , you can execute the
system procedure "SP_HELP_JOBHISTORY" to get the information regarding the
status of each scheduled task.
Thanks
Hari
MCDBA
"Guru S. Anand" <anonymous@.discussions.microsoft.com> wrote in message
news:2d1b01c3fcd6$10b00d80$a001280a@.phx.gbl...
> Hi all
> In which table in msdb Database the Executing status of
> the job is stored. I need the table name - which holds the
> information like
> 1. Job started.
> 2. Job executing
> 3. Job completed info.
> The above status may be in the same field of the table
> Thanks in advance
> Anand.|||Thanks Hari
Anand.

>--Original Message--
>Hi,
>Data will be stored in SYSJOBHISTORY table of MSDB
database
>Column name is : RUN_STATUS
>The column hols the below status,
>0 = Failed
>1 = Succeeded
>2 = Retry
>3 = Canceled
>4 = In progress
>Since querying the system table is not advisible , you
can execute the
>system procedure "SP_HELP_JOBHISTORY" to get the
information regarding the
>status of each scheduled task.
>Thanks
>Hari
>MCDBA
>
>"Guru S. Anand" <anonymous@.discussions.microsoft.com>
wrote in message
>news:2d1b01c3fcd6$10b00d80$a001280a@.phx.gbl...
the
>
>.
>

Job Scheduler

Hello,
Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2 PM for
the first three weeks of the month and for the last week of the month have
the job run every 90 minutes.
Thanks in advance
stone outI doubt that you can do that via EM. Perhaps you wil, have to run some
script that determines a week's number and changes the schedule accordingly
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:81122877-29AB-4F21-82E0-A0F6F337269D@.microsoft.com...
> Hello,
> Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2 PM for
> the first three weeks of the month and for the last week of the month have
> the job run every 90 minutes.
> Thanks in advance
> stone out|||You may be able to do this with multiple schedules.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:81122877-29AB-4F21-82E0-A0F6F337269D@.microsoft.com...
> Hello,
> Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2 PM for
> the first three weeks of the month and for the last week of the month have
> the job run every 90 minutes.
> Thanks in advance
> stone out|||stoney wrote:
> Hello,
> Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2
> PM for the first three weeks of the month and for the last week of
> the month have the job run every 90 minutes.
> Thanks in advance
> stone out
Set up the schedule to run every 90 minutes. Using T-SQL, determine
where you are in the month and complete or terminate the script
accordingly.
David Gugick
Quest Software
www.imceda.com
www.quest.com

Job Scheduler

To All:
How do you make sure a job does not run until a first step job finishes.
For example you want to make sure a "dbcc CHECKDB" does not run until a
backup job finishes.
Thanks
TunjiYou mean you have 2 seperate jobs and you want to run
them back to back?
What I am aware are 1. combine the 2 jobs into one
or 2. in the second job, check the jobhistory table to
see if the first one finishes or not.
>--Original Message--
>To All:
>How do you make sure a job does not run until a first
step job finishes.
>For example you want to make sure a "dbcc CHECKDB" does
not run until a
>backup job finishes.
>Thanks
>Tunji
>
>.
>|||Thanks Keene.
Yes, if you have 2 seperate jobs ... I want the second job to run only after
the first job finishes.
Thanks for your response.
"Keene" <anonymous@.discussions.microsoft.com> wrote in message
news:1a7e801c41e3c$55b17220$a501280a@.phx
.gbl...
> You mean you have 2 seperate jobs and you want to run
> them back to back?
> What I am aware are 1. combine the 2 jobs into one
> or 2. in the second job, check the jobhistory table to
> see if the first one finishes or not.
> step job finishes.
> not run until a|||When there are 2 separate jobs, there is no easy way to do this... Even if
you create another job which does an sp_start_job on each of the other jobs,
they will run concurrently. When the first job is started, the next
statement runs...
You can put each of the steps in both jobs into a single job with multiple
steps, then they will run as you wish, but that leaves you with a single
huge job...
Some folks write programs which use SQL DMO to query the status of one job
prior to programmatically starting the second... This is often too much
trouble as well... Most folks simply check the elapsed times of jobs and
adjust the start times occasionally..
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Tunji" <Tunj@.hotmail.com> wrote in message
news:e3ZYXjjHEHA.3696@.TK2MSFTNGP10.phx.gbl...
> To All:
> How do you make sure a job does not run until a first step job finishes.
> For example you want to make sure a "dbcc CHECKDB" does not run until a
> backup job finishes.
> Thanks
> Tunji
>|||Thanks Wayne!
That was helpful.
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:uDpNCAkHEHA.1528@.TK2MSFTNGP09.phx.gbl...
> When there are 2 separate jobs, there is no easy way to do this... Even
if
> you create another job which does an sp_start_job on each of the other
jobs,
> they will run concurrently. When the first job is started, the next
> statement runs...
> You can put each of the steps in both jobs into a single job with multiple
> steps, then they will run as you wish, but that leaves you with a single
> huge job...
> Some folks write programs which use SQL DMO to query the status of one job
> prior to programmatically starting the second... This is often too much
> trouble as well... Most folks simply check the elapsed times of jobs and
> adjust the start times occasionally..
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Computer Education Services Corporation (CESC), Charlotte, NC
> www.computeredservices.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
>
> "Tunji" <Tunj@.hotmail.com> wrote in message
> news:e3ZYXjjHEHA.3696@.TK2MSFTNGP10.phx.gbl...
>|||What if i have a job that runs say twice a day (12.00 A.M and 12.00 Noon).
what happens if the 12.00 am job does not finish at 12 noon (next run).
Thanks,
Tunji
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:uDpNCAkHEHA.1528@.TK2MSFTNGP09.phx.gbl...
> When there are 2 separate jobs, there is no easy way to do this... Even
if
> you create another job which does an sp_start_job on each of the other
jobs,
> they will run concurrently. When the first job is started, the next
> statement runs...
> You can put each of the steps in both jobs into a single job with multiple
> steps, then they will run as you wish, but that leaves you with a single
> huge job...
> Some folks write programs which use SQL DMO to query the status of one job
> prior to programmatically starting the second... This is often too much
> trouble as well... Most folks simply check the elapsed times of jobs and
> adjust the start times occasionally..
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Computer Education Services Corporation (CESC), Charlotte, NC
> www.computeredservices.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
>
> "Tunji" <Tunj@.hotmail.com> wrote in message
> news:e3ZYXjjHEHA.3696@.TK2MSFTNGP10.phx.gbl...
>

Job Scheduler

Hello,
Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2 PM for
the first three weeks of the month and for the last week of the month have
the job run every 90 minutes.
Thanks in advance
stone outI doubt that you can do that via EM. Perhaps you wil, have to run some
script that determines a week's number and changes the schedule accordingly
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:81122877-29AB-4F21-82E0-A0F6F337269D@.microsoft.com...
> Hello,
> Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2 PM for
> the first three weeks of the month and for the last week of the month have
> the job run every 90 minutes.
> Thanks in advance
> stone out|||You may be able to do this with multiple schedules.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:81122877-29AB-4F21-82E0-A0F6F337269D@.microsoft.com...
> Hello,
> Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2 PM for
> the first three weeks of the month and for the last week of the month have
> the job run every 90 minutes.
> Thanks in advance
> stone out|||stoney wrote:
> Hello,
> Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2
> PM for the first three weeks of the month and for the last week of
> the month have the job run every 90 minutes.
> Thanks in advance
> stone out
Set up the schedule to run every 90 minutes. Using T-SQL, determine
where you are in the month and complete or terminate the script
accordingly.
--
David Gugick
Quest Software
www.imceda.com
www.quest.comsql

Job Scheduler

To All:
How do you make sure a job does not run until a first step job finishes.
For example you want to make sure a "dbcc CHECKDB" does not run until a
backup job finishes.
Thanks
TunjiYou mean you have 2 seperate jobs and you want to run
them back to back?
What I am aware are 1. combine the 2 jobs into one
or 2. in the second job, check the jobhistory table to
see if the first one finishes or not.
>--Original Message--
>To All:
>How do you make sure a job does not run until a first
step job finishes.
>For example you want to make sure a "dbcc CHECKDB" does
not run until a
>backup job finishes.
>Thanks
>Tunji
>
>.
>|||Thanks Keene.
Yes, if you have 2 seperate jobs ... I want the second job to run only after
the first job finishes.
Thanks for your response.
"Keene" <anonymous@.discussions.microsoft.com> wrote in message
news:1a7e801c41e3c$55b17220$a501280a@.phx.gbl...
> You mean you have 2 seperate jobs and you want to run
> them back to back?
> What I am aware are 1. combine the 2 jobs into one
> or 2. in the second job, check the jobhistory table to
> see if the first one finishes or not.
> >--Original Message--
> >To All:
> >
> >How do you make sure a job does not run until a first
> step job finishes.
> >For example you want to make sure a "dbcc CHECKDB" does
> not run until a
> >backup job finishes.
> >
> >Thanks
> >
> >Tunji
> >
> >
> >.
> >|||When there are 2 separate jobs, there is no easy way to do this... Even if
you create another job which does an sp_start_job on each of the other jobs,
they will run concurrently. When the first job is started, the next
statement runs...
You can put each of the steps in both jobs into a single job with multiple
steps, then they will run as you wish, but that leaves you with a single
huge job...
Some folks write programs which use SQL DMO to query the status of one job
prior to programmatically starting the second... This is often too much
trouble as well... Most folks simply check the elapsed times of jobs and
adjust the start times occasionally..
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Tunji" <Tunj@.hotmail.com> wrote in message
news:e3ZYXjjHEHA.3696@.TK2MSFTNGP10.phx.gbl...
> To All:
> How do you make sure a job does not run until a first step job finishes.
> For example you want to make sure a "dbcc CHECKDB" does not run until a
> backup job finishes.
> Thanks
> Tunji
>|||Thanks Wayne!
That was helpful.
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:uDpNCAkHEHA.1528@.TK2MSFTNGP09.phx.gbl...
> When there are 2 separate jobs, there is no easy way to do this... Even
if
> you create another job which does an sp_start_job on each of the other
jobs,
> they will run concurrently. When the first job is started, the next
> statement runs...
> You can put each of the steps in both jobs into a single job with multiple
> steps, then they will run as you wish, but that leaves you with a single
> huge job...
> Some folks write programs which use SQL DMO to query the status of one job
> prior to programmatically starting the second... This is often too much
> trouble as well... Most folks simply check the elapsed times of jobs and
> adjust the start times occasionally..
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Computer Education Services Corporation (CESC), Charlotte, NC
> www.computeredservices.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
>
> "Tunji" <Tunj@.hotmail.com> wrote in message
> news:e3ZYXjjHEHA.3696@.TK2MSFTNGP10.phx.gbl...
> > To All:
> >
> > How do you make sure a job does not run until a first step job finishes.
> > For example you want to make sure a "dbcc CHECKDB" does not run until a
> > backup job finishes.
> >
> > Thanks
> >
> > Tunji
> >
> >
>|||What if i have a job that runs say twice a day (12.00 A.M and 12.00 Noon).
what happens if the 12.00 am job does not finish at 12 noon (next run).
Thanks,
Tunji
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:uDpNCAkHEHA.1528@.TK2MSFTNGP09.phx.gbl...
> When there are 2 separate jobs, there is no easy way to do this... Even
if
> you create another job which does an sp_start_job on each of the other
jobs,
> they will run concurrently. When the first job is started, the next
> statement runs...
> You can put each of the steps in both jobs into a single job with multiple
> steps, then they will run as you wish, but that leaves you with a single
> huge job...
> Some folks write programs which use SQL DMO to query the status of one job
> prior to programmatically starting the second... This is often too much
> trouble as well... Most folks simply check the elapsed times of jobs and
> adjust the start times occasionally..
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Computer Education Services Corporation (CESC), Charlotte, NC
> www.computeredservices.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
>
> "Tunji" <Tunj@.hotmail.com> wrote in message
> news:e3ZYXjjHEHA.3696@.TK2MSFTNGP10.phx.gbl...
> > To All:
> >
> > How do you make sure a job does not run until a first step job finishes.
> > For example you want to make sure a "dbcc CHECKDB" does not run until a
> > backup job finishes.
> >
> > Thanks
> >
> > Tunji
> >
> >
>

Job scheduler

Hi all
In which table in msdb Database the Executing status of
the job is stored. I need the table name - which holds the
information like
1. Job started.
2. Job executing
3. Job completed info.
The above status may be in the same field of the table
Thanks in advance
Anand.Hi,
Data will be stored in SYSJOBHISTORY table of MSDB database
Column name is : RUN_STATUS
The column hols the below status,
0 = Failed
1 = Succeeded
2 = Retry
3 = Canceled
4 = In progress
Since querying the system table is not advisible , you can execute the
system procedure "SP_HELP_JOBHISTORY" to get the information regarding the
status of each scheduled task.
Thanks
Hari
MCDBA
"Guru S. Anand" <anonymous@.discussions.microsoft.com> wrote in message
news:2d1b01c3fcd6$10b00d80$a001280a@.phx.gbl...
> Hi all
> In which table in msdb Database the Executing status of
> the job is stored. I need the table name - which holds the
> information like
> 1. Job started.
> 2. Job executing
> 3. Job completed info.
> The above status may be in the same field of the table
> Thanks in advance
> Anand.|||Thanks Hari
Anand.
>--Original Message--
>Hi,
>Data will be stored in SYSJOBHISTORY table of MSDB
database
>Column name is : RUN_STATUS
>The column hols the below status,
>0 = Failed
>1 = Succeeded
>2 = Retry
>3 = Canceled
>4 = In progress
>Since querying the system table is not advisible , you
can execute the
>system procedure "SP_HELP_JOBHISTORY" to get the
information regarding the
>status of each scheduled task.
>Thanks
>Hari
>MCDBA
>
>"Guru S. Anand" <anonymous@.discussions.microsoft.com>
wrote in message
>news:2d1b01c3fcd6$10b00d80$a001280a@.phx.gbl...
>> Hi all
>> In which table in msdb Database the Executing status of
>> the job is stored. I need the table name - which holds
the
>> information like
>> 1. Job started.
>> 2. Job executing
>> 3. Job completed info.
>> The above status may be in the same field of the table
>> Thanks in advance
>> Anand.
>
>.
>

Job Scheduler

Hi all
When I run a stored procedure using the job scheduler in
SQL 2000 it takes more time to complete comparing when I
run it in the Query analyser.
Is there any reason behind this?
Example
I am running a stored Procedure for generating a report
every one minute using a job scheduler.
It takes 13 seconds to complete.
Whereas when I run the same SP in Query Analyser it takes
only 2 sec or 3 seconds.
Please clarify.
Thanks in advance
AnandThis could be the problem:
http://support.microsoft.com/default.aspx?scid=kb;en-us;249730&Product=sql
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Anand" <gurusanand@.yahoo.com> wrote in message
news:024101c3db49$baff3990$a001280a@.phx.gbl...
Hi all
When I run a stored procedure using the job scheduler in
SQL 2000 it takes more time to complete comparing when I
run it in the Query analyser.
Is there any reason behind this?
Example
I am running a stored Procedure for generating a report
every one minute using a job scheduler.
It takes 13 seconds to complete.
Whereas when I run the same SP in Query Analyser it takes
only 2 sec or 3 seconds.
Please clarify.
Thanks in advance
Anand|||Do you SET NOCOUNT ON at the beginning of your stored
procedure? Sometimes this can help with this type of
problem.
Matthew Bando
BandoM@.CSCTGI(remove this).com
>--Original Message--
>Hi all
>When I run a stored procedure using the job scheduler in
>SQL 2000 it takes more time to complete comparing when I
>run it in the Query analyser.
>Is there any reason behind this?
>Example
>I am running a stored Procedure for generating a report
>every one minute using a job scheduler.
>It takes 13 seconds to complete.
>Whereas when I run the same SP in Query Analyser it
takes
>only 2 sec or 3 seconds.
>Please clarify.
>Thanks in advance
>Anand
>.
>

Job Scheduler

Hello,

I am have problems running a couple of jobs. It makes no sense. I have checked and made sure the agent service is running the same user level permissions as I am. I run the job manually from SMS and it works fine.

User is a Windows Login.

Any suggestions would be greatly appreciated.

Date 6/11/2007 6:00:01 AM
Log Job History (BidBackLog)

Step ID 1
Server TWSQLRPTS
Job Name BidBackLog
Step Name Step1
Duration 00:00:21
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: TWDOMAIN\SQLADMIN. ... 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 6:00:01 AM Error: 2007-06-11 06:00:22.50 Code: 0xC0202009 Source: BidBacklog Connection manager "TWSQLRPTS.HomeBASE" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Login failed for user 'TWDOMAIN\SQLADMIN'.". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Cannot open database "HomeBASE" requested by the login. The login failed.". End Error Error: 2007-06-11 06:00:22.50 Code: 0xC020801C Source: DTSTask_DTSDataPumpTask_1 OLE DB Source [1] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager ... The package execution fa... The step failed.

TrussworksLeo1 wrote:

Hello,

I am have problems running a couple of jobs. It makes no sense. I have checked and made sure the agent service is running the same user level permissions as I am. I run the job manually from SMS and it works fine.

User is a Windows Login.

Any suggestions would be greatly appreciated.

Date 6/11/2007 6:00:01 AM
Log Job History (BidBackLog)

Step ID 1
Server TWSQLRPTS
Job Name BidBackLog
Step Name Step1
Duration 00:00:21
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: TWDOMAIN\SQLADMIN. ... 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 6:00:01 AM Error: 2007-06-11 06:00:22.50 Code: 0xC0202009 Source: BidBacklog Connection manager "TWSQLRPTS.HomeBASE" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Login failed for user 'TWDOMAIN\SQLADMIN'.". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Cannot open database "HomeBASE" requested by the login. The login failed.". End Error Error: 2007-06-11 06:00:22.50 Code: 0xC020801C Source: DTSTask_DTSDataPumpTask_1 OLE DB Source [1] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager ... The package execution fa... The step failed.

The user, TWDOMAIN\SQLADMIN doesn't have access to the databases... You're likely using windows authentication for your database connections, and when Agent runs the job, the user account is that of the SQL Server service account. (In this case ...\SQLADMIN)|||

Phil,

Thanks for the reply.

I have checked the permissions. The user is the owner of the databases that it is writting to, but it reads from a database that has mirroring setup. It will not let me change permisssions on that database. Do you know a way around this?

Thanks, Leo

Job Scheduler

To All:
How do you make sure a job does not run until a first step job finishes.
For example you want to make sure a "dbcc CHECKDB" does not run until a
backup job finishes.
Thanks
Tunji
You mean you have 2 seperate jobs and you want to run
them back to back?
What I am aware are 1. combine the 2 jobs into one
or 2. in the second job, check the jobhistory table to
see if the first one finishes or not.
>--Original Message--
>To All:
>How do you make sure a job does not run until a first
step job finishes.
>For example you want to make sure a "dbcc CHECKDB" does
not run until a
>backup job finishes.
>Thanks
>Tunji
>
>.
>
|||Thanks Keene.
Yes, if you have 2 seperate jobs ... I want the second job to run only after
the first job finishes.
Thanks for your response.
"Keene" <anonymous@.discussions.microsoft.com> wrote in message
news:1a7e801c41e3c$55b17220$a501280a@.phx.gbl...
> You mean you have 2 seperate jobs and you want to run
> them back to back?
> What I am aware are 1. combine the 2 jobs into one
> or 2. in the second job, check the jobhistory table to
> see if the first one finishes or not.
> step job finishes.
> not run until a
|||When there are 2 separate jobs, there is no easy way to do this... Even if
you create another job which does an sp_start_job on each of the other jobs,
they will run concurrently. When the first job is started, the next
statement runs...
You can put each of the steps in both jobs into a single job with multiple
steps, then they will run as you wish, but that leaves you with a single
huge job...
Some folks write programs which use SQL DMO to query the status of one job
prior to programmatically starting the second... This is often too much
trouble as well... Most folks simply check the elapsed times of jobs and
adjust the start times occasionally..
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Tunji" <Tunj@.hotmail.com> wrote in message
news:e3ZYXjjHEHA.3696@.TK2MSFTNGP10.phx.gbl...
> To All:
> How do you make sure a job does not run until a first step job finishes.
> For example you want to make sure a "dbcc CHECKDB" does not run until a
> backup job finishes.
> Thanks
> Tunji
>
|||Thanks Wayne!
That was helpful.
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:uDpNCAkHEHA.1528@.TK2MSFTNGP09.phx.gbl...
> When there are 2 separate jobs, there is no easy way to do this... Even
if
> you create another job which does an sp_start_job on each of the other
jobs,
> they will run concurrently. When the first job is started, the next
> statement runs...
> You can put each of the steps in both jobs into a single job with multiple
> steps, then they will run as you wish, but that leaves you with a single
> huge job...
> Some folks write programs which use SQL DMO to query the status of one job
> prior to programmatically starting the second... This is often too much
> trouble as well... Most folks simply check the elapsed times of jobs and
> adjust the start times occasionally..
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Computer Education Services Corporation (CESC), Charlotte, NC
> www.computeredservices.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
>
> "Tunji" <Tunj@.hotmail.com> wrote in message
> news:e3ZYXjjHEHA.3696@.TK2MSFTNGP10.phx.gbl...
>
|||What if i have a job that runs say twice a day (12.00 A.M and 12.00 Noon).
what happens if the 12.00 am job does not finish at 12 noon (next run).
Thanks,
Tunji
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:uDpNCAkHEHA.1528@.TK2MSFTNGP09.phx.gbl...
> When there are 2 separate jobs, there is no easy way to do this... Even
if
> you create another job which does an sp_start_job on each of the other
jobs,
> they will run concurrently. When the first job is started, the next
> statement runs...
> You can put each of the steps in both jobs into a single job with multiple
> steps, then they will run as you wish, but that leaves you with a single
> huge job...
> Some folks write programs which use SQL DMO to query the status of one job
> prior to programmatically starting the second... This is often too much
> trouble as well... Most folks simply check the elapsed times of jobs and
> adjust the start times occasionally..
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Computer Education Services Corporation (CESC), Charlotte, NC
> www.computeredservices.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
>
> "Tunji" <Tunj@.hotmail.com> wrote in message
> news:e3ZYXjjHEHA.3696@.TK2MSFTNGP10.phx.gbl...
>
sql

Job Scheduler

Hello,
Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2 PM for
the first three weeks of the month and for the last week of the month have
the job run every 90 minutes.
Thanks in advance
stone out
I doubt that you can do that via EM. Perhaps you wil, have to run some
script that determines a week's number and changes the schedule accordingly
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:81122877-29AB-4F21-82E0-A0F6F337269D@.microsoft.com...
> Hello,
> Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2 PM for
> the first three weeks of the month and for the last week of the month have
> the job run every 90 minutes.
> Thanks in advance
> stone out
|||You may be able to do this with multiple schedules.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:81122877-29AB-4F21-82E0-A0F6F337269D@.microsoft.com...
> Hello,
> Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2 PM for
> the first three weeks of the month and for the last week of the month have
> the job run every 90 minutes.
> Thanks in advance
> stone out
|||stoney wrote:
> Hello,
> Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2
> PM for the first three weeks of the month and for the last week of
> the month have the job run every 90 minutes.
> Thanks in advance
> stone out
Set up the schedule to run every 90 minutes. Using T-SQL, determine
where you are in the month and complete or terminate the script
accordingly.
David Gugick
Quest Software
www.imceda.com
www.quest.com

job fails through scheduler

I run a DTS job manually, it works fine woth no proble.
However, if I schedule it to run, it always fails
with the following message: ( in the Event Viewer )
Event Type: Warning
Description:
SQL Server Scheduled Job 'BackorderByItemReport'
(0x6C0FDB5A6F7B6149AB8565F9F349FDE4) - Status: Failed -
Invoked on: 2003-09-09 14:44:00 - Message: The job
failed. The Job was invoked by Schedule 2
(BackorderByItemReport). The last step to run was step 1
(BackorderByItemReport).
Since the message doesn't provide enough info, I have no
idea about what's wrong. BTW, I have set up the
SQLServerAgent service running as a network user who is
also a member of the Local System Admin Group.
Has anybody experienced this?
Thanx.
Y.J.Yanjie,
INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/default.aspx?scid=kb;en-us;269074
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Yanjie Ren" <yren@.cc3.com> wrote in message
news:640d01c377aa$773abe30$a501280a@.phx.gbl...
> I run a DTS job manually, it works fine woth no proble.
> However, if I schedule it to run, it always fails
> with the following message: ( in the Event Viewer )
> Event Type: Warning
> Description:
> SQL Server Scheduled Job 'BackorderByItemReport'
> (0x6C0FDB5A6F7B6149AB8565F9F349FDE4) - Status: Failed -
> Invoked on: 2003-09-09 14:44:00 - Message: The job
> failed. The Job was invoked by Schedule 2
> (BackorderByItemReport). The last step to run was step 1
> (BackorderByItemReport).
> Since the message doesn't provide enough info, I have no
> idea about what's wrong. BTW, I have set up the
> SQLServerAgent service running as a network user who is
> also a member of the Local System Admin Group.
> Has anybody experienced this?
> Thanx.
> Y.J.
>

Job failed in Job scheduler

I got the following error messages from a job history. It says that the job
failed. Actually these messages are warning. Id like to make this job
successful in the job history. Is it possible to do that? How can I change i
n
the Job?
Executed as user: WCBDOM01\clusteradmin. ...tact your system administrator.
[SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC print
ed
error messages, contact your system administrator.
[SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC print
ed
error messages, contact your system administrator.
[SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC print
ed
error messages, contact your system administrator.
[SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC print
ed
error messages, contact your system administrator.
[SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC print
ed
error messages, contact your system administrator.
[SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC print
ed
error messages, contact your system administrator.
[SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC print
ed
error messages, contact your system administrator.
[SQLSTATE 01000] (Message 2528) DBCC execu... The step failed.
I ran the following job through scheduler.
BCC DBREINDEX( unq_id )
DBCC DBREINDEX( user_adr )
DBCC DBREINDEX( user_group )
DBCC DBREINDEX( user_slice_approval )
DBCC DBREINDEX( userpriv )
DBCC DBREINDEX( wg )
DBCC DBREINDEX( wg_acc )
DBCC DBREINDEX( wg_dates )
DBCC DBREINDEX( WG_FTE )
Thanks in advance,
Do.
Message posted via http://www.droptable.comA jobstep should only fail if you get errors with severity > 10. I suggest y
ou start by specifying
an output file for the jobstep and post here the contents of that output fil
e. That should give a
more complete picture of the messages returned.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Do Park via droptable.com" <forum@.droptable.com> wrote in message
news:504898D6216E0@.droptable.com...
>I got the following error messages from a job history. It says that the job
> failed. Actually these messages are warning. I'd like to make this job
> successful in the job history. Is it possible to do that? How can I change
in
> the Job?
>
> Executed as user: WCBDOM01\clusteradmin. ...tact your system administrator
.
> [SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC pri
nted
> error messages, contact your system administrator.
> [SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC pri
nted
> error messages, contact your system administrator.
> [SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC pri
nted
> error messages, contact your system administrator.
> [SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC pri
nted
> error messages, contact your system administrator.
> [SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC pri
nted
> error messages, contact your system administrator.
> [SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC pri
nted
> error messages, contact your system administrator.
> [SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC pri
nted
> error messages, contact your system administrator.
> [SQLSTATE 01000] (Message 2528) DBCC execu... The step failed.
>
> I ran the following job through scheduler.
> BCC DBREINDEX( unq_id )
> DBCC DBREINDEX( user_adr )
> DBCC DBREINDEX( user_group )
> DBCC DBREINDEX( user_slice_approval )
> DBCC DBREINDEX( userpriv )
> DBCC DBREINDEX( wg )
> DBCC DBREINDEX( wg_acc )
> DBCC DBREINDEX( wg_dates )
> DBCC DBREINDEX( WG_FTE )
> Thanks in advance,
> Do.
> --
> Message posted via http://www.droptable.com|||I already posted the detailed message in the first note (I posted it here
again).
I know the cause. The messages are warning, but it keeps sending alert every
day. Also, X mark is shown beside the name in the Job in EM.
The last sentence of the message says that [SQLSTATE 01000] (Message 252
8)
DBCC execu... The step failed. I think that the job was not failed. The
last message shouldnt be displayed.
Is there a way to avoid the The step failed message from occurring?
I
The following is the detailed messages.
Executed as user: WCBDOM01\clusteradmin. ...tact your system administrator.
[SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC print
ed
error messages, contact your system administrator.
[SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC print
ed
error messages, contact your system administrator.
[SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC print
ed
error messages, contact your system administrator.
[SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC print
ed
error messages, contact your system administrator.
[SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC print
ed
error messages, contact your system administrator.
[SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC print
ed
error messages, contact your system administrator.
[SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC print
ed
error messages, contact your system administrator.
[SQLSTATE 01000] (Message 2528) DBCC execu... The step failed.
Thanks,
Do.
Message posted via http://www.droptable.com|||So the messages are from the job step output file, not from the job history?
Then I'm out of ideas.
Agent haven't failed jobs with only informational messages in my installatio
ns. You might want to
open a case with MS Support on this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Do Park via droptable.com" <forum@.droptable.com> wrote in message
news:50554B5DE16D0@.droptable.com...
>I already posted the detailed message in the first note (I posted it here
> again).
> I know the cause. The messages are warning, but it keeps sending alert eve
ry
> day. Also, X mark is shown beside the name in the Job in EM.
> The last sentence of the message says that [SQLSTATE 01000] (Message 2
528)
> DBCC execu... The step failed. I think that the job was not failed. The
> last message shouldn't be displayed.
> Is there a way to avoid the "The step failed" message from occurring?
> I
> The following is the detailed messages.
> Executed as user: WCBDOM01\clusteradmin. ...tact your system administrator
.
> [SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC pri
nted
> error messages, contact your system administrator.
> [SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC pri
nted
> error messages, contact your system administrator.
> [SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC pri
nted
> error messages, contact your system administrator.
> [SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC pri
nted
> error messages, contact your system administrator.
> [SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC pri
nted
> error messages, contact your system administrator.
> [SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC pri
nted
> error messages, contact your system administrator.
> [SQLSTATE 01000] (Message 2528) DBCC execution completed. If DBCC pri
nted
> error messages, contact your system administrator.
> [SQLSTATE 01000] (Message 2528) DBCC execu... The step failed.
>
> Thanks,
> Do.
> --
> Message posted via http://www.droptable.com