maintenance plan wizard: backups

Showing posts with label backups. Show all posts

Wednesday, March 28, 2012

Making the Log file small

backups shrink the logical space, not physical...
try backup log with the no_log clause, then shrink the file
Tina wrote:
> I'm using ss2005 and Management Studio...
> I have this huge log file and I want it to be small. I read that if I do
a
> transaction backup that it will make it small. That did give it 90% free
> space. So then I did a shrink (all three types) but that did not shrink i
t
> at all. I did a database shrink and that did nothing.
> Then I read that if I detach it, delete the log file (I just moved it), an
d
> reattach it that a new small log file will be built. But, the reattach
> would not work saying that the log file is missing. So I had to move it
> back and now I still have this huge log file.
> How can I make it small?
> Thanks,
> TI'm using ss2005 and Management Studio...
I have this huge log file and I want it to be small. I read that if I do a
transaction backup that it will make it small. That did give it 90% free
space. So then I did a shrink (all three types) but that did not shrink it
at all. I did a database shrink and that did nothing.
Then I read that if I detach it, delete the log file (I just moved it), and
reattach it that a new small log file will be built. But, the reattach
would not work saying that the log file is missing. So I had to move it
back and now I still have this huge log file.
How can I make it small?
Thanks,
T|||backups shrink the logical space, not physical...
try backup log with the no_log clause, then shrink the file
Tina wrote:
> I'm using ss2005 and Management Studio...
> I have this huge log file and I want it to be small. I read that if I do
a
> transaction backup that it will make it small. That did give it 90% free
> space. So then I did a shrink (all three types) but that did not shrink i
t
> at all. I did a database shrink and that did nothing.
> Then I read that if I detach it, delete the log file (I just moved it), an
d
> reattach it that a new small log file will be built. But, the reattach
> would not work saying that the log file is missing. So I had to move it
> back and now I still have this huge log file.
> How can I make it small?
> Thanks,
> T|||After you backup your log file, you can shrink the file with DBCC
SHRINKFILE. For example:
DBCC SHRINKFILE('MyDatabase_Log', 100)
See the SQL Server Books Online for more info on DBCC SHRINKFILE.
The most common cause of out-of-control log files is failure to implement a
backup/recovery plan. If you choose to run the database in the
FULL/BULK_LOGGED recovery model, you will need to do regular transaction log
backups to keep the log size reasonable and provide the means to minimize
data loss after a failure. You can also run the database in the SIMPLE
recovery model so that you don't need to bother with log backups. However,
your only recovery recourse in the SIMPLE model is to restore from the last
full backup.
Hope this helps.
Dan Guzman
SQL Server MVP
"Tina" <tinamseaburn@.nospammeexcite.com> wrote in message
news:Oj5uSqvmGHA.4772@.TK2MSFTNGP04.phx.gbl...
> I'm using ss2005 and Management Studio...
> I have this huge log file and I want it to be small. I read that if I do
> a transaction backup that it will make it small. That did give it 90%
> free space. So then I did a shrink (all three types) but that did not
> shrink it at all. I did a database shrink and that did nothing.
> Then I read that if I detach it, delete the log file (I just moved it),
> and reattach it that a new small log file will be built. But, the
> reattach would not work saying that the log file is missing. So I had to
> move it back and now I still have this huge log file.
> How can I make it small?
> Thanks,
> T
>|||After you backup your log file, you can shrink the file with DBCC
SHRINKFILE. For example:
DBCC SHRINKFILE('MyDatabase_Log', 100)
See the SQL Server Books Online for more info on DBCC SHRINKFILE.
The most common cause of out-of-control log files is failure to implement a
backup/recovery plan. If you choose to run the database in the
FULL/BULK_LOGGED recovery model, you will need to do regular transaction log
backups to keep the log size reasonable and provide the means to minimize
data loss after a failure. You can also run the database in the SIMPLE
recovery model so that you don't need to bother with log backups. However,
your only recovery recourse in the SIMPLE model is to restore from the last
full backup.
Hope this helps.
Dan Guzman
SQL Server MVP
"Tina" <tinamseaburn@.nospammeexcite.com> wrote in message
news:Oj5uSqvmGHA.4772@.TK2MSFTNGP04.phx.gbl...
> I'm using ss2005 and Management Studio...
> I have this huge log file and I want it to be small. I read that if I do
> a transaction backup that it will make it small. That did give it 90%
> free space. So then I did a shrink (all three types) but that did not
> shrink it at all. I did a database shrink and that did nothing.
> Then I read that if I detach it, delete the log file (I just moved it),
> and reattach it that a new small log file will be built. But, the
> reattach would not work saying that the log file is missing. So I had to
> move it back and now I still have this huge log file.
> How can I make it small?
> Thanks,
> T
>|||http://www.karaszi.com/SQLServer/info_dont_shrink.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tina" <tinamseaburn@.nospammeexcite.com> wrote in message
news:Oj5uSqvmGHA.4772@.TK2MSFTNGP04.phx.gbl...
> I'm using ss2005 and Management Studio...
> I have this huge log file and I want it to be small. I read that if I do
a transaction backup
> that it will make it small. That did give it 90% free space. So then I d
id a shrink (all three
> types) but that did not shrink it at all. I did a database shrink and tha
t did nothing.
> Then I read that if I detach it, delete the log file (I just moved it), an
d reattach it that a new
> small log file will be built. But, the reattach would not work saying tha
t the log file is
> missing. So I had to move it back and now I still have this huge log fil
e.
> How can I make it small?
> Thanks,
> T
>|||http://www.karaszi.com/SQLServer/info_dont_shrink.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tina" <tinamseaburn@.nospammeexcite.com> wrote in message
news:Oj5uSqvmGHA.4772@.TK2MSFTNGP04.phx.gbl...
> I'm using ss2005 and Management Studio...
> I have this huge log file and I want it to be small. I read that if I do
a transaction backup
> that it will make it small. That did give it 90% free space. So then I d
id a shrink (all three
> types) but that did not shrink it at all. I did a database shrink and tha
t did nothing.
> Then I read that if I detach it, delete the log file (I just moved it), an
d reattach it that a new
> small log file will be built. But, the reattach would not work saying tha
t the log file is
> missing. So I had to move it back and now I still have this huge log fil
e.
> How can I make it small?
> Thanks,
> T
>sql

Friday, March 9, 2012

Maitenance Job

In my Maintenance job I specify to keep the BAK and TRN backups for 1 week.
BAK files are delted that are older than this, however the TRN backups are
not deleted. Why is this and how can I resolve it?Hi ,
Typically, the size of the transaction log file stabilizes when it can hold
the maximum number of transactions that can occur between transaction log
truncations that either checkpoints or transaction log backups trigger.
However, in some situations the transaction log may become very large and
run out of space or become full.
For more information, please refer to:
317375 A transaction log grows unexpectedly or becomes full on a computer
that is running SQL Server
http://support.microsoft.com/default.aspx?scid=kb;EN-US;317375
Best regards,
Vincent Xu
Microsoft Online Partner Support
======================================================Get Secure! - www.microsoft.com/security
======================================================When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================>>Thread-Topic: Maitenance Job
>>thread-index: AcZn26C5VxQ5EMvgQt6cXAn7hAS36A==>>X-WBNR-Posting-Host: 209.244.152.162
>>From: =?Utf-8?B?R2VvcmdlIFNjaG5laWRlcg==?=<georgedschneider@.news.postalias>
>>Subject: Maitenance Job
>>Date: Mon, 24 Apr 2006 13:14:01 -0700
>>Lines: 3
>>Message-ID: <E2EDCF6E-06F1-4FB2-9918-D80D57D971AF@.microsoft.com>
>>MIME-Version: 1.0
>>Content-Type: text/plain;
>> charset="Utf-8"
>>Content-Transfer-Encoding: 7bit
>>X-Newsreader: Microsoft CDO for Windows 2000
>>Content-Class: urn:content-classes:message
>>Importance: normal
>>Priority: normal
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>>Newsgroups: microsoft.public.sqlserver.server
>>Path: TK2MSFTNGXA01.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:429048
>>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>In my Maintenance job I specify to keep the BAK and TRN backups for 1
week.
>>BAK files are delted that are older than this, however the TRN backups
are
>>not deleted. Why is this and how can I resolve it?|||Did you include databases in simple recovery model in the maint plan?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"George Schneider" <georgedschneider@.news.postalias> wrote in message
news:E2EDCF6E-06F1-4FB2-9918-D80D57D971AF@.microsoft.com...
> In my Maintenance job I specify to keep the BAK and TRN backups for 1 week.
> BAK files are delted that are older than this, however the TRN backups are
> not deleted. Why is this and how can I resolve it?|||what do you mean by simple recovery model
"Tibor Karaszi" wrote:
> Did you include databases in simple recovery model in the maint plan?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "George Schneider" <georgedschneider@.news.postalias> wrote in message
> news:E2EDCF6E-06F1-4FB2-9918-D80D57D971AF@.microsoft.com...
> > In my Maintenance job I specify to keep the BAK and TRN backups for 1 week.
> > BAK files are delted that are older than this, however the TRN backups are
> > not deleted. Why is this and how can I resolve it?
>
>|||The tranactions logs are only like 84 kb when they are backuped up.
"George Schneider" wrote:
> In my Maintenance job I specify to keep the BAK and TRN backups for 1 week.
> BAK files are delted that are older than this, however the TRN backups are
> not deleted. Why is this and how can I resolve it?|||This is very well documented in Books Online (BOL), and I suggest you take the time to learn those
concepts:
BOL 2000, search for "Selecting a Recovery Model"
BOL 2005, search for "Choosing the Recovery Model for a Database"
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"George Schneider" <georgedschneider@.news.postalias> wrote in message
news:1EE7026E-7AB5-41E7-B5E6-F474B3B6A9E0@.microsoft.com...
> what do you mean by simple recovery model
> "Tibor Karaszi" wrote:
>> Did you include databases in simple recovery model in the maint plan?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "George Schneider" <georgedschneider@.news.postalias> wrote in message
>> news:E2EDCF6E-06F1-4FB2-9918-D80D57D971AF@.microsoft.com...
>> > In my Maintenance job I specify to keep the BAK and TRN backups for 1 week.
>> > BAK files are delted that are older than this, however the TRN backups are
>> > not deleted. Why is this and how can I resolve it?
>>|||Hi George ,
How is everything going? Let me know if you still have concerns.
Have a good day.
Best regards,
Vincent Xu
Microsoft Online Partner Support
======================================================Get Secure! - www.microsoft.com/security
======================================================When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================>>Thread-Topic: Maitenance Job
>>thread-index: AcZoZcp6c/Q/UTZhQfOLwJIjZnhIqA==>>X-WBNR-Posting-Host: 209.244.152.162
>>From: =?Utf-8?B?R2VvcmdlIFNjaG5laWRlcg==?=<georgedschneider@.news.postalias>
>>References: <E2EDCF6E-06F1-4FB2-9918-D80D57D971AF@.microsoft.com>
>>Subject: RE: Maitenance Job
>>Date: Tue, 25 Apr 2006 05:43:02 -0700
>>Lines: 7
>>Message-ID: <C88CCAF2-A7E1-409B-96BA-11C7F6B060F0@.microsoft.com>
>>MIME-Version: 1.0
>>Content-Type: text/plain;
>> charset="Utf-8"
>>Content-Transfer-Encoding: 7bit
>>X-Newsreader: Microsoft CDO for Windows 2000
>>Content-Class: urn:content-classes:message
>>Importance: normal
>>Priority: normal
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>>Newsgroups: microsoft.public.sqlserver.server
>>Path: TK2MSFTNGXA01.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:429121
>>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>The tranactions logs are only like 84 kb when they are backuped up.
>>"George Schneider" wrote:
>> In my Maintenance job I specify to keep the BAK and TRN backups for 1
week.
>> BAK files are delted that are older than this, however the TRN backups
are
>> not deleted. Why is this and how can I resolve it?

Wednesday, March 7, 2012

Maintenance plans not deleting old transaction log backups

I'm the dba for a large company and have setup many maintenance plans for our sql servers. One of the options I have set is to delete old backups of databases and transaction logs after 2 days. For some reason, the old database backups are being deleted, but the old transaction logs backups are not. I have them being put in the same directory. Anybody have any ideas why this is happening and what if any fix is available?

Those are separate items that you check off in the options for each step - are you sure you asked the wizard to do that? If possible, drop the old plans and recreate them, checking that section to make sure you select that option.

Other than missing the check box, I don't know what else might cause this. Both delete operations use the same delete stored procedure, so if one works, the other one should.

If you do change your plans and this happens again, check the event logs and the SQL Server error logs.

Maintenance Plans Disappear

I recently restored 3 databases. The maintenance plans responsible for
creating the backups for those databases appear to have disappeared after th
e
restoration. I deleted the databases prior to restoration, but did not touc
h
the plans.
Is there a way to make sure that the next time I have to restore the
databases that the plans do not get removed? Is there a way to backup or
export the maintenance plans?
Thanks
MarkDid you restore msdb? Or did you perform a rebuild of the system databases?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Mark Coffman" <MarkCoffman@.discussions.microsoft.com> wrote in message
news:970287BA-384C-49A8-BA53-26E1BE124F57@.microsoft.com...
>I recently restored 3 databases. The maintenance plans responsible for
> creating the backups for those databases appear to have disappeared after
the
> restoration. I deleted the databases prior to restoration, but did not to
uch
> the plans.
> Is there a way to make sure that the next time I have to restore the
> databases that the plans do not get removed? Is there a way to backup or
> export the maintenance plans?
> Thanks
> Mark
>

Maintenance Plans Disappear

I recently restored 3 databases. The maintenance plans responsible for
creating the backups for those databases appear to have disappeared after the
restoration. I deleted the databases prior to restoration, but did not touch
the plans.
Is there a way to make sure that the next time I have to restore the
databases that the plans do not get removed? Is there a way to backup or
export the maintenance plans?
Thanks
MarkDid you restore msdb? Or did you perform a rebuild of the system databases?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Mark Coffman" <MarkCoffman@.discussions.microsoft.com> wrote in message
news:970287BA-384C-49A8-BA53-26E1BE124F57@.microsoft.com...
>I recently restored 3 databases. The maintenance plans responsible for
> creating the backups for those databases appear to have disappeared after the
> restoration. I deleted the databases prior to restoration, but did not touch
> the plans.
> Is there a way to make sure that the next time I have to restore the
> databases that the plans do not get removed? Is there a way to backup or
> export the maintenance plans?
> Thanks
> Mark
>

Maintenance Plans Disappear

I recently restored 3 databases. The maintenance plans responsible for
creating the backups for those databases appear to have disappeared after the
restoration. I deleted the databases prior to restoration, but did not touch
the plans.
Is there a way to make sure that the next time I have to restore the
databases that the plans do not get removed? Is there a way to backup or
export the maintenance plans?
Thanks
Mark
Did you restore msdb? Or did you perform a rebuild of the system databases?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Mark Coffman" <MarkCoffman@.discussions.microsoft.com> wrote in message
news:970287BA-384C-49A8-BA53-26E1BE124F57@.microsoft.com...
>I recently restored 3 databases. The maintenance plans responsible for
> creating the backups for those databases appear to have disappeared after the
> restoration. I deleted the databases prior to restoration, but did not touch
> the plans.
> Is there a way to make sure that the next time I have to restore the
> databases that the plans do not get removed? Is there a way to backup or
> export the maintenance plans?
> Thanks
> Mark
>

Saturday, February 25, 2012

Maintenance Plans and Integrity checks

Just inherited a couple os SQL V7 servers and am reviewing the backups they
have been doing. New to SQL server.
In Enterprise Manager in the plan window I see two intregrity options
1) check database integrity (which is not checked)
2) verify the intergrity of the backup upon completion (checked)
What is number 2 doing?
If #1 is not checked, it seems to me their is no DBCC being run. So far I
cannot get their ops dept to send me the job logs for these backups so at
this point want to make sure from what I can see in Enterprise Manager that
they are running consistancy checks.
Thanks
Mike Lackey
Database Adminstration
Sybase/Oracle and enthusiastically trying to learn MSSQL
If #1 is not checked and there are no other jobs doing this that means there
are no DBCC CHECKDB's being run.
#2 refers to issuing a Verify against the backup after it completes and does
not pertain to DBCC's.
Andrew J. Kelly SQL MVP
"Mike Lackey" <MikeLackey@.discussions.microsoft.com> wrote in message
news:15060A70-AAE2-43D4-86C5-CCC0B08483A8@.microsoft.com...
> Just inherited a couple os SQL V7 servers and am reviewing the backups
they
> have been doing. New to SQL server.
> In Enterprise Manager in the plan window I see two intregrity options
> 1) check database integrity (which is not checked)
> 2) verify the intergrity of the backup upon completion (checked)
> What is number 2 doing?
> If #1 is not checked, it seems to me their is no DBCC being run. So far I
> cannot get their ops dept to send me the job logs for these backups so at
> this point want to make sure from what I can see in Enterprise Manager
that
> they are running consistancy checks.
> Thanks
> --
> Mike Lackey
> Database Adminstration
> Sybase/Oracle and enthusiastically trying to learn MSSQL

Maintenance Plans and Integrity checks

Just inherited a couple os SQL V7 servers and am reviewing the backups they
have been doing. New to SQL server.
In Enterprise Manager in the plan window I see two intregrity options
1) check database integrity (which is not checked)
2) verify the intergrity of the backup upon completion (checked)
What is number 2 doing?
If #1 is not checked, it seems to me their is no DBCC being run. So far I
cannot get their ops dept to send me the job logs for these backups so at
this point want to make sure from what I can see in Enterprise Manager that
they are running consistancy checks.
Thanks
--
Mike Lackey
Database Adminstration
Sybase/Oracle and enthusiastically trying to learn MSSQLIf #1 is not checked and there are no other jobs doing this that means there
are no DBCC CHECKDB's being run.
#2 refers to issuing a Verify against the backup after it completes and does
not pertain to DBCC's.
--
Andrew J. Kelly SQL MVP
"Mike Lackey" <MikeLackey@.discussions.microsoft.com> wrote in message
news:15060A70-AAE2-43D4-86C5-CCC0B08483A8@.microsoft.com...
> Just inherited a couple os SQL V7 servers and am reviewing the backups
they
> have been doing. New to SQL server.
> In Enterprise Manager in the plan window I see two intregrity options
> 1) check database integrity (which is not checked)
> 2) verify the intergrity of the backup upon completion (checked)
> What is number 2 doing?
> If #1 is not checked, it seems to me their is no DBCC being run. So far I
> cannot get their ops dept to send me the job logs for these backups so at
> this point want to make sure from what I can see in Enterprise Manager
that
> they are running consistancy checks.
> Thanks
> --
> Mike Lackey
> Database Adminstration
> Sybase/Oracle and enthusiastically trying to learn MSSQL

Maintenance Plans and cleaning up backups in subfolders...

The maintenance job I have creates sub-folders for each database when it
backups.
The Cleanup Job is pointing to the root of this folder but it's not deleting
previous backups. It's set to delete files older than 2 days.
Does this not supported by the SQL2K5?
Should I not set it to create folders for each database backup?
Thanks in advance...With sp1, you have an option to recurse sub-folders. also, there has been lots of work on maint
plans in sp2.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Artunc" <artunc_u2@.hotmail.com> wrote in message
news:60572E3A-8C37-4236-A7DE-7E16EE73292D@.microsoft.com...
> The maintenance job I have creates sub-folders for each database when it
> backups.
> The Cleanup Job is pointing to the root of this folder but it's not deleting
> previous backups. It's set to delete files older than 2 days.
> Does this not supported by the SQL2K5?
> Should I not set it to create folders for each database backup?
> Thanks in advance...|||Do you know where can I enable this option?
"Tibor Karaszi" wrote:
> With sp1, you have an option to recurse sub-folders. also, there has been lots of work on maint
> plans in sp2.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Artunc" <artunc_u2@.hotmail.com> wrote in message
> news:60572E3A-8C37-4236-A7DE-7E16EE73292D@.microsoft.com...
> >
> > The maintenance job I have creates sub-folders for each database when it
> > backups.
> > The Cleanup Job is pointing to the root of this folder but it's not deleting
> > previous backups. It's set to delete files older than 2 days.
> >
> > Does this not supported by the SQL2K5?
> > Should I not set it to create folders for each database backup?
> >
> > Thanks in advance...
>|||It is in the cleanup task. You have to open it in the maintenance plan
editor and you will see it.
--
Andrew J. Kelly SQL MVP
"Artunc" <artunc_u2@.hotmail.com> wrote in message
news:201DF41C-9E0C-44A2-9582-332E33E25A09@.microsoft.com...
> Do you know where can I enable this option?
> "Tibor Karaszi" wrote:
>> With sp1, you have an option to recurse sub-folders. also, there has been
>> lots of work on maint
>> plans in sp2.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Artunc" <artunc_u2@.hotmail.com> wrote in message
>> news:60572E3A-8C37-4236-A7DE-7E16EE73292D@.microsoft.com...
>> >
>> > The maintenance job I have creates sub-folders for each database when
>> > it
>> > backups.
>> > The Cleanup Job is pointing to the root of this folder but it's not
>> > deleting
>> > previous backups. It's set to delete files older than 2 days.
>> >
>> > Does this not supported by the SQL2K5?
>> > Should I not set it to create folders for each database backup?
>> >
>> > Thanks in advance...
>>|||I don't see it in there, I'm running SP1.
Do I need to install SP2 to see it?
"Andrew J. Kelly" wrote:
> It is in the cleanup task. You have to open it in the maintenance plan
> editor and you will see it.
> --
> Andrew J. Kelly SQL MVP
> "Artunc" <artunc_u2@.hotmail.com> wrote in message
> news:201DF41C-9E0C-44A2-9582-332E33E25A09@.microsoft.com...
> >
> > Do you know where can I enable this option?
> >
> > "Tibor Karaszi" wrote:
> >
> >> With sp1, you have an option to recurse sub-folders. also, there has been
> >> lots of work on maint
> >> plans in sp2.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://sqlblog.com/blogs/tibor_karaszi
> >>
> >>
> >> "Artunc" <artunc_u2@.hotmail.com> wrote in message
> >> news:60572E3A-8C37-4236-A7DE-7E16EE73292D@.microsoft.com...
> >> >
> >> > The maintenance job I have creates sub-folders for each database when
> >> > it
> >> > backups.
> >> > The Cleanup Job is pointing to the root of this folder but it's not
> >> > deleting
> >> > previous backups. It's set to delete files older than 2 days.
> >> >
> >> > Does this not supported by the SQL2K5?
> >> > Should I not set it to create folders for each database backup?
> >> >
> >> > Thanks in advance...
> >>
> >>
>
>|||Never mind, I see it now.
I had to open the Management Studio localy on the SQL Server.
For some reason, I don't see this option when I look at it remotely from my
workstation.
Thanks everyone...
"Artunc" wrote:
> I don't see it in there, I'm running SP1.
> Do I need to install SP2 to see it?
> "Andrew J. Kelly" wrote:
> > It is in the cleanup task. You have to open it in the maintenance plan
> > editor and you will see it.
> >
> > --
> > Andrew J. Kelly SQL MVP
> >
> > "Artunc" <artunc_u2@.hotmail.com> wrote in message
> > news:201DF41C-9E0C-44A2-9582-332E33E25A09@.microsoft.com...
> > >
> > > Do you know where can I enable this option?
> > >
> > > "Tibor Karaszi" wrote:
> > >
> > >> With sp1, you have an option to recurse sub-folders. also, there has been
> > >> lots of work on maint
> > >> plans in sp2.
> > >>
> > >> --
> > >> Tibor Karaszi, SQL Server MVP
> > >> http://www.karaszi.com/sqlserver/default.asp
> > >> http://sqlblog.com/blogs/tibor_karaszi
> > >>
> > >>
> > >> "Artunc" <artunc_u2@.hotmail.com> wrote in message
> > >> news:60572E3A-8C37-4236-A7DE-7E16EE73292D@.microsoft.com...
> > >> >
> > >> > The maintenance job I have creates sub-folders for each database when
> > >> > it
> > >> > backups.
> > >> > The Cleanup Job is pointing to the root of this folder but it's not
> > >> > deleting
> > >> > previous backups. It's set to delete files older than 2 days.
> > >> >
> > >> > Does this not supported by the SQL2K5?
> > >> > Should I not set it to create folders for each database backup?
> > >> >
> > >> > Thanks in advance...
> > >>
> > >>
> >
> >
> >

Maintenance Plans and cleaning up backups in subfolders...

Maintenance Plans

We just started using DPM 2007 to backup our 2005 DB's so I am deleting the
backups in the maintenance plans. Should I go back in and have any regular
maintenance on DB's like Shrink or Reorganize or is just backing up using DPM
ok?DPM only does backups and AFAIK it also takes care of the retention period
as well. But it does not handle any other routine database functions such as
CHECKDB's, Reindexing etc. so you still have to do that yourself. And
shrinking should not be one of them.
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Robert" <Robert@.discussions.microsoft.com> wrote in message
news:ED8523CE-150E-4576-AFF0-0D9AD6B89EAB@.microsoft.com...
> We just started using DPM 2007 to backup our 2005 DB's so I am deleting
> the
> backups in the maintenance plans. Should I go back in and have any regular
> maintenance on DB's like Shrink or Reorganize or is just backing up using
> DPM
> ok?
>|||Thanks Andrew. What is typical for a maintenance plan, there are many options
in the Admin. Studio.
I just set one up to:
Check Integrity
Reorg Index
Update Stats
Clean up history
Maintenance Cleanup
"Andrew J. Kelly" wrote:
> DPM only does backups and AFAIK it also takes care of the retention period
> as well. But it does not handle any other routine database functions such as
> CHECKDB's, Reindexing etc. so you still have to do that yourself. And
> shrinking should not be one of them.
> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Robert" <Robert@.discussions.microsoft.com> wrote in message
> news:ED8523CE-150E-4576-AFF0-0D9AD6B89EAB@.microsoft.com...
> > We just started using DPM 2007 to backup our 2005 DB's so I am deleting
> > the
> > backups in the maintenance plans. Should I go back in and have any regular
> > maintenance on DB's like Shrink or Reorganize or is just backing up using
> > DPM
> > ok?
> >
> >
>|||By understanding what each option do, you can decide which options are suitable for a particular
installation.
For instance, Maint Cleanup can be critical if you also do backup and don't have other means to
remove old backup files.
Or, Reorg can be important to reduce fragmentation, but since the maint plan's reorg is stupid and
don't take into account initial fragmentation one might want to skip this step and do it yourself
(smarter). Or perhaps not at all, if fragmentation don't cost you.
etc...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Robert" <Robert@.discussions.microsoft.com> wrote in message
news:29C1FCC7-A476-4474-AB91-541A8CC16C00@.microsoft.com...
> Thanks Andrew. What is typical for a maintenance plan, there are many options
> in the Admin. Studio.
> I just set one up to:
> Check Integrity
> Reorg Index
> Update Stats
> Clean up history
> Maintenance Cleanup
>
>
> "Andrew J. Kelly" wrote:
>> DPM only does backups and AFAIK it also takes care of the retention period
>> as well. But it does not handle any other routine database functions such as
>> CHECKDB's, Reindexing etc. so you still have to do that yourself. And
>> shrinking should not be one of them.
>> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "Robert" <Robert@.discussions.microsoft.com> wrote in message
>> news:ED8523CE-150E-4576-AFF0-0D9AD6B89EAB@.microsoft.com...
>> > We just started using DPM 2007 to backup our 2005 DB's so I am deleting
>> > the
>> > backups in the maintenance plans. Should I go back in and have any regular
>> > maintenance on DB's like Shrink or Reorganize or is just backing up using
>> > DPM
>> > ok?
>> >
>> >
>>|||Thanks Tibor. I will get to reading to better understand what each does.
"Tibor Karaszi" wrote:
> By understanding what each option do, you can decide which options are suitable for a particular
> installation.
> For instance, Maint Cleanup can be critical if you also do backup and don't have other means to
> remove old backup files.
> Or, Reorg can be important to reduce fragmentation, but since the maint plan's reorg is stupid and
> don't take into account initial fragmentation one might want to skip this step and do it yourself
> (smarter). Or perhaps not at all, if fragmentation don't cost you.
> etc...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Robert" <Robert@.discussions.microsoft.com> wrote in message
> news:29C1FCC7-A476-4474-AB91-541A8CC16C00@.microsoft.com...
> > Thanks Andrew. What is typical for a maintenance plan, there are many options
> > in the Admin. Studio.
> >
> > I just set one up to:
> > Check Integrity
> > Reorg Index
> > Update Stats
> > Clean up history
> > Maintenance Cleanup
> >
> >
> >
> >
> >
> > "Andrew J. Kelly" wrote:
> >
> >> DPM only does backups and AFAIK it also takes care of the retention period
> >> as well. But it does not handle any other routine database functions such as
> >> CHECKDB's, Reindexing etc. so you still have to do that yourself. And
> >> shrinking should not be one of them.
> >> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >> Solid Quality Mentors
> >>
> >>
> >> "Robert" <Robert@.discussions.microsoft.com> wrote in message
> >> news:ED8523CE-150E-4576-AFF0-0D9AD6B89EAB@.microsoft.com...
> >> > We just started using DPM 2007 to backup our 2005 DB's so I am deleting
> >> > the
> >> > backups in the maintenance plans. Should I go back in and have any regular
> >> > maintenance on DB's like Shrink or Reorganize or is just backing up using
> >> > DPM
> >> > ok?
> >> >
> >> >
> >>
> >>
>

Maintenance Plans

I created a SQL Server Maintenance Plan that performs sql
backups, optimizations and integrity checks through a
maintenance plan.
The backup portion of the maintenance plan works okay.
But the optimization and integrity checks fail with the
following errors:
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC failed
because the following SET options have incorrect
settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
We are running SQL 2000 Standard Edition SP3.
I saw the Microsoft Knowledge Base Article - 301292 which
seems to be the problem. I tried setting the sp_options
mentioned in the article at the database level but the
problem still occurred. I really want to use a generic
maintenance plan, I don't want to have to write jobs for
each database I need to perform optimization or integrity
checks on.
As a side note the database that is reporting the errors
is part of a sharepoint install.
Any help would be great.
Thanks.Gary,
We ran into this also, but the Maintenance Plan will not issue the proper
SET as the note describes. The only way that I know to do it is to go ahead
and write your own script.
Sorry,
Russell Fields
"Gary Murphy" <anonymous@.discussions.microsoft.com> wrote in message
news:ec0c01c43d0e$6512bda0$a101280a@.phx.gbl...
> I created a SQL Server Maintenance Plan that performs sql
> backups, optimizations and integrity checks through a
> maintenance plan.
> The backup portion of the maintenance plan works okay.
> But the optimization and integrity checks fail with the
> following errors:
> [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC failed
> because the following SET options have incorrect
> settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
> We are running SQL 2000 Standard Edition SP3.
> I saw the Microsoft Knowledge Base Article - 301292 which
> seems to be the problem. I tried setting the sp_options
> mentioned in the article at the database level but the
> problem still occurred. I really want to use a generic
> maintenance plan, I don't want to have to write jobs for
> each database I need to perform optimization or integrity
> checks on.
> As a side note the database that is reporting the errors
> is part of a sharepoint install.
> Any help would be great.
> Thanks.

Monday, February 20, 2012

Maintenance Plan: Backup Database Task (Backup Transaction Log opt

-1073548784)". I think It could be also
due to (1).
Can anybody help me? Is an error in Maintenanced plans with Sp2?
By the way, Sql version is SP2.
Then plan has been created with "new plan option" -> add "Backup database
task"
(without wizard)
Thanks, JuanSa.Hi
"JuanSa" wrote:

> Hello.
> I have an issue making transaction logs backups with the Backup Database
> Task within a Maintenance Plan.
> (1) When I check the option to backup trn logs of all users databases, all
> databases or any selection, then save the subplan and reopen the task
> properties and this selection is lost. That is to say, the option
> Databases(to backup) is set again to <Select one or more>
I have run through this and when re-editing the plan it does seem to "loose"
the selected databases, also when you re-select the databases the destinatio
n
files are changed back to one per database. You don't need to enter the drop
down list for this to happen, just changing the overwrite/append option seem
s
to do this. it does not seem to happen with Full backups.

> (2)When I execute the plan, it fails with an error saying something like "
it
> can't make backup of a bd with simple model recovery option" (if there was
> one like that in the server).
> It's supposed that in the selection of databases in this task I don′t sel
ect
> any database with that option(in addition, it doesn't let you do that
> logically), but I think the reason for the error is that the selection of
> databases isn't saved (see 1).
Simple recovery mode databases are not listed in the selectable database
when you choose transaction logs. They should be ignored for the other
options as well!

> (3) It also fails when the plan is created and executing ok, and I create
a
> new database. Then the next execution fails until I make a TRN Log backup
of
> the new database manually. After that, next plan execution runs ok.
> The error in this case is: "Failed

-1073548784)". I think It could be als
o
> due to (1).
You would expect an error for a transaction log backup if there was not a
full backup previously. This would occur for the all databases/all user
databases option but not the specifically selected databases unless you add
it to the list.

> Can anybody help me? Is an error in Maintenanced plans with Sp2?
> By the way, Sql version is SP2.
> Then plan has been created with "new plan option" -> add "Backup database
> task"
> (without wizard)
>
I used the add maintenance plan option under maintenance plans, but it
results in the same thing! BI studio also seems to do the same, if you just
go into the plan and choose the View SQL it comes up with no statements.

> Thanks, JuanSa.
>
You could call PSS
https://support.microsoft.com/oas/d...508&gprid=2855&
or log a fault at https://connect.microsoft.com/SQLServer/feedback (if you
do this post the number)
Alternatively you could use the view SQL option to save the SQL that will be
run and create a job of your own which will do this.
John|||The FeedbackID is 262295
https://connect.microsoft.com/SQLSe...=2622
95|||On May 13, 4:22 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
> "JuanSa" wrote:
>
>
all[vbcol=seagreen]
> I have run through this and when re-editing theplanit does seem to "loose"
> the selected databases, also when you re-select the databases the destina=
tion
> files are changed back to one per database. You don't need to enter the d=
rop
> down list for this to happen, just changing the overwrite/append option s=
eems
> to do this. it does not seem to happen with Full backups.
>
>
"it[vbcol=seagreen]
was[vbcol=seagreen]
elect[vbcol=seagreen]
> Simple recovery mode databases are not listed in the selectable database
> when you choose transaction logs. They should be ignored for the other
> options as well!
>
>
a[vbcol=seagreen]
up of[vbcol=seagreen]
>
also[vbcol=seagreen]
> You would expect an error for a transaction log backup if there was not a
> full backup previously. This would occur for the all databases/all user
> databases option but not the specifically selected databases unless you a=
dd
> it to the list.
>
>
> I used the addmaintenanceplanoption undermaintenanceplans, but it
> results in the same thing! BI studio also seems to do the same, if you ju=
st
> go into theplanand choose the View SQL it comes up with no statements.
>
> You could call PSShttps://support.microsoft.com/oas/default.aspx?&c1=3D50=
8&gprid=3D2855&
> or log a fault athttps://connect.microsoft.com/SQLServer/feedback(if you
> do this post the number)
> Alternatively you could use the view SQL option to save the SQL that will=
be
> run and create a job of your own which will do this.
> John

Maintenance Plan: Backup Database Task (Backup Transaction Log opt

Hello.
I have an issue making transaction logs backups with the Backup Database
Task within a Maintenance Plan.
(1) When I check the option to backup trn logs of all users databases, all
databases or any selection, then save the subplan and reopen the task
properties and this selection is lost. That is to say, the option
Databases(to backup) is set again to <Select one or more>
(2)When I execute the plan, it fails with an error saying something like "it
can't make backup of a bd with simple model recovery option" (if there was
one like that in the server).
It's supposed that in the selection of databases in this task I donÂ´t select
any database with that option(in addition, it doesn't let you do that
logically), but I think the reason for the error is that the selection of
databases isn't saved (see 1).
(3) It also fails when the plan is created and executing ok, and I create a
new database. Then the next execution fails until I make a TRN Log backup of
the new database manually. After that, next plan execution runs ok.
The error in this case is: "Failed:(-1073548784)". I think It could be also
due to (1).
Can anybody help me? Is an error in Maintenanced plans with Sp2?
By the way, Sql version is SP2.
Then plan has been created with "new plan option" -> add "Backup database
task"
(without wizard)
Thanks, JuanSa.Hi
"JuanSa" wrote:
> Hello.
> I have an issue making transaction logs backups with the Backup Database
> Task within a Maintenance Plan.
> (1) When I check the option to backup trn logs of all users databases, all
> databases or any selection, then save the subplan and reopen the task
> properties and this selection is lost. That is to say, the option
> Databases(to backup) is set again to <Select one or more>
I have run through this and when re-editing the plan it does seem to "loose"
the selected databases, also when you re-select the databases the destination
files are changed back to one per database. You don't need to enter the drop
down list for this to happen, just changing the overwrite/append option seems
to do this. it does not seem to happen with Full backups.
> (2)When I execute the plan, it fails with an error saying something like "it
> can't make backup of a bd with simple model recovery option" (if there was
> one like that in the server).
> It's supposed that in the selection of databases in this task I donÂ´t select
> any database with that option(in addition, it doesn't let you do that
> logically), but I think the reason for the error is that the selection of
> databases isn't saved (see 1).
Simple recovery mode databases are not listed in the selectable database
when you choose transaction logs. They should be ignored for the other
options as well!
> (3) It also fails when the plan is created and executing ok, and I create a
> new database. Then the next execution fails until I make a TRN Log backup of
> the new database manually. After that, next plan execution runs ok.
> The error in this case is: "Failed:(-1073548784)". I think It could be also
> due to (1).
You would expect an error for a transaction log backup if there was not a
full backup previously. This would occur for the all databases/all user
databases option but not the specifically selected databases unless you add
it to the list.
> Can anybody help me? Is an error in Maintenanced plans with Sp2?
> By the way, Sql version is SP2.
> Then plan has been created with "new plan option" -> add "Backup database
> task"
> (without wizard)
>
I used the add maintenance plan option under maintenance plans, but it
results in the same thing! BI studio also seems to do the same, if you just
go into the plan and choose the View SQL it comes up with no statements.
> Thanks, JuanSa.
>
You could call PSS
https://support.microsoft.com/oas/default.aspx?&c1=508&gprid=2855&
or log a fault at https://connect.microsoft.com/SQLServer/feedback (if you
do this post the number)
Alternatively you could use the view SQL option to save the SQL that will be
run and create a job of your own which will do this.
John|||On May 13, 4:22 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
> "JuanSa" wrote:
> > Hello.
> > I have an issue making transaction logs backups with the Backup Database
> > Task within aMaintenancePlan.
> > (1) When I check the option to backup trn logs of all users databases, =all
> > databases or anyselection, then save the subplan and reopen the task
> > properties and thisselectionis lost. That is to say, the option
> > Databases(to backup) is set again to <Select one or more>
> I have run through this and when re-editing theplanit does seem to "loose"
> the selected databases, also when you re-select the databases the destina=tion
> files are changed back to one per database. You don't need to enter the d=rop
> down list for this to happen, just changing the overwrite/append option s=eems
> to do this. it does not seem to happen with Full backups.
>
> > (2)When I execute theplan, it fails with an error saying something like= "it
> > can't make backup of a bd with simple model recovery option" (if there =was
> > one like that in the server).
> > It's supposed that in theselectionof databases in this task I don=B4t s=elect
> > any database with that option(in addition, it doesn't let you do that
> > logically), but I think the reason for the error is that theselectionof
> > databases isn't saved (see 1).
> Simple recovery mode databases are not listed in the selectable database
> when you choose transaction logs. They should be ignored for the other
> options as well!
>
> > (3) It also fails when theplanis created and executing ok, and I create= a
> > new database. Then the next execution fails until I make a TRN Log back=up of
> > the new database manually. After that, nextplanexecution runs ok.
> > The error in this case is: "Failed:(-1073548784)". I think It could be =also
> > due to (1).
> You would expect an error for a transaction log backup if there was not a
> full backup previously. This would occur for the all databases/all user
> databases option but not the specifically selected databases unless you a=dd
> it to the list.
> > Can anybody help me? Is an error in Maintenanced plans with Sp2?
> > By the way, Sql version is SP2.
> > Thenplanhas been created with "newplanoption" -> add "Backup database
> > task"
> > (without wizard)
> I used the addmaintenanceplanoption undermaintenanceplans, but it
> results in the same thing! BI studio also seems to do the same, if you ju=st
> go into theplanand choose the View SQL it comes up with no statements.
> > Thanks, JuanSa.
> You could call PSShttps://support.microsoft.com/oas/default.aspx?&c1=3D50=8&gprid=3D2855&
> or log a fault athttps://connect.microsoft.com/SQLServer/feedback(if you
> do this post the number)
> Alternatively you could use the view SQL option to save the SQL that will= be
> run and create a job of your own which will do this.
> John|||The FeedbackID is 262295
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=262295

Maintenance Plan: Backup Database Task (Backup Transaction Log opt

-1073548784)". I think It could be also
due to (1).
Can anybody help me? Is an error in Maintenanced plans with Sp2?
By the way, Sql version is SP2.
Then plan has been created with "new plan option" -> add "Backup database
task"
(without wizard)
Thanks, JuanSa.
Hi
"JuanSa" wrote:

> Hello.
> I have an issue making transaction logs backups with the Backup Database
> Task within a Maintenance Plan.
> (1) When I check the option to backup trn logs of all users databases, all
> databases or any selection, then save the subplan and reopen the task
> properties and this selection is lost. That is to say, the option
> Databases(to backup) is set again to <Select one or more>
I have run through this and when re-editing the plan it does seem to "loose"
the selected databases, also when you re-select the databases the destination
files are changed back to one per database. You don't need to enter the drop
down list for this to happen, just changing the overwrite/append option seems
to do this. it does not seem to happen with Full backups.

> (2)When I execute the plan, it fails with an error saying something like "it
> can't make backup of a bd with simple model recovery option" (if there was
> one like that in the server).
> It's supposed that in the selection of databases in this task I don′t select
> any database with that option(in addition, it doesn't let you do that
> logically), but I think the reason for the error is that the selection of
> databases isn't saved (see 1).
Simple recovery mode databases are not listed in the selectable database
when you choose transaction logs. They should be ignored for the other
options as well!

> (3) It also fails when the plan is created and executing ok, and I create a
> new database. Then the next execution fails until I make a TRN Log backup of
> the new database manually. After that, next plan execution runs ok.
> The error in this case is: "Failed

-1073548784)". I think It could be also
> due to (1).
You would expect an error for a transaction log backup if there was not a
full backup previously. This would occur for the all databases/all user
databases option but not the specifically selected databases unless you add
it to the list.

> Can anybody help me? Is an error in Maintenanced plans with Sp2?
> By the way, Sql version is SP2.
> Then plan has been created with "new plan option" -> add "Backup database
> task"
> (without wizard)
>
I used the add maintenance plan option under maintenance plans, but it
results in the same thing! BI studio also seems to do the same, if you just
go into the plan and choose the View SQL it comes up with no statements.

> Thanks, JuanSa.
>
You could call PSS
https://support.microsoft.com/oas/default.aspx?&c1=508&gprid=2855&
or log a fault at https://connect.microsoft.com/SQLServer/feedback (if you
do this post the number)
Alternatively you could use the view SQL option to save the SQL that will be
run and create a job of your own which will do this.
John
|||The FeedbackID is 262295
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=262295
|||On May 13, 4:22 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
> "JuanSa" wrote:
>
> I have run through this and when re-editing theplanit does seem to "loose"
> the selected databases, also when you re-select the databases the destination
> files are changed back to one per database. You don't need to enter the drop
> down list for this to happen, just changing the overwrite/append option seems
> to do this. it does not seem to happen with Full backups.
>
>
> Simple recovery mode databases are not listed in the selectable database
> when you choose transaction logs. They should be ignored for the other
> options as well!
>
>
> You would expect an error for a transaction log backup if there was not a
> full backup previously. This would occur for the all databases/all user
> databases option but not the specifically selected databases unless you add
> it to the list.
>
> I used the addmaintenanceplanoption undermaintenanceplans, but it
> results in the same thing! BI studio also seems to do the same, if you just
> go into theplanand choose the View SQL it comes up with no statements.
>
> You could call PSShttps://support.microsoft.com/oas/default.aspx?&c1=508&gprid=2855&
> or log a fault athttps://connect.microsoft.com/SQLServer/feedback(if you
> do this post the number)
> Alternatively you could use the view SQL option to save the SQL that willbe
> run and create a job of your own which will do this.
> John

Maintenance Plan,SQL Server 2000

Hi,
I set up a scheduled Maintenance Plan for DB backups. For some reason just user DBs backups are performed. For master and msdb I can run backups manually via T-SQL or Enterprise Mngr and do not have any problems. But it doesn't work with Maint. Plan. There are no any error messages in SQL error log, the only error message I can see comes from View Job History(SQL Server Agent, Jobs) and says 'job failed'.
I administrate several servers and never had this kind of problem.
I logged as 'sa' .
Any ideas?
I appreciate all your help.:confused:Any chance you can post the command(s) you are using to backup your user and system dbs?|||Thank you for your response. I've fixed the problem - it was a security issue for the NT account on master & msdb files.
Thanx again

Wednesday, March 28, 2012

Making the Log file small

Friday, March 9, 2012

Maitenance Job

Maitenance Job

Wednesday, March 7, 2012

Maintenance plans not deleting old transaction log backups

Maintenance Plans Disappear

Maintenance Plans Disappear

Maintenance Plans Disappear

Saturday, February 25, 2012

Maintenance Plans and Integrity checks

Maintenance Plans and Integrity checks

Maintenance Plans and cleaning up backups in subfolders...

Maintenance Plans and cleaning up backups in subfolders...

Maintenance Plans and cleaning up backups in subfolders...

Maintenance Plans

Maintenance Plans

Monday, February 20, 2012

Maintenance Plan: Backup Database Task (Backup Transaction Log opt

Maintenance Plan: Backup Database Task (Backup Transaction Log opt

Maintenance Plan: Backup Database Task (Backup Transaction Log opt

Maintenance Plan,SQL Server 2000

maintenance plan wizard

Blog Archive

About Me