Database Overwritten: dbs

Showing posts with label dbs. Show all posts

Wednesday, March 21, 2012

Database Migration

Hello.
I'm going to migrate an entrie SQL Server to a new box. The original plan
was to backup and restore all DBs on the new server, but due the long time o
f
the backup I'd like to try other way.
I'm thinking of simply offline->copy->attach .MDF to the new server, but as
the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if a
simple attach is risk-free (basically in terms of systables/sysprocedures) o
r
maybe exist a better way to do it.
What can you advice me?
Thanks
RodrigoBackups should give you much less downtime than you can achieve by
detaching and re-attaching:
1. Database backup on Server A
2. Restore to new Server B
3. Set A to single-user mode
4. Transaction log backup on A
5. Restore transaction log(s) on B
Make sure you read the following article. Particularly the references
to orphaned users:
http://support.microsoft.com/?id=314546
David Portas
SQL Server MVP
--|||Have a look at this article: http://vyaskn.tripod.com/moving_sql_server.htm
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Rodrigo Guerra" <RodrigoGuerra@.discussions.microsoft.com> wrote in message
news:D364210D-6F34-4806-B58F-6DA671E2A248@.microsoft.com...
> Hello.
> I'm going to migrate an entrie SQL Server to a new box. The original plan
> was to backup and restore all DBs on the new server, but due the long time
> of
> the backup I'd like to try other way.
> I'm thinking of simply offline->copy->attach .MDF to the new server, but
> as
> the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if
> a
> simple attach is risk-free (basically in terms of systables/sysprocedures)
> or
> maybe exist a better way to do it.
> What can you advice me?
> Thanks
> Rodrigo|||Thanks David & Narayana; both excellent links.
There they solve the doubt about moving DBs between SQL versions (answer: no
problem).
The orphan users were been considerated too.
Thanks
"Narayana Vyas Kondreddi" wrote:

> Have a look at this article: http://vyaskn.tripod.com/moving_sql...skn.tripod.com/
>
> "Rodrigo Guerra" <RodrigoGuerra@.discussions.microsoft.com> wrote in messag
e
> news:D364210D-6F34-4806-B58F-6DA671E2A248@.microsoft.com...
>
>sql

Database Migration

Hello.
I'm going to migrate an entrie SQL Server to a new box. The original plan
was to backup and restore all DBs on the new server, but due the long time of
the backup I'd like to try other way.
I'm thinking of simply offline->copy->attach .MDF to the new server, but as
the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if a
simple attach is risk-free (basically in terms of systables/sysprocedures) or
maybe exist a better way to do it.
What can you advice me?
Thanks
Rodrigo
Backups should give you much less downtime than you can achieve by
detaching and re-attaching:
1. Database backup on Server A
2. Restore to new Server B
3. Set A to single-user mode
4. Transaction log backup on A
5. Restore transaction log(s) on B
Make sure you read the following article. Particularly the references
to orphaned users:
http://support.microsoft.com/?id=314546
David Portas
SQL Server MVP
|||Have a look at this article: http://vyaskn.tripod.com/moving_sql_server.htm
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Rodrigo Guerra" <RodrigoGuerra@.discussions.microsoft.com> wrote in message
news:D364210D-6F34-4806-B58F-6DA671E2A248@.microsoft.com...
> Hello.
> I'm going to migrate an entrie SQL Server to a new box. The original plan
> was to backup and restore all DBs on the new server, but due the long time
> of
> the backup I'd like to try other way.
> I'm thinking of simply offline->copy->attach .MDF to the new server, but
> as
> the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if
> a
> simple attach is risk-free (basically in terms of systables/sysprocedures)
> or
> maybe exist a better way to do it.
> What can you advice me?
> Thanks
> Rodrigo
|||Thanks David & Narayana; both excellent links.
There they solve the doubt about moving DBs between SQL versions (answer: no
problem).
The orphan users were been considerated too.
Thanks
"Narayana Vyas Kondreddi" wrote:

> Have a look at this article: http://vyaskn.tripod.com/moving_sql_server.htm
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Rodrigo Guerra" <RodrigoGuerra@.discussions.microsoft.com> wrote in message
> news:D364210D-6F34-4806-B58F-6DA671E2A248@.microsoft.com...
>
>

Database Migration

Hello.
I'm going to migrate an entrie SQL Server to a new box. The original plan
was to backup and restore all DBs on the new server, but due the long time of
the backup I'd like to try other way.
I'm thinking of simply offline->copy->attach .MDF to the new server, but as
the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if a
simple attach is risk-free (basically in terms of systables/sysprocedures) or
maybe exist a better way to do it.
What can you advice me?
Thanks
RodrigoBackups should give you much less downtime than you can achieve by
detaching and re-attaching:
1. Database backup on Server A
2. Restore to new Server B
3. Set A to single-user mode
4. Transaction log backup on A
5. Restore transaction log(s) on B
Make sure you read the following article. Particularly the references
to orphaned users:
http://support.microsoft.com/?id=314546
--
David Portas
SQL Server MVP
--|||Have a look at this article: http://vyaskn.tripod.com/moving_sql_server.htm
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Rodrigo Guerra" <RodrigoGuerra@.discussions.microsoft.com> wrote in message
news:D364210D-6F34-4806-B58F-6DA671E2A248@.microsoft.com...
> Hello.
> I'm going to migrate an entrie SQL Server to a new box. The original plan
> was to backup and restore all DBs on the new server, but due the long time
> of
> the backup I'd like to try other way.
> I'm thinking of simply offline->copy->attach .MDF to the new server, but
> as
> the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if
> a
> simple attach is risk-free (basically in terms of systables/sysprocedures)
> or
> maybe exist a better way to do it.
> What can you advice me?
> Thanks
> Rodrigo|||Thanks David & Narayana; both excellent links.
There they solve the doubt about moving DBs between SQL versions (answer: no
problem).
The orphan users were been considerated too.
Thanks
"Narayana Vyas Kondreddi" wrote:
> Have a look at this article: http://vyaskn.tripod.com/moving_sql_server.htm
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Rodrigo Guerra" <RodrigoGuerra@.discussions.microsoft.com> wrote in message
> news:D364210D-6F34-4806-B58F-6DA671E2A248@.microsoft.com...
> > Hello.
> >
> > I'm going to migrate an entrie SQL Server to a new box. The original plan
> > was to backup and restore all DBs on the new server, but due the long time
> > of
> > the backup I'd like to try other way.
> >
> > I'm thinking of simply offline->copy->attach .MDF to the new server, but
> > as
> > the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if
> > a
> > simple attach is risk-free (basically in terms of systables/sysprocedures)
> > or
> > maybe exist a better way to do it.
> >
> > What can you advice me?
> >
> > Thanks
> > Rodrigo
>
>sql

Sunday, March 11, 2012

Database Maintenance Plans

Hello all, I seem to be having some trouble with maintenance plans which
are to backup all my user dbs.
The plan worked before, backing up all the user dbs daily. However,
recently, I have noticed the dbs are not getting backed up. The latest
backup was on Sept. 21, 2004. I have not made any major changes, so I
don't know why the plan stopped working all of a sudden.
If I go to SQL Server Agent > Jobs > Right click on my backup job > View
Job History > Turn on show step details
I see two steps repeated many times
Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
The last step to run was step 1 (Step 1).
Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000] (Error
22029). The step failed.
I have tried creating a new job and set the time to run within a few
minutes, but it does not run. I believe the reason for this is because
under 'Next Run Date' it says (Date and time are not available). I have
also tried simply right clicking the job and clicking Start Job. This
appears to do nothing.
I have looked up numerous MS Knowledge Base articles
(http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
various newsgroup postings, but none seem to really cure my problem.
One thing I have accomplished was backing up the dbs manually using
sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
my job properties > Steps > Edit and found the TSQL script:
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
"d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
-BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
I modified the line to:
sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
"d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
-BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
and ran it in a command prompt. The backups were created without any
problems. So why can't I create backups using Enterprise Manager >
Database Maintenance Plans?
I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
Any help is greatly appreciated.
Thanks,
HarryHave you verified that the SQL Server Agent is running?
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
Hello all, I seem to be having some trouble with maintenance plans which
are to backup all my user dbs.
The plan worked before, backing up all the user dbs daily. However,
recently, I have noticed the dbs are not getting backed up. The latest
backup was on Sept. 21, 2004. I have not made any major changes, so I
don't know why the plan stopped working all of a sudden.
If I go to SQL Server Agent > Jobs > Right click on my backup job > View
Job History > Turn on show step details
I see two steps repeated many times
Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
The last step to run was step 1 (Step 1).
Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000] (Error
22029). The step failed.
I have tried creating a new job and set the time to run within a few
minutes, but it does not run. I believe the reason for this is because
under 'Next Run Date' it says (Date and time are not available). I have
also tried simply right clicking the job and clicking Start Job. This
appears to do nothing.
I have looked up numerous MS Knowledge Base articles
(http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
various newsgroup postings, but none seem to really cure my problem.
One thing I have accomplished was backing up the dbs manually using
sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
my job properties > Steps > Edit and found the TSQL script:
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
"d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
-BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
I modified the line to:
sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
"d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
-BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
and ran it in a command prompt. The backups were created without any
problems. So why can't I create backups using Enterprise Manager >
Database Maintenance Plans?
I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
Any help is greatly appreciated.
Thanks,
Harry|||Yes it is running
On Fri, 8 Oct 2004, Tom Moreau wrote:
> Have you verified that the SQL Server Agent is running?
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
> Hello all, I seem to be having some trouble with maintenance plans which
> are to backup all my user dbs.
> The plan worked before, backing up all the user dbs daily. However,
> recently, I have noticed the dbs are not getting backed up. The latest
> backup was on Sept. 21, 2004. I have not made any major changes, so I
> don't know why the plan stopped working all of a sudden.
> If I go to SQL Server Agent > Jobs > Right click on my backup job > View
> Job History > Turn on show step details
> I see two steps repeated many times
> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
> The last step to run was step 1 (Step 1).
> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000] (Error
> 22029). The step failed.
> I have tried creating a new job and set the time to run within a few
> minutes, but it does not run. I believe the reason for this is because
> under 'Next Run Date' it says (Date and time are not available). I have
> also tried simply right clicking the job and clicking Start Job. This
> appears to do nothing.
> I have looked up numerous MS Knowledge Base articles
> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
> various newsgroup postings, but none seem to really cure my problem.
> One thing I have accomplished was backing up the dbs manually using
> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
> my job properties > Steps > Edit and found the TSQL script:
> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
> I modified the line to:
> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
> and ran it in a command prompt. The backups were created without any
> problems. So why can't I create backups using Enterprise Manager >
> Database Maintenance Plans?
> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
> Any help is greatly appreciated.
> Thanks,
> Harry
>|||Do you have any entries in the SQL Server or SQL Agent error logs - or the
Windows event logs?
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
Yes it is running
On Fri, 8 Oct 2004, Tom Moreau wrote:
> Have you verified that the SQL Server Agent is running?
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
> Hello all, I seem to be having some trouble with maintenance plans which
> are to backup all my user dbs.
> The plan worked before, backing up all the user dbs daily. However,
> recently, I have noticed the dbs are not getting backed up. The latest
> backup was on Sept. 21, 2004. I have not made any major changes, so I
> don't know why the plan stopped working all of a sudden.
> If I go to SQL Server Agent > Jobs > Right click on my backup job > View
> Job History > Turn on show step details
> I see two steps repeated many times
> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
> The last step to run was step 1 (Step 1).
> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000] (Error
> 22029). The step failed.
> I have tried creating a new job and set the time to run within a few
> minutes, but it does not run. I believe the reason for this is because
> under 'Next Run Date' it says (Date and time are not available). I have
> also tried simply right clicking the job and clicking Start Job. This
> appears to do nothing.
> I have looked up numerous MS Knowledge Base articles
> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
> various newsgroup postings, but none seem to really cure my problem.
> One thing I have accomplished was backing up the dbs manually using
> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
> my job properties > Steps > Edit and found the TSQL script:
> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
> I modified the line to:
> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
> and ran it in a command prompt. The backups were created without any
> problems. So why can't I create backups using Enterprise Manager >
> Database Maintenance Plans?
> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
> Any help is greatly appreciated.
> Thanks,
> Harry
>|||There doesn't seem to be any relevant information in the SQL Server log.
For the SQL Agent logs, isn't it what I originally posted? Or do I find
this somewhere else. Windows Event Log gives me:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
(The event ID is 208)
On Fri, 8 Oct 2004, Tom Moreau wrote:
> Do you have any entries in the SQL Server or SQL Agent error logs - or the
> Windows event logs?
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
> Yes it is running
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Have you verified that the SQL Server Agent is running?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
>> Hello all, I seem to be having some trouble with maintenance plans which
>> are to backup all my user dbs.
>> The plan worked before, backing up all the user dbs daily. However,
>> recently, I have noticed the dbs are not getting backed up. The latest
>> backup was on Sept. 21, 2004. I have not made any major changes, so I
>> don't know why the plan stopped working all of a sudden.
>> If I go to SQL Server Agent > Jobs > Right click on my backup job > View
>> Job History > Turn on show step details
>> I see two steps repeated many times
>> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
>> The last step to run was step 1 (Step 1).
>> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000] (Error
>> 22029). The step failed.
>> I have tried creating a new job and set the time to run within a few
>> minutes, but it does not run. I believe the reason for this is because
>> under 'Next Run Date' it says (Date and time are not available). I have
>> also tried simply right clicking the job and clicking Start Job. This
>> appears to do nothing.
>> I have looked up numerous MS Knowledge Base articles
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
>> various newsgroup postings, but none seem to really cure my problem.
>> One thing I have accomplished was backing up the dbs manually using
>> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
>> my job properties > Steps > Edit and found the TSQL script:
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> I modified the line to:
>> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> and ran it in a command prompt. The backups were created without any
>> problems. So why can't I create backups using Enterprise Manager >
>> Database Maintenance Plans?
>> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
>> Any help is greatly appreciated.
>> Thanks,
>> Harry
>>
>|||Right click on SQL Server Agent in EM. Click on Display Error Log. I the
drop-down, select All Types. See if anything pops out.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081307240.1373@.pastpower.net...
There doesn't seem to be any relevant information in the SQL Server log.
For the SQL Agent logs, isn't it what I originally posted? Or do I find
this somewhere else. Windows Event Log gives me:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
(The event ID is 208)
On Fri, 8 Oct 2004, Tom Moreau wrote:
> Do you have any entries in the SQL Server or SQL Agent error logs - or the
> Windows event logs?
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
> Yes it is running
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Have you verified that the SQL Server Agent is running?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
>> Hello all, I seem to be having some trouble with maintenance plans which
>> are to backup all my user dbs.
>> The plan worked before, backing up all the user dbs daily. However,
>> recently, I have noticed the dbs are not getting backed up. The latest
>> backup was on Sept. 21, 2004. I have not made any major changes, so I
>> don't know why the plan stopped working all of a sudden.
>> If I go to SQL Server Agent > Jobs > Right click on my backup job > View
>> Job History > Turn on show step details
>> I see two steps repeated many times
>> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
>> The last step to run was step 1 (Step 1).
>> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000]
(Error
>> 22029). The step failed.
>> I have tried creating a new job and set the time to run within a few
>> minutes, but it does not run. I believe the reason for this is because
>> under 'Next Run Date' it says (Date and time are not available). I have
>> also tried simply right clicking the job and clicking Start Job. This
>> appears to do nothing.
>> I have looked up numerous MS Knowledge Base articles
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
>> various newsgroup postings, but none seem to really cure my problem.
>> One thing I have accomplished was backing up the dbs manually using
>> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
>> my job properties > Steps > Edit and found the TSQL script:
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> I modified the line to:
>> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> and ran it in a command prompt. The backups were created without any
>> problems. So why can't I create backups using Enterprise Manager >
>> Database Maintenance Plans?
>> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
>> Any help is greatly appreciated.
>> Thanks,
>> Harry
>>
>|||Yes
There are 12 information messages and 1 warning. No errors.
Is there anything in particular you are looking for?
On Fri, 8 Oct 2004, Tom Moreau wrote:
> Right click on SQL Server Agent in EM. Click on Display Error Log. I the
> drop-down, select All Types. See if anything pops out.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081307240.1373@.pastpower.net...
> There doesn't seem to be any relevant information in the SQL Server log.
> For the SQL Agent logs, isn't it what I originally posted? Or do I find
> this somewhere else. Windows Event Log gives me:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
> dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
> 2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
> Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
> (The event ID is 208)
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Do you have any entries in the SQL Server or SQL Agent error logs - or the
>> Windows event logs?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
>> Yes it is running
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Have you verified that the SQL Server Agent is running?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
>> Hello all, I seem to be having some trouble with maintenance plans which
>> are to backup all my user dbs.
>> The plan worked before, backing up all the user dbs daily. However,
>> recently, I have noticed the dbs are not getting backed up. The latest
>> backup was on Sept. 21, 2004. I have not made any major changes, so I
>> don't know why the plan stopped working all of a sudden.
>> If I go to SQL Server Agent > Jobs > Right click on my backup job > View
>> Job History > Turn on show step details
>> I see two steps repeated many times
>> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule 1).
>> The last step to run was step 1 (Step 1).
>> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000]
> (Error
>> 22029). The step failed.
>> I have tried creating a new job and set the time to run within a few
>> minutes, but it does not run. I believe the reason for this is because
>> under 'Next Run Date' it says (Date and time are not available). I have
>> also tried simply right clicking the job and clicking Start Job. This
>> appears to do nothing.
>> I have looked up numerous MS Knowledge Base articles
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
>> various newsgroup postings, but none seem to really cure my problem.
>> One thing I have accomplished was backing up the dbs manually using
>> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs > Opened
>> my job properties > Steps > Edit and found the TSQL script:
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> I modified the line to:
>> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> and ran it in a command prompt. The backups were created without any
>> problems. So why can't I create backups using Enterprise Manager >
>> Database Maintenance Plans?
>> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
>> Any help is greatly appreciated.
>> Thanks,
>> Harry
>>
>>
>|||What did the warning say?
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081409270.1410@.pastpower.net...
Yes
There are 12 information messages and 1 warning. No errors.
Is there anything in particular you are looking for?
On Fri, 8 Oct 2004, Tom Moreau wrote:
> Right click on SQL Server Agent in EM. Click on Display Error Log. I the
> drop-down, select All Types. See if anything pops out.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081307240.1373@.pastpower.net...
> There doesn't seem to be any relevant information in the SQL Server log.
> For the SQL Agent logs, isn't it what I originally posted? Or do I find
> this somewhere else. Windows Event Log gives me:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
> dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
> 2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
> Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
> (The event ID is 208)
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Do you have any entries in the SQL Server or SQL Agent error logs - or
the
>> Windows event logs?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
>> Yes it is running
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Have you verified that the SQL Server Agent is running?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
>> Hello all, I seem to be having some trouble with maintenance plans which
>> are to backup all my user dbs.
>> The plan worked before, backing up all the user dbs daily. However,
>> recently, I have noticed the dbs are not getting backed up. The latest
>> backup was on Sept. 21, 2004. I have not made any major changes, so I
>> don't know why the plan stopped working all of a sudden.
>> If I go to SQL Server Agent > Jobs > Right click on my backup job > View
>> Job History > Turn on show step details
>> I see two steps repeated many times
>> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule
1).
>> The last step to run was step 1 (Step 1).
>> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000]
> (Error
>> 22029). The step failed.
>> I have tried creating a new job and set the time to run within a few
>> minutes, but it does not run. I believe the reason for this is because
>> under 'Next Run Date' it says (Date and time are not available). I have
>> also tried simply right clicking the job and clicking Start Job. This
>> appears to do nothing.
>> I have looked up numerous MS Knowledge Base articles
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
>> various newsgroup postings, but none seem to really cure my problem.
>> One thing I have accomplished was backing up the dbs manually using
>> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs >
Opened
>> my job properties > Steps > Edit and found the TSQL script:
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> I modified the line to:
>> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> and ran it in a command prompt. The backups were created without any
>> problems. So why can't I create backups using Enterprise Manager >
>> Database Maintenance Plans?
>> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
>> Any help is greatly appreciated.
>> Thanks,
>> Harry
>>
>>
>|||[396] An idle CPU condition has not been defined - OnIdle job schedules
will have no effect
On Fri, 8 Oct 2004, Tom Moreau wrote:
> What did the warning say?
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081409270.1410@.pastpower.net...
> Yes
> There are 12 information messages and 1 warning. No errors.
> Is there anything in particular you are looking for?
>
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Right click on SQL Server Agent in EM. Click on Display Error Log. I the
>> drop-down, select All Types. See if anything pops out.
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081307240.1373@.pastpower.net...
>> There doesn't seem to be any relevant information in the SQL Server log.
>> For the SQL Agent logs, isn't it what I originally posted? Or do I find
>> this somewhere else. Windows Event Log gives me:
>> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
>> dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
>> 2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
>> Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
>> (The event ID is 208)
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Do you have any entries in the SQL Server or SQL Agent error logs - or
> the
>> Windows event logs?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
>> Yes it is running
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Have you verified that the SQL Server Agent is running?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
>> Hello all, I seem to be having some trouble with maintenance plans which
>> are to backup all my user dbs.
>> The plan worked before, backing up all the user dbs daily. However,
>> recently, I have noticed the dbs are not getting backed up. The latest
>> backup was on Sept. 21, 2004. I have not made any major changes, so I
>> don't know why the plan stopped working all of a sudden.
>> If I go to SQL Server Agent > Jobs > Right click on my backup job > View
>> Job History > Turn on show step details
>> I see two steps repeated many times
>> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule
> 1).
>> The last step to run was step 1 (Step 1).
>> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000]
>> (Error
>> 22029). The step failed.
>> I have tried creating a new job and set the time to run within a few
>> minutes, but it does not run. I believe the reason for this is because
>> under 'Next Run Date' it says (Date and time are not available). I have
>> also tried simply right clicking the job and clicking Start Job. This
>> appears to do nothing.
>> I have looked up numerous MS Knowledge Base articles
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
>> various newsgroup postings, but none seem to really cure my problem.
>> One thing I have accomplished was backing up the dbs manually using
>> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs >
> Opened
>> my job properties > Steps > Edit and found the TSQL script:
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> I modified the line to:
>> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> and ran it in a command prompt. The backups were created without any
>> problems. So why can't I create backups using Enterprise Manager >
>> Database Maintenance Plans?
>> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
>> Any help is greatly appreciated.
>> Thanks,
>> Harry
>>
>>
>>
>|||Can you run other - non-DBMaint - jobs through SQL Agent? I'm trying to
narrow down the scope of the problem.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081433390.1425@.pastpower.net...
[396] An idle CPU condition has not been defined - OnIdle job schedules
will have no effect
On Fri, 8 Oct 2004, Tom Moreau wrote:
> What did the warning say?
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081409270.1410@.pastpower.net...
> Yes
> There are 12 information messages and 1 warning. No errors.
> Is there anything in particular you are looking for?
>
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Right click on SQL Server Agent in EM. Click on Display Error Log. I
the
>> drop-down, select All Types. See if anything pops out.
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081307240.1373@.pastpower.net...
>> There doesn't seem to be any relevant information in the SQL Server log.
>> For the SQL Agent logs, isn't it what I originally posted? Or do I find
>> this somewhere else. Windows Event Log gives me:
>> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
>> dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
>> 2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
>> Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
>> (The event ID is 208)
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Do you have any entries in the SQL Server or SQL Agent error logs - or
> the
>> Windows event logs?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
>> Yes it is running
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Have you verified that the SQL Server Agent is running?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
>> Hello all, I seem to be having some trouble with maintenance plans
which
>> are to backup all my user dbs.
>> The plan worked before, backing up all the user dbs daily. However,
>> recently, I have noticed the dbs are not getting backed up. The latest
>> backup was on Sept. 21, 2004. I have not made any major changes, so I
>> don't know why the plan stopped working all of a sudden.
>> If I go to SQL Server Agent > Jobs > Right click on my backup job >
View
>> Job History > Turn on show step details
>> I see two steps repeated many times
>> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule
> 1).
>> The last step to run was step 1 (Step 1).
>> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000]
>> (Error
>> 22029). The step failed.
>> I have tried creating a new job and set the time to run within a few
>> minutes, but it does not run. I believe the reason for this is because
>> under 'Next Run Date' it says (Date and time are not available). I
have
>> also tried simply right clicking the job and clicking Start Job. This
>> appears to do nothing.
>> I have looked up numerous MS Knowledge Base articles
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
>> various newsgroup postings, but none seem to really cure my problem.
>> One thing I have accomplished was backing up the dbs manually using
>> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs >
> Opened
>> my job properties > Steps > Edit and found the TSQL script:
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> I modified the line to:
>> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> and ran it in a command prompt. The backups were created without any
>> problems. So why can't I create backups using Enterprise Manager >
>> Database Maintenance Plans?
>> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
>> Any help is greatly appreciated.
>> Thanks,
>> Harry
>>
>>
>>
>|||Yes, I believe so.
I have other successfully completed jobs in SQL Server Agent > Jobs
Such as:
Start_Full on Palmas.PagesSearch.[15.6]
Desc: Scheduled full-text full population for full-text Catalog
PagesSearch in database Palmas. This job was created by the full-text
scheduling dialog or full-text index wizard..
SmartRisk Daily Content Expiry
Desc: Execute package: SmartRisk Daily Content Expiry
Which have completed successfully...
On Fri, 8 Oct 2004, Tom Moreau wrote:
> Can you run other - non-DBMaint - jobs through SQL Agent? I'm trying to
> narrow down the scope of the problem.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081433390.1425@.pastpower.net...
> [396] An idle CPU condition has not been defined - OnIdle job schedules
> will have no effect
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> What did the warning say?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081409270.1410@.pastpower.net...
>> Yes
>> There are 12 information messages and 1 warning. No errors.
>> Is there anything in particular you are looking for?
>>
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Right click on SQL Server Agent in EM. Click on Display Error Log. I
> the
>> drop-down, select All Types. See if anything pops out.
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081307240.1373@.pastpower.net...
>> There doesn't seem to be any relevant information in the SQL Server log.
>> For the SQL Agent logs, isn't it what I originally posted? Or do I find
>> this somewhere else. Windows Event Log gives me:
>> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
>> dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked on:
>> 2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
>> Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
>> (The event ID is 208)
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Do you have any entries in the SQL Server or SQL Agent error logs - or
>> the
>> Windows event logs?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
>> Yes it is running
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Have you verified that the SQL Server Agent is running?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
>> Hello all, I seem to be having some trouble with maintenance plans
> which
>> are to backup all my user dbs.
>> The plan worked before, backing up all the user dbs daily. However,
>> recently, I have noticed the dbs are not getting backed up. The latest
>> backup was on Sept. 21, 2004. I have not made any major changes, so I
>> don't know why the plan stopped working all of a sudden.
>> If I go to SQL Server Agent > Jobs > Right click on my backup job >
> View
>> Job History > Turn on show step details
>> I see two steps repeated many times
>> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule
>> 1).
>> The last step to run was step 1 (Step 1).
>> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000]
>> (Error
>> 22029). The step failed.
>> I have tried creating a new job and set the time to run within a few
>> minutes, but it does not run. I believe the reason for this is because
>> under 'Next Run Date' it says (Date and time are not available). I
> have
>> also tried simply right clicking the job and clicking Start Job. This
>> appears to do nothing.
>> I have looked up numerous MS Knowledge Base articles
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
>> various newsgroup postings, but none seem to really cure my problem.
>> One thing I have accomplished was backing up the dbs manually using
>> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs >
>> Opened
>> my job properties > Steps > Edit and found the TSQL script:
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> I modified the line to:
>> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> and ran it in a command prompt. The backups were created without any
>> problems. So why can't I create backups using Enterprise Manager >
>> Database Maintenance Plans?
>> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
>> Any help is greatly appreciated.
>> Thanks,
>> Harry
>>
>>
>>
>>
>|||I get the feeling that somehow, the DLL's relating to DBmaint may be
corrupted. I know you've tried re-doing the job. How about a new, simple
DB maintenance plan - just Northwind, full backup? Does that work?
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081503020.1425@.pastpower.net...
Yes, I believe so.
I have other successfully completed jobs in SQL Server Agent > Jobs
Such as:
Start_Full on Palmas.PagesSearch.[15.6]
Desc: Scheduled full-text full population for full-text Catalog
PagesSearch in database Palmas. This job was created by the full-text
scheduling dialog or full-text index wizard..
SmartRisk Daily Content Expiry
Desc: Execute package: SmartRisk Daily Content Expiry
Which have completed successfully...
On Fri, 8 Oct 2004, Tom Moreau wrote:
> Can you run other - non-DBMaint - jobs through SQL Agent? I'm trying to
> narrow down the scope of the problem.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081433390.1425@.pastpower.net...
> [396] An idle CPU condition has not been defined - OnIdle job schedules
> will have no effect
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> What did the warning say?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081409270.1410@.pastpower.net...
>> Yes
>> There are 12 information messages and 1 warning. No errors.
>> Is there anything in particular you are looking for?
>>
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Right click on SQL Server Agent in EM. Click on Display Error Log. I
> the
>> drop-down, select All Types. See if anything pops out.
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081307240.1373@.pastpower.net...
>> There doesn't seem to be any relevant information in the SQL Server log.
>> For the SQL Agent logs, isn't it what I originally posted? Or do I find
>> this somewhere else. Windows Event Log gives me:
>> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
>> dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked
on:
>> 2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
>> Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
>> (The event ID is 208)
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Do you have any entries in the SQL Server or SQL Agent error logs - or
>> the
>> Windows event logs?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
>> Yes it is running
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Have you verified that the SQL Server Agent is running?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
>> Hello all, I seem to be having some trouble with maintenance plans
> which
>> are to backup all my user dbs.
>> The plan worked before, backing up all the user dbs daily. However,
>> recently, I have noticed the dbs are not getting backed up. The
latest
>> backup was on Sept. 21, 2004. I have not made any major changes, so I
>> don't know why the plan stopped working all of a sudden.
>> If I go to SQL Server Agent > Jobs > Right click on my backup job >
> View
>> Job History > Turn on show step details
>> I see two steps repeated many times
>> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule
>> 1).
>> The last step to run was step 1 (Step 1).
>> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000]
>> (Error
>> 22029). The step failed.
>> I have tried creating a new job and set the time to run within a few
>> minutes, but it does not run. I believe the reason for this is
because
>> under 'Next Run Date' it says (Date and time are not available). I
> have
>> also tried simply right clicking the job and clicking Start Job. This
>> appears to do nothing.
>> I have looked up numerous MS Knowledge Base articles
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
>> various newsgroup postings, but none seem to really cure my problem.
>> One thing I have accomplished was backing up the dbs manually using
>> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs >
>> Opened
>> my job properties > Steps > Edit and found the TSQL script:
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> I modified the line to:
>> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> and ran it in a command prompt. The backups were created without any
>> problems. So why can't I create backups using Enterprise Manager >
>> Database Maintenance Plans?
>> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
>> Any help is greatly appreciated.
>> Thanks,
>> Harry
>>
>>
>>
>>
>|||No, I tried that too before but with a different database.
I also tried it again now with Northwind.
It does not seem to execute. Under next run date it says dat and time are
not available. I also tried right clicking on the job and pressing start
job. Nothing seemed to happen...
On Fri, 8 Oct 2004, Tom Moreau wrote:
> I get the feeling that somehow, the DLL's relating to DBmaint may be
> corrupted. I know you've tried re-doing the job. How about a new, simple
> DB maintenance plan - just Northwind, full backup? Does that work?
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081503020.1425@.pastpower.net...
> Yes, I believe so.
> I have other successfully completed jobs in SQL Server Agent > Jobs
> Such as:
> Start_Full on Palmas.PagesSearch.[15.6]
> Desc: Scheduled full-text full population for full-text Catalog
> PagesSearch in database Palmas. This job was created by the full-text
> scheduling dialog or full-text index wizard..
> SmartRisk Daily Content Expiry
> Desc: Execute package: SmartRisk Daily Content Expiry
> Which have completed successfully...
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Can you run other - non-DBMaint - jobs through SQL Agent? I'm trying to
>> narrow down the scope of the problem.
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081433390.1425@.pastpower.net...
>> [396] An idle CPU condition has not been defined - OnIdle job schedules
>> will have no effect
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> What did the warning say?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081409270.1410@.pastpower.net...
>> Yes
>> There are 12 information messages and 1 warning. No errors.
>> Is there anything in particular you are looking for?
>>
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Right click on SQL Server Agent in EM. Click on Display Error Log. I
>> the
>> drop-down, select All Types. See if anything pops out.
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081307240.1373@.pastpower.net...
>> There doesn't seem to be any relevant information in the SQL Server log.
>> For the SQL Agent logs, isn't it what I originally posted? Or do I find
>> this somewhere else. Windows Event Log gives me:
>> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
>> dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked
> on:
>> 2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
>> Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
>> (The event ID is 208)
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Do you have any entries in the SQL Server or SQL Agent error logs - or
>> the
>> Windows event logs?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
>> Yes it is running
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Have you verified that the SQL Server Agent is running?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
>> Hello all, I seem to be having some trouble with maintenance plans
>> which
>> are to backup all my user dbs.
>> The plan worked before, backing up all the user dbs daily. However,
>> recently, I have noticed the dbs are not getting backed up. The
> latest
>> backup was on Sept. 21, 2004. I have not made any major changes, so I
>> don't know why the plan stopped working all of a sudden.
>> If I go to SQL Server Agent > Jobs > Right click on my backup job >
>> View
>> Job History > Turn on show step details
>> I see two steps repeated many times
>> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule
>> 1).
>> The last step to run was step 1 (Step 1).
>> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000]
>> (Error
>> 22029). The step failed.
>> I have tried creating a new job and set the time to run within a few
>> minutes, but it does not run. I believe the reason for this is
> because
>> under 'Next Run Date' it says (Date and time are not available). I
>> have
>> also tried simply right clicking the job and clicking Start Job. This
>> appears to do nothing.
>> I have looked up numerous MS Knowledge Base articles
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
>> various newsgroup postings, but none seem to really cure my problem.
>> One thing I have accomplished was backing up the dbs manually using
>> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs >
>> Opened
>> my job properties > Steps > Edit and found the TSQL script:
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> I modified the line to:
>> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> and ran it in a command prompt. The backups were created without any
>> problems. So why can't I create backups using Enterprise Manager >
>> Database Maintenance Plans?
>> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
>> Any help is greatly appreciated.
>> Thanks,
>> Harry
>>
>>
>>
>>
>>
>|||I think you're gonna have to open a ticket with Product Support Services.
It sounds like something has been corrupted.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Harry Kim" <heri0n@.pastpower.net> wrote in message
news:Pine.LNX.4.60.0410081547010.1425@.pastpower.net...
No, I tried that too before but with a different database.
I also tried it again now with Northwind.
It does not seem to execute. Under next run date it says dat and time are
not available. I also tried right clicking on the job and pressing start
job. Nothing seemed to happen...
On Fri, 8 Oct 2004, Tom Moreau wrote:
> I get the feeling that somehow, the DLL's relating to DBmaint may be
> corrupted. I know you've tried re-doing the job. How about a new, simple
> DB maintenance plan - just Northwind, full backup? Does that work?
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Harry Kim" <heri0n@.pastpower.net> wrote in message
> news:Pine.LNX.4.60.0410081503020.1425@.pastpower.net...
> Yes, I believe so.
> I have other successfully completed jobs in SQL Server Agent > Jobs
> Such as:
> Start_Full on Palmas.PagesSearch.[15.6]
> Desc: Scheduled full-text full population for full-text Catalog
> PagesSearch in database Palmas. This job was created by the full-text
> scheduling dialog or full-text index wizard..
> SmartRisk Daily Content Expiry
> Desc: Execute package: SmartRisk Daily Content Expiry
> Which have completed successfully...
> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Can you run other - non-DBMaint - jobs through SQL Agent? I'm trying to
>> narrow down the scope of the problem.
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081433390.1425@.pastpower.net...
>> [396] An idle CPU condition has not been defined - OnIdle job schedules
>> will have no effect
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> What did the warning say?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081409270.1410@.pastpower.net...
>> Yes
>> There are 12 information messages and 1 warning. No errors.
>> Is there anything in particular you are looking for?
>>
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Right click on SQL Server Agent in EM. Click on Display Error Log. I
>> the
>> drop-down, select All Types. See if anything pops out.
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081307240.1373@.pastpower.net...
>> There doesn't seem to be any relevant information in the SQL Server
log.
>> For the SQL Agent logs, isn't it what I originally posted? Or do I
find
>> this somewhere else. Windows Event Log gives me:
>> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'user
>> dbs'' (0x9AC86DAEC2694A469BADFCFAD9063C53) - Status: Failed - Invoked
> on:
>> 2004-10-08 01:00:00 - Message: The job failed. The Job was invoked by
>> Schedule 30 (Schedule 1). The last step to run was step 1 (Step 1).
>> (The event ID is 208)
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Do you have any entries in the SQL Server or SQL Agent error logs - or
>> the
>> Windows event logs?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081204240.1323@.pastpower.net...
>> Yes it is running
>> On Fri, 8 Oct 2004, Tom Moreau wrote:
>> Have you verified that the SQL Server Agent is running?
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "Harry Kim" <heri0n@.pastpower.net> wrote in message
>> news:Pine.LNX.4.60.0410081056070.1087@.pastpower.net...
>> Hello all, I seem to be having some trouble with maintenance plans
>> which
>> are to backup all my user dbs.
>> The plan worked before, backing up all the user dbs daily. However,
>> recently, I have noticed the dbs are not getting backed up. The
> latest
>> backup was on Sept. 21, 2004. I have not made any major changes, so
I
>> don't know why the plan stopped working all of a sudden.
>> If I go to SQL Server Agent > Jobs > Right click on my backup job >
>> View
>> Job History > Turn on show step details
>> I see two steps repeated many times
>> Step 0: The job failed. The Job was invoked by Schedule 30 (Schedule
>> 1).
>> The last step to run was step 1 (Step 1).
>> Step 1: Executed as user: sa. sqlmaint.exe failed. [SQLSTATE 42000]
>> (Error
>> 22029). The step failed.
>> I have tried creating a new job and set the time to run within a few
>> minutes, but it does not run. I believe the reason for this is
> because
>> under 'Next Run Date' it says (Date and time are not available). I
>> have
>> also tried simply right clicking the job and clicking Start Job.
This
>> appears to do nothing.
>> I have looked up numerous MS Knowledge Base articles
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;288577) and
>> various newsgroup postings, but none seem to really cure my problem.
>> One thing I have accomplished was backing up the dbs manually using
>> sqlmaint in a command prompt. I went to SQL Server Agent > Jobs >
>> Opened
>> my job properties > Steps > Edit and found the TSQL script:
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> I modified the line to:
>> sqlmaint -PlanID 1D626322-E403-4065-A37C-EE5F8B9BC2E0 -To "hkim" -Rpt
>> "d:\mssqldata\MSSQL\LOG\user dbs4.txt" -DelTxtRpt 4DAYS -WriteHistory
>> -BkUpMedia DISK -BkUpDB "E:\sqlback" -DelBkUps 3DAYS -BkExt "BAK"'
>> and ran it in a command prompt. The backups were created without any
>> problems. So why can't I create backups using Enterprise Manager >
>> Database Maintenance Plans?
>> I am running MS-SQL 2000 (8.00.760) on Windows 2000 Server.
>> Any help is greatly appreciated.
>> Thanks,
>> Harry
>>
>>
>>
>>
>>
>

Wednesday, March 21, 2012

Database Migration

Database Migration

Database Migration

Sunday, March 11, 2012

Database Maintenance Plans

Database Maintenance Plans

Database Overwritten

Blog Archive

About Me