Make sure the application for the project type (.rptproj) is installed

Hi,

Till Some time back my SSRS SSIS services were working fine. I was able to create/open any project from the Business Intelligence Development Studio. That time only BI suite was installed in Visual Studio 2005.

But due to some other requirements , we had to installed Complete VS.NET 2005 on the same system. After the installation i am only able to create/open ASP.NET applications. All earlier Reporting and Integration project are giving error on opening. Even i a m not able to create a new SSRS or SSIS application.

Error Message says:

"The application for the project 'c:\documents and settings\....rtpproj' is not installed.

Make sure the application for the project type (.rptproj) is installed"

I remote login to this server to work on.

There is another thing, one of my colleague when he log in to this system using his ID, he is able to create new porjects. This is system is not a Terminal Server in true sense.

So What should be the solution for this?.

Installation/Reinstallation of Sql Server component or reinstallation of everything.

Or may be some better option.Pls your suggestions will be highly appreciated.

Thanks

Sumit

I think you need to re-install the client components, especially the BI Development Studio|||Can you also check the .NET framework version installed after that VS installation.sql

Make sure the application for the project type (.rptproj) is installed

Hi,

Till Some time back my SSRS SSIS services were working fine. I was able to create/open any project from the Business Intelligence Development Studio. That time only BI suite was installed in Visual Studio 2005.

But due to some other requirements , we had to installed Complete VS.NET 2005 on the same system. After the installation i am only able to create/open ASP.NET applications. All earlier Reporting and Integration project are giving error on opening. Even i a m not able to create a new SSRS or SSIS application.

Error Message says:

"The application for the project 'c:\documents and settings\....rtpproj' is not installed.

Make sure the application for the project type (.rptproj) is installed"

I remote login to this server to work on.

There is another thing, one of my colleague when he log in to this system using his ID, he is able to create new porjects. This is system is not a Terminal Server in true sense.

So What should be the solution for this?.

Installation/Reinstallation of Sql Server component or reinstallation of everything.

Or may be some better option.Pls your suggestions will be highly appreciated.

Thanks

Sumit

I think you need to re-install the client components, especially the BI Development Studio|||Can you also check the .NET framework version installed after that VS installation.|||

I received this same exact error

wondering if you found a "quick" fix, or maybe just one that works

Please help

Maitenance plans and noskip

I am using SQL Server 2005. I have a Backup Database task which I use
to back up to a single backup device. I want to set a retention time
of 3 days and have old backups overwritten. This seems to be the WITH
INIT, NOSKIP problem. However using the wizard there doesn't seem to
be the possibility of doing this. I find it hard to believe though
that anyone would write a wizard which didn't offer this feature.
Is there any way to backup with NOSKIP or failing that alter the SQL
genereated by the wizard.
For info, here's the first few SQL statements from the wizard!
BACKUP DATABASE [master] TO [All299LocalDatabases] WITH RETAINDAYS =
3, NOFORMAT, INIT, NAME = N'master_backup_20070802123131', SKIP,
REWIND, NOUNLOAD, STATS = 10
GO
BACKUP DATABASE [model] TO [All299LocalDatabases] WITH RETAINDAYS =
3, NOFORMAT, NOINIT, NAME = N'model_backup_20070802123131', SKIP,
REWIND, NOUNLOAD, STATS = 10
GO
BACKUP DATABASE [msdb] TO [All299LocalDatabases] WITH RETAINDAYS =
3, NOFORMAT, NOINIT, NAME = N'msdb_backup_20070802123132', SKIP,
REWIND, NOUNLOAD, STATS = 10
GO
BACKUP DATABASE [ReportServer] TO [All299LocalDatabases] WITH
RETAINDAYS = 3, NOFORMAT, NOINIT, NAME =
N'ReportServer_backup_20070802123132', SKIP, REWIND, NOUNLOAD, STATS
= 10
GO
etc
There's no way in SQL Server to backup to a single backup device and overwrite "only the oldest"
backups. Either you overwrite everything, or you append. Period.
Now, I understand that the interaction between INIT/NOINIT and SKIP/NOSKIP can be confusing, and
that it probably why there's a section in Books Online titled "Interaction of SKIP, NOSKIP, INIT,
and NOINIT" (in the BACKUP topic). Bu, as mentioned before, SQL Server either overwrites everything
or not at all. This is how the engine work, so it doesn't relate to the maintenance wizard.
Personally,. I don't use SKIP/NOSKIP at all, as I don't find those options adding anything to
INIT/NOINIT.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<usenet@.tynemarch.co.uk> wrote in message
news:1186054522.882732.218720@.d55g2000hsg.googlegr oups.com...
>I am using SQL Server 2005. I have a Backup Database task which I use
> to back up to a single backup device. I want to set a retention time
> of 3 days and have old backups overwritten. This seems to be the WITH
> INIT, NOSKIP problem. However using the wizard there doesn't seem to
> be the possibility of doing this. I find it hard to believe though
> that anyone would write a wizard which didn't offer this feature.
> Is there any way to backup with NOSKIP or failing that alter the SQL
> genereated by the wizard.
> For info, here's the first few SQL statements from the wizard!
> BACKUP DATABASE [master] TO [All299LocalDatabases] WITH RETAINDAYS =
> 3, NOFORMAT, INIT, NAME = N'master_backup_20070802123131', SKIP,
> REWIND, NOUNLOAD, STATS = 10
> GO
> BACKUP DATABASE [model] TO [All299LocalDatabases] WITH RETAINDAYS =
> 3, NOFORMAT, NOINIT, NAME = N'model_backup_20070802123131', SKIP,
> REWIND, NOUNLOAD, STATS = 10
> GO
> BACKUP DATABASE [msdb] TO [All299LocalDatabases] WITH RETAINDAYS =
> 3, NOFORMAT, NOINIT, NAME = N'msdb_backup_20070802123132', SKIP,
> REWIND, NOUNLOAD, STATS = 10
> GO
> BACKUP DATABASE [ReportServer] TO [All299LocalDatabases] WITH
> RETAINDAYS = 3, NOFORMAT, NOINIT, NAME =
> N'ReportServer_backup_20070802123132', SKIP, REWIND, NOUNLOAD, STATS
> = 10
> GO
> etc
>
|||I would happily overwrite everything but there doesn't seem to be that
option either in the Wizard. You only have the option that it either
expires or it doesn't as whatever you do it always puts in SKIP into
the SQL. The only way you seem to be able to backup without having old
backups is to backup to individual files rather than using a backup
device as I am.
Rob
On 2 Aug, 12:58, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> There's no way in SQL Server to backup to a single backup device and overwrite "only the oldest"
> backups. Either you overwrite everything, or you append. Period.
> Now, I understand that the interaction between INIT/NOINIT and SKIP/NOSKIP can be confusing, and
> that it probably why there's a section in Books Online titled "Interaction of SKIP, NOSKIP, INIT,
> and NOINIT" (in the BACKUP topic). Bu, as mentioned before, SQL Server either overwrites everything
> or not at all. This is how the engine work, so it doesn't relate to the maintenance wizard.
> Personally,. I don't use SKIP/NOSKIP at all, as I don't find those options adding anything to
> INIT/NOINIT.
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> <use...@.tynemarch.co.uk> wrote in message
> news:1186054522.882732.218720@.d55g2000hsg.googlegr oups.com...
>
>
>
>
> - Show quoted text -
|||So what you want to do is to backup to the same backup device name and always overwrite?
In my wizard (I'm on sp2, there has been improvements here...), I see an option "If backup files
exists:" and I select "Overwrite".
Here are the backup commands executed, as catched by Profiler:
BACKUP DATABASE [master] TO [MyDevice] WITH NOFORMAT, INIT, NAME =
N'master_backup_20070802151715', SKIP, REWIND, NOUNLOAD, STATS = 10
BACKUP DATABASE [model] TO [MyDevice] WITH NOFORMAT, NOINIT, NAME =
N'model_backup_20070802151715', SKIP, REWIND, NOUNLOAD, STATS = 10
As you see, it does INIT for the first backup and NOINIT for the following backups. Is above what
you want, ir are you saying that there's some problem with the TSQL above?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<usenet@.tynemarch.co.uk> wrote in message
news:1186057933.490529.68270@.l70g2000hse.googlegro ups.com...
>I would happily overwrite everything but there doesn't seem to be that
> option either in the Wizard. You only have the option that it either
> expires or it doesn't as whatever you do it always puts in SKIP into
> the SQL. The only way you seem to be able to backup without having old
> backups is to backup to individual files rather than using a backup
> device as I am.
> Rob
> On 2 Aug, 12:58, "Tibor Karaszi"
> <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
>
|||I could not get the wizard to generate any SQL with SKIP in it.
However, the answer to my problems was to use a one-off backup file
rather than have a pre-allocated backup device. I could then move to
the file to somewhere else and start afresh with a new file the next
day. Thanks for the help anyway.
On 2 Aug, 14:19, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> So what you want to do is to backup to the same backup device name and always overwrite?
> In my wizard (I'm on sp2, there has been improvements here...), I see an option "If backup files
> exists:" and I select "Overwrite".
> Here are the backup commands executed, as catched by Profiler:
> BACKUP DATABASE [master] TO [MyDevice] WITH NOFORMAT, INIT, NAME =
> N'master_backup_20070802151715', SKIP, REWIND, NOUNLOAD, STATS = 10
> BACKUP DATABASE [model] TO [MyDevice] WITH NOFORMAT, NOINIT, NAME =
> N'model_backup_20070802151715', SKIP, REWIND, NOUNLOAD, STATS = 10
> As you see, it does INIT for the first backup and NOINIT for the following backups. Is above what
> you want, ir are you saying that there's some problem with the TSQL above?
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> <use...@.tynemarch.co.uk> wrote in message
> news:1186057933.490529.68270@.l70g2000hse.googlegro ups.com...
>
>
>
>
>
>
>
>
> - Show quoted text -

Maitenance plans and noskip

I am using SQL Server 2005. I have a Backup Database task which I use
to back up to a single backup device. I want to set a retention time
of 3 days and have old backups overwritten. This seems to be the WITH
INIT, NOSKIP problem. However using the wizard there doesn't seem to
be the possibility of doing this. I find it hard to believe though
that anyone would write a wizard which didn't offer this feature.
Is there any way to backup with NOSKIP or failing that alter the SQL
genereated by the wizard.
For info, here's the first few SQL statements from the wizard!
BACKUP DATABASE [master] TO [All299LocalDatabases] WITH RETAINDAYS = 3, NOFORMAT, INIT, NAME = N'master_backup_20070802123131', SKIP,
REWIND, NOUNLOAD, STATS = 10
GO
BACKUP DATABASE [model] TO [All299LocalDatabases] WITH RETAINDAYS = 3, NOFORMAT, NOINIT, NAME = N'model_backup_20070802123131', SKIP,
REWIND, NOUNLOAD, STATS = 10
GO
BACKUP DATABASE [msdb] TO [All299LocalDatabases] WITH RETAINDAYS = 3, NOFORMAT, NOINIT, NAME = N'msdb_backup_20070802123132', SKIP,
REWIND, NOUNLOAD, STATS = 10
GO
BACKUP DATABASE [ReportServer] TO [All299LocalDatabases] WITH
RETAINDAYS = 3, NOFORMAT, NOINIT, NAME = N'ReportServer_backup_20070802123132', SKIP, REWIND, NOUNLOAD, STATS
= 10
GO
etcThere's no way in SQL Server to backup to a single backup device and overwrite "only the oldest"
backups. Either you overwrite everything, or you append. Period.
Now, I understand that the interaction between INIT/NOINIT and SKIP/NOSKIP can be confusing, and
that it probably why there's a section in Books Online titled "Interaction of SKIP, NOSKIP, INIT,
and NOINIT" (in the BACKUP topic). Bu, as mentioned before, SQL Server either overwrites everything
or not at all. This is how the engine work, so it doesn't relate to the maintenance wizard.
Personally,. I don't use SKIP/NOSKIP at all, as I don't find those options adding anything to
INIT/NOINIT.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<usenet@.tynemarch.co.uk> wrote in message
news:1186054522.882732.218720@.d55g2000hsg.googlegroups.com...
>I am using SQL Server 2005. I have a Backup Database task which I use
> to back up to a single backup device. I want to set a retention time
> of 3 days and have old backups overwritten. This seems to be the WITH
> INIT, NOSKIP problem. However using the wizard there doesn't seem to
> be the possibility of doing this. I find it hard to believe though
> that anyone would write a wizard which didn't offer this feature.
> Is there any way to backup with NOSKIP or failing that alter the SQL
> genereated by the wizard.
> For info, here's the first few SQL statements from the wizard!
> BACKUP DATABASE [master] TO [All299LocalDatabases] WITH RETAINDAYS => 3, NOFORMAT, INIT, NAME = N'master_backup_20070802123131', SKIP,
> REWIND, NOUNLOAD, STATS = 10
> GO
> BACKUP DATABASE [model] TO [All299LocalDatabases] WITH RETAINDAYS => 3, NOFORMAT, NOINIT, NAME = N'model_backup_20070802123131', SKIP,
> REWIND, NOUNLOAD, STATS = 10
> GO
> BACKUP DATABASE [msdb] TO [All299LocalDatabases] WITH RETAINDAYS => 3, NOFORMAT, NOINIT, NAME = N'msdb_backup_20070802123132', SKIP,
> REWIND, NOUNLOAD, STATS = 10
> GO
> BACKUP DATABASE [ReportServer] TO [All299LocalDatabases] WITH
> RETAINDAYS = 3, NOFORMAT, NOINIT, NAME => N'ReportServer_backup_20070802123132', SKIP, REWIND, NOUNLOAD, STATS
> = 10
> GO
> etc
>|||I would happily overwrite everything but there doesn't seem to be that
option either in the Wizard. You only have the option that it either
expires or it doesn't as whatever you do it always puts in SKIP into
the SQL. The only way you seem to be able to backup without having old
backups is to backup to individual files rather than using a backup
device as I am.
Rob
On 2 Aug, 12:58, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> There's no way in SQL Server to backup to a single backup device and overwrite "only the oldest"
> backups. Either you overwrite everything, or you append. Period.
> Now, I understand that the interaction between INIT/NOINIT and SKIP/NOSKIP can be confusing, and
> that it probably why there's a section in Books Online titled "Interaction of SKIP, NOSKIP, INIT,
> and NOINIT" (in the BACKUP topic). Bu, as mentioned before, SQL Server either overwrites everything
> or not at all. This is how the engine work, so it doesn't relate to the maintenance wizard.
> Personally,. I don't use SKIP/NOSKIP at all, as I don't find those options adding anything to
> INIT/NOINIT.
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> <use...@.tynemarch.co.uk> wrote in message
> news:1186054522.882732.218720@.d55g2000hsg.googlegroups.com...
>
> >I am using SQL Server 2005. I have a Backup Database task which I use
> > to back up to a single backup device. I want to set a retention time
> > of 3 days and have old backups overwritten. This seems to be the WITH
> > INIT, NOSKIP problem. However using the wizard there doesn't seem to
> > be the possibility of doing this. I find it hard to believe though
> > that anyone would write a wizard which didn't offer this feature.
> > Is there any way to backup with NOSKIP or failing that alter the SQL
> > genereated by the wizard.
> > For info, here's the first few SQL statements from the wizard!
> > BACKUP DATABASE [master] TO [All299LocalDatabases] WITH RETAINDAYS => > 3, NOFORMAT, INIT, NAME = N'master_backup_20070802123131', SKIP,
> > REWIND, NOUNLOAD, STATS = 10
> > GO
> > BACKUP DATABASE [model] TO [All299LocalDatabases] WITH RETAINDAYS => > 3, NOFORMAT, NOINIT, NAME = N'model_backup_20070802123131', SKIP,
> > REWIND, NOUNLOAD, STATS = 10
> > GO
> > BACKUP DATABASE [msdb] TO [All299LocalDatabases] WITH RETAINDAYS => > 3, NOFORMAT, NOINIT, NAME = N'msdb_backup_20070802123132', SKIP,
> > REWIND, NOUNLOAD, STATS = 10
> > GO
> > BACKUP DATABASE [ReportServer] TO [All299LocalDatabases] WITH
> > RETAINDAYS = 3, NOFORMAT, NOINIT, NAME => > N'ReportServer_backup_20070802123132', SKIP, REWIND, NOUNLOAD, STATS
> > = 10
> > GO
> > etc- Hide quoted text -
> - Show quoted text -|||So what you want to do is to backup to the same backup device name and always overwrite?
In my wizard (I'm on sp2, there has been improvements here...), I see an option "If backup files
exists:" and I select "Overwrite".
Here are the backup commands executed, as catched by Profiler:
BACKUP DATABASE [master] TO [MyDevice] WITH NOFORMAT, INIT, NAME =N'master_backup_20070802151715', SKIP, REWIND, NOUNLOAD, STATS = 10
BACKUP DATABASE [model] TO [MyDevice] WITH NOFORMAT, NOINIT, NAME =N'model_backup_20070802151715', SKIP, REWIND, NOUNLOAD, STATS = 10
As you see, it does INIT for the first backup and NOINIT for the following backups. Is above what
you want, ir are you saying that there's some problem with the TSQL above?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<usenet@.tynemarch.co.uk> wrote in message
news:1186057933.490529.68270@.l70g2000hse.googlegroups.com...
>I would happily overwrite everything but there doesn't seem to be that
> option either in the Wizard. You only have the option that it either
> expires or it doesn't as whatever you do it always puts in SKIP into
> the SQL. The only way you seem to be able to backup without having old
> backups is to backup to individual files rather than using a backup
> device as I am.
> Rob
> On 2 Aug, 12:58, "Tibor Karaszi"
> <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
>> There's no way in SQL Server to backup to a single backup device and overwrite "only the oldest"
>> backups. Either you overwrite everything, or you append. Period.
>> Now, I understand that the interaction between INIT/NOINIT and SKIP/NOSKIP can be confusing, and
>> that it probably why there's a section in Books Online titled "Interaction of SKIP, NOSKIP, INIT,
>> and NOINIT" (in the BACKUP topic). Bu, as mentioned before, SQL Server either overwrites
>> everything
>> or not at all. This is how the engine work, so it doesn't relate to the maintenance wizard.
>> Personally,. I don't use SKIP/NOSKIP at all, as I don't find those options adding anything to
>> INIT/NOINIT.
>> --
>> Tibor Karaszi, SQL Server
>> MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
>> <use...@.tynemarch.co.uk> wrote in message
>> news:1186054522.882732.218720@.d55g2000hsg.googlegroups.com...
>>
>> >I am using SQL Server 2005. I have a Backup Database task which I use
>> > to back up to a single backup device. I want to set a retention time
>> > of 3 days and have old backups overwritten. This seems to be the WITH
>> > INIT, NOSKIP problem. However using the wizard there doesn't seem to
>> > be the possibility of doing this. I find it hard to believe though
>> > that anyone would write a wizard which didn't offer this feature.
>> > Is there any way to backup with NOSKIP or failing that alter the SQL
>> > genereated by the wizard.
>> > For info, here's the first few SQL statements from the wizard!
>> > BACKUP DATABASE [master] TO [All299LocalDatabases] WITH RETAINDAYS =>> > 3, NOFORMAT, INIT, NAME = N'master_backup_20070802123131', SKIP,
>> > REWIND, NOUNLOAD, STATS = 10
>> > GO
>> > BACKUP DATABASE [model] TO [All299LocalDatabases] WITH RETAINDAYS =>> > 3, NOFORMAT, NOINIT, NAME = N'model_backup_20070802123131', SKIP,
>> > REWIND, NOUNLOAD, STATS = 10
>> > GO
>> > BACKUP DATABASE [msdb] TO [All299LocalDatabases] WITH RETAINDAYS =>> > 3, NOFORMAT, NOINIT, NAME = N'msdb_backup_20070802123132', SKIP,
>> > REWIND, NOUNLOAD, STATS = 10
>> > GO
>> > BACKUP DATABASE [ReportServer] TO [All299LocalDatabases] WITH
>> > RETAINDAYS = 3, NOFORMAT, NOINIT, NAME =>> > N'ReportServer_backup_20070802123132', SKIP, REWIND, NOUNLOAD, STATS
>> > = 10
>> > GO
>> > etc- Hide quoted text -
>> - Show quoted text -
>|||I could not get the wizard to generate any SQL with SKIP in it.
However, the answer to my problems was to use a one-off backup file
rather than have a pre-allocated backup device. I could then move to
the file to somewhere else and start afresh with a new file the next
day. Thanks for the help anyway.
On 2 Aug, 14:19, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> So what you want to do is to backup to the same backup device name and always overwrite?
> In my wizard (I'm on sp2, there has been improvements here...), I see an option "If backup files
> exists:" and I select "Overwrite".
> Here are the backup commands executed, as catched by Profiler:
> BACKUP DATABASE [master] TO [MyDevice] WITH NOFORMAT, INIT, NAME => N'master_backup_20070802151715', SKIP, REWIND, NOUNLOAD, STATS = 10
> BACKUP DATABASE [model] TO [MyDevice] WITH NOFORMAT, NOINIT, NAME => N'model_backup_20070802151715', SKIP, REWIND, NOUNLOAD, STATS = 10
> As you see, it does INIT for the first backup and NOINIT for the following backups. Is above what
> you want, ir are you saying that there's some problem with the TSQL above?
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> <use...@.tynemarch.co.uk> wrote in message
> news:1186057933.490529.68270@.l70g2000hse.googlegroups.com...
>
> >I would happily overwrite everything but there doesn't seem to be that
> > option either in the Wizard. You only have the option that it either
> > expires or it doesn't as whatever you do it always puts in SKIP into
> > the SQL. The only way you seem to be able to backup without having old
> > backups is to backup to individual files rather than using a backup
> > device as I am.
> > Rob
> > On 2 Aug, 12:58, "Tibor Karaszi"
> > <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> >> There's no way in SQL Server to backup to a single backup device and overwrite "only the oldest"
> >> backups. Either you overwrite everything, or you append. Period.
> >> Now, I understand that the interaction between INIT/NOINIT and SKIP/NOSKIP can be confusing, and
> >> that it probably why there's a section in Books Online titled "Interaction of SKIP, NOSKIP, INIT,
> >> and NOINIT" (in the BACKUP topic). Bu, as mentioned before, SQL Server either overwrites
> >> everything
> >> or not at all. This is how the engine work, so it doesn't relate to the maintenance wizard.
> >> Personally,. I don't use SKIP/NOSKIP at all, as I don't find those options adding anything to
> >> INIT/NOINIT.
> >> --
> >> Tibor Karaszi, SQL Server
> >> MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/...
> >> <use...@.tynemarch.co.uk> wrote in message
> >>news:1186054522.882732.218720@.d55g2000hsg.googlegroups.com...
> >> >I am using SQL Server 2005. I have a Backup Database task which I use
> >> > to back up to a single backup device. I want to set a retention time
> >> > of 3 days and have old backups overwritten. This seems to be the WITH
> >> > INIT, NOSKIP problem. However using the wizard there doesn't seem to
> >> > be the possibility of doing this. I find it hard to believe though
> >> > that anyone would write a wizard which didn't offer this feature.
> >> > Is there any way to backup with NOSKIP or failing that alter the SQL
> >> > genereated by the wizard.
> >> > For info, here's the first few SQL statements from the wizard!
> >> > BACKUP DATABASE [master] TO [All299LocalDatabases] WITH RETAINDAYS => >> > 3, NOFORMAT, INIT, NAME = N'master_backup_20070802123131', SKIP,
> >> > REWIND, NOUNLOAD, STATS = 10
> >> > GO
> >> > BACKUP DATABASE [model] TO [All299LocalDatabases] WITH RETAINDAYS => >> > 3, NOFORMAT, NOINIT, NAME = N'model_backup_20070802123131', SKIP,
> >> > REWIND, NOUNLOAD, STATS = 10
> >> > GO
> >> > BACKUP DATABASE [msdb] TO [All299LocalDatabases] WITH RETAINDAYS => >> > 3, NOFORMAT, NOINIT, NAME = N'msdb_backup_20070802123132', SKIP,
> >> > REWIND, NOUNLOAD, STATS = 10
> >> > GO
> >> > BACKUP DATABASE [ReportServer] TO [All299LocalDatabases] WITH
> >> > RETAINDAYS = 3, NOFORMAT, NOINIT, NAME => >> > N'ReportServer_backup_20070802123132', SKIP, REWIND, NOUNLOAD, STATS
> >> > = 10
> >> > GO
> >> > etc- Hide quoted text -
> >> - Show quoted text -- Hide quoted text -
> - Show quoted text -

Maitenance plans and noskip

I am using SQL Server 2005. I have a Backup Database task which I use
to back up to a single backup device. I want to set a retention time
of 3 days and have old backups overwritten. This seems to be the WITH
INIT, NOSKIP problem. However using the wizard there doesn't seem to
be the possibility of doing this. I find it hard to believe though
that anyone would write a wizard which didn't offer this feature.
Is there any way to backup with NOSKIP or failing that alter the SQL
genereated by the wizard.
For info, here's the first few SQL statements from the wizard!
BACKUP DATABASE [master] TO [All299LocalDatabases] WITH RETAINDAYS
=
3, NOFORMAT, INIT, NAME = N'master_backup_20070802123131', SKIP,
REWIND, NOUNLOAD, STATS = 10
GO
BACKUP DATABASE [model] TO [All299LocalDatabases] WITH RETAINDAYS
=
3, NOFORMAT, NOINIT, NAME = N'model_backup_20070802123131', SKIP,
REWIND, NOUNLOAD, STATS = 10
GO
BACKUP DATABASE [msdb] TO [All299LocalDatabases] WITH RETAINDAYS =
3, NOFORMAT, NOINIT, NAME = N'msdb_backup_20070802123132', SKIP,
REWIND, NOUNLOAD, STATS = 10
GO
BACKUP DATABASE [ReportServer] TO [All299LocalDatabases] WITH
RETAINDAYS = 3, NOFORMAT, NOINIT, NAME =
N'ReportServer_backup_20070802123132', SKIP, REWIND, NOUNLOAD, STATS
= 10
GO
etcThere's no way in SQL Server to backup to a single backup device and overwri
te "only the oldest"
backups. Either you overwrite everything, or you append. Period.
Now, I understand that the interaction between INIT/NOINIT and SKIP/NOSKIP c
an be confusing, and
that it probably why there's a section in Books Online titled "Interaction o
f SKIP, NOSKIP, INIT,
and NOINIT" (in the BACKUP topic). Bu, as mentioned before, SQL Server eithe
r overwrites everything
or not at all. This is how the engine work, so it doesn't relate to the main
tenance wizard.
Personally,. I don't use SKIP/NOSKIP at all, as I don't find those options a
dding anything to
INIT/NOINIT.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<usenet@.tynemarch.co.uk> wrote in message
news:1186054522.882732.218720@.d55g2000hsg.googlegroups.com...
>I am using SQL Server 2005. I have a Backup Database task which I use
> to back up to a single backup device. I want to set a retention time
> of 3 days and have old backups overwritten. This seems to be the WITH
> INIT, NOSKIP problem. However using the wizard there doesn't seem to
> be the possibility of doing this. I find it hard to believe though
> that anyone would write a wizard which didn't offer this feature.
> Is there any way to backup with NOSKIP or failing that alter the SQL
> genereated by the wizard.
> For info, here's the first few SQL statements from the wizard!
> BACKUP DATABASE [master] TO [All299LocalDatabases] WITH RETAINDA
YS =
> 3, NOFORMAT, INIT, NAME = N'master_backup_20070802123131', SKIP,
> REWIND, NOUNLOAD, STATS = 10
> GO
> BACKUP DATABASE [model] TO [All299LocalDatabases] WITH RETAINDAY
S =
> 3, NOFORMAT, NOINIT, NAME = N'model_backup_20070802123131', SKIP,
> REWIND, NOUNLOAD, STATS = 10
> GO
> BACKUP DATABASE [msdb] TO [All299LocalDatabases] WITH RETAINDAYS
=
> 3, NOFORMAT, NOINIT, NAME = N'msdb_backup_20070802123132', SKIP,
> REWIND, NOUNLOAD, STATS = 10
> GO
> BACKUP DATABASE [ReportServer] TO [All299LocalDatabases] WITH
> RETAINDAYS = 3, NOFORMAT, NOINIT, NAME =
> N'ReportServer_backup_20070802123132', SKIP, REWIND, NOUNLOAD, STATS
> = 10
> GO
> etc
>|||I would happily overwrite everything but there doesn't seem to be that
option either in the Wizard. You only have the option that it either
expires or it doesn't as whatever you do it always puts in SKIP into
the SQL. The only way you seem to be able to backup without having old
backups is to backup to individual files rather than using a backup
device as I am.
Rob
On 2 Aug, 12:58, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> There's no way in SQL Server to backup to a single backup device and overw
rite "only the oldest"
> backups. Either you overwrite everything, or you append. Period.
> Now, I understand that the interaction between INIT/NOINIT and SKIP/NOSKIP
can be confusing, and
> that it probably why there's a section in Books Online titled "Interaction
of SKIP, NOSKIP, INIT,
> and NOINIT" (in the BACKUP topic). Bu, as mentioned before, SQL Server eit
her overwrites everything
> or not at all. This is how the engine work, so it doesn't relate to the ma
intenance wizard.
> Personally,. I don't use SKIP/NOSKIP at all, as I don't find those options
adding anything to
> INIT/NOINIT.
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asph
ttp://sqlblog.com/blogs/tibor_karaszi
> <use...@.tynemarch.co.uk> wrote in message
> news:1186054522.882732.218720@.d55g2000hsg.googlegroups.com...
>
>
>
>
>
>
> - Show quoted text -|||So what you want to do is to backup to the same backup device name and alway
s overwrite?
In my wizard (I'm on sp2, there has been improvements here...), I see an opt
ion "If backup files
exists:" and I select "Overwrite".
Here are the backup commands executed, as catched by Profiler:
BACKUP DATABASE [master] TO [MyDevice] WITH NOFORMAT, INIT, NAME =
N'master_backup_20070802151715', SKIP, REWIND, NOUNLOAD, STATS = 10
BACKUP DATABASE [model] TO [MyDevice] WITH NOFORMAT, NOINIT, NAME
=
N'model_backup_20070802151715', SKIP, REWIND, NOUNLOAD, STATS = 10
As you see, it does INIT for the first backup and NOINIT for the following b
ackups. Is above what
you want, ir are you saying that there's some problem with the TSQL above?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<usenet@.tynemarch.co.uk> wrote in message
news:1186057933.490529.68270@.l70g2000hse.googlegroups.com...
>I would happily overwrite everything but there doesn't seem to be that
> option either in the Wizard. You only have the option that it either
> expires or it doesn't as whatever you do it always puts in SKIP into
> the SQL. The only way you seem to be able to backup without having old
> backups is to backup to individual files rather than using a backup
> device as I am.
> Rob
> On 2 Aug, 12:58, "Tibor Karaszi"
> <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
>|||I could not get the wizard to generate any SQL with SKIP in it.
However, the answer to my problems was to use a one-off backup file
rather than have a pre-allocated backup device. I could then move to
the file to somewhere else and start afresh with a new file the next
day. Thanks for the help anyway.
On 2 Aug, 14:19, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> So what you want to do is to backup to the same backup device name and alw
ays overwrite?
> In my wizard (I'm on sp2, there has been improvements here...), I see an o
ption "If backup files
> exists:" and I select "Overwrite".
> Here are the backup commands executed, as catched by Profiler:
> BACKUP DATABASE [master] TO [MyDevice] WITH NOFORMAT, INIT, NAME
=
> N'master_backup_20070802151715', SKIP, REWIND, NOUNLOAD, STATS = 10
> BACKUP DATABASE [model] TO [MyDevice] WITH NOFORMAT, NOINIT, NAM
E =
> N'model_backup_20070802151715', SKIP, REWIND, NOUNLOAD, STATS = 10
> As you see, it does INIT for the first backup and NOINIT for the following
backups. Is above what
> you want, ir are you saying that there's some problem with the TSQL above?
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asph
ttp://sqlblog.com/blogs/tibor_karaszi
> <use...@.tynemarch.co.uk> wrote in message
> news:1186057933.490529.68270@.l70g2000hse.googlegroups.com...
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> - Show quoted text -

Maintinence Jobs vs Defag Jobs

Quick question, I have a maintinence job that optimizes (reorganizes back to
original size my databases back to the original amount of free space). I also
have jobs that defrag specific tables.
Will the maintinence job defrag as well as reorgainize.
I would like to get rid of my defrag jobs and have one maintinence job that
does both.
Yes. If you select Reorganize data and index pages in the maintenance
plans, it will execute dbcc dbreindex. If you select Remove unused
space from database files, it will execute dbcc shrinkdatabase.
Considerations in going this route is that dbreindex is your only
option in using a maintenance plan. There are different considerations
to take into account when determining whether to use dbreindex or
indexdefrag. You would want to check the following article:
Microsoft SQL Server 2000 Index Defragmentation Best Practices
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx
A consideration with shrinking is that it is a resource intensive
operation. Additionally, the maintenance plan will limit you to using
shrinkdatabase instead of shrinkfile. You have less control and
somewhat unpredictable individual file sizes when using
shrinkdatabase. If you shrink a database, then it grows back to the
size it was before the shrink and then you shrink it again, the
process can unnecessarily waste a lot of resources as well as
contributing to OS level fragmentation. You can find additional
information in this article:
http://www.karaszi.com/sqlserver/info_dont_shrink.asp
-Sue
On Mon, 25 Oct 2004 09:59:05 -0700, "robert_at_cbb"
<robertatcbb@.discussions.microsoft.com> wrote:

>Quick question, I have a maintinence job that optimizes (reorganizes back to
>original size my databases back to the original amount of free space). I also
>have jobs that defrag specific tables.
>Will the maintinence job defrag as well as reorgainize.
>I would like to get rid of my defrag jobs and have one maintinence job that
>does both.
|||Another consideration is that shrinking introduces logical fragmentation
that dbcc dbreindex removes - if you reindex then shrink you're shooting
yourself in the foot...
You should ask yourself why you have to shrink repeatedly - the reason the
db size grows is that SQL needs the extra space. If the db size grows and
then remains relatively static, you'd do best to leave it alone otherwise
you're wasting resources as Sue says.
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:knfvn0tq38v3a905ff208i5u134m35top5@.4ax.com...
> Yes. If you select Reorganize data and index pages in the maintenance
> plans, it will execute dbcc dbreindex. If you select Remove unused
> space from database files, it will execute dbcc shrinkdatabase.
> Considerations in going this route is that dbreindex is your only
> option in using a maintenance plan. There are different considerations
> to take into account when determining whether to use dbreindex or
> indexdefrag. You would want to check the following article:
> Microsoft SQL Server 2000 Index Defragmentation Best Practices
>
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx[vbcol=seagreen]
> A consideration with shrinking is that it is a resource intensive
> operation. Additionally, the maintenance plan will limit you to using
> shrinkdatabase instead of shrinkfile. You have less control and
> somewhat unpredictable individual file sizes when using
> shrinkdatabase. If you shrink a database, then it grows back to the
> size it was before the shrink and then you shrink it again, the
> process can unnecessarily waste a lot of resources as well as
> contributing to OS level fragmentation. You can find additional
> information in this article:
> http://www.karaszi.com/sqlserver/info_dont_shrink.asp
> -Sue
> On Mon, 25 Oct 2004 09:59:05 -0700, "robert_at_cbb"
> <robertatcbb@.discussions.microsoft.com> wrote:
to[vbcol=seagreen]
also[vbcol=seagreen]
that
>

Maintinence Jobs vs Defag Jobs

Quick question, I have a maintinence job that optimizes (reorganizes back to
original size my databases back to the original amount of free space). I also
have jobs that defrag specific tables.
Will the maintinence job defrag as well as reorgainize.
I would like to get rid of my defrag jobs and have one maintinence job that
does both.Yes. If you select Reorganize data and index pages in the maintenance
plans, it will execute dbcc dbreindex. If you select Remove unused
space from database files, it will execute dbcc shrinkdatabase.
Considerations in going this route is that dbreindex is your only
option in using a maintenance plan. There are different considerations
to take into account when determining whether to use dbreindex or
indexdefrag. You would want to check the following article:
Microsoft SQL Server 2000 Index Defragmentation Best Practices
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
A consideration with shrinking is that it is a resource intensive
operation. Additionally, the maintenance plan will limit you to using
shrinkdatabase instead of shrinkfile. You have less control and
somewhat unpredictable individual file sizes when using
shrinkdatabase. If you shrink a database, then it grows back to the
size it was before the shrink and then you shrink it again, the
process can unnecessarily waste a lot of resources as well as
contributing to OS level fragmentation. You can find additional
information in this article:
http://www.karaszi.com/sqlserver/info_dont_shrink.asp
-Sue
On Mon, 25 Oct 2004 09:59:05 -0700, "robert_at_cbb"
<robertatcbb@.discussions.microsoft.com> wrote:
>Quick question, I have a maintinence job that optimizes (reorganizes back to
>original size my databases back to the original amount of free space). I also
>have jobs that defrag specific tables.
>Will the maintinence job defrag as well as reorgainize.
>I would like to get rid of my defrag jobs and have one maintinence job that
>does both.|||Another consideration is that shrinking introduces logical fragmentation
that dbcc dbreindex removes - if you reindex then shrink you're shooting
yourself in the foot...
You should ask yourself why you have to shrink repeatedly - the reason the
db size grows is that SQL needs the extra space. If the db size grows and
then remains relatively static, you'd do best to leave it alone otherwise
you're wasting resources as Sue says.
Regards.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:knfvn0tq38v3a905ff208i5u134m35top5@.4ax.com...
> Yes. If you select Reorganize data and index pages in the maintenance
> plans, it will execute dbcc dbreindex. If you select Remove unused
> space from database files, it will execute dbcc shrinkdatabase.
> Considerations in going this route is that dbreindex is your only
> option in using a maintenance plan. There are different considerations
> to take into account when determining whether to use dbreindex or
> indexdefrag. You would want to check the following article:
> Microsoft SQL Server 2000 Index Defragmentation Best Practices
>
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
> A consideration with shrinking is that it is a resource intensive
> operation. Additionally, the maintenance plan will limit you to using
> shrinkdatabase instead of shrinkfile. You have less control and
> somewhat unpredictable individual file sizes when using
> shrinkdatabase. If you shrink a database, then it grows back to the
> size it was before the shrink and then you shrink it again, the
> process can unnecessarily waste a lot of resources as well as
> contributing to OS level fragmentation. You can find additional
> information in this article:
> http://www.karaszi.com/sqlserver/info_dont_shrink.asp
> -Sue
> On Mon, 25 Oct 2004 09:59:05 -0700, "robert_at_cbb"
> <robertatcbb@.discussions.microsoft.com> wrote:
> >Quick question, I have a maintinence job that optimizes (reorganizes back
to
> >original size my databases back to the original amount of free space). I
also
> >have jobs that defrag specific tables.
> >
> >Will the maintinence job defrag as well as reorgainize.
> >
> >I would like to get rid of my defrag jobs and have one maintinence job
that
> >does both.
>

Maintinence Jobs vs Defag Jobs

Quick question, I have a maintinence job that optimizes (reorganizes back to
original size my databases back to the original amount of free space). I als
o
have jobs that defrag specific tables.
Will the maintinence job defrag as well as reorgainize.
I would like to get rid of my defrag jobs and have one maintinence job that
does both.Yes. If you select Reorganize data and index pages in the maintenance
plans, it will execute dbcc dbreindex. If you select Remove unused
space from database files, it will execute dbcc shrinkdatabase.
Considerations in going this route is that dbreindex is your only
option in using a maintenance plan. There are different considerations
to take into account when determining whether to use dbreindex or
indexdefrag. You would want to check the following article:
Microsoft SQL Server 2000 Index Defragmentation Best Practices
http://www.microsoft.com/technet/pr...n/ss2kidbp.mspx
A consideration with shrinking is that it is a resource intensive
operation. Additionally, the maintenance plan will limit you to using
shrinkdatabase instead of shrinkfile. You have less control and
somewhat unpredictable individual file sizes when using
shrinkdatabase. If you shrink a database, then it grows back to the
size it was before the shrink and then you shrink it again, the
process can unnecessarily waste a lot of resources as well as
contributing to OS level fragmentation. You can find additional
information in this article:
http://www.karaszi.com/sqlserver/info_dont_shrink.asp
-Sue
On Mon, 25 Oct 2004 09:59:05 -0700, "robert_at_cbb"
<robertatcbb@.discussions.microsoft.com> wrote:

>Quick question, I have a maintinence job that optimizes (reorganizes back t
o
>original size my databases back to the original amount of free space). I al
so
>have jobs that defrag specific tables.
>Will the maintinence job defrag as well as reorgainize.
>I would like to get rid of my defrag jobs and have one maintinence job that
>does both.|||Another consideration is that shrinking introduces logical fragmentation
that dbcc dbreindex removes - if you reindex then shrink you're shooting
yourself in the foot...
You should ask yourself why you have to shrink repeatedly - the reason the
db size grows is that SQL needs the extra space. If the db size grows and
then remains relatively static, you'd do best to leave it alone otherwise
you're wasting resources as Sue says.
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:knfvn0tq38v3a905ff208i5u134m35top5@.
4ax.com...
> Yes. If you select Reorganize data and index pages in the maintenance
> plans, it will execute dbcc dbreindex. If you select Remove unused
> space from database files, it will execute dbcc shrinkdatabase.
> Considerations in going this route is that dbreindex is your only
> option in using a maintenance plan. There are different considerations
> to take into account when determining whether to use dbreindex or
> indexdefrag. You would want to check the following article:
> Microsoft SQL Server 2000 Index Defragmentation Best Practices
>
http://www.microsoft.com/technet/pr...n/ss2kidbp.mspx
> A consideration with shrinking is that it is a resource intensive
> operation. Additionally, the maintenance plan will limit you to using
> shrinkdatabase instead of shrinkfile. You have less control and
> somewhat unpredictable individual file sizes when using
> shrinkdatabase. If you shrink a database, then it grows back to the
> size it was before the shrink and then you shrink it again, the
> process can unnecessarily waste a lot of resources as well as
> contributing to OS level fragmentation. You can find additional
> information in this article:
> http://www.karaszi.com/sqlserver/info_dont_shrink.asp
> -Sue
> On Mon, 25 Oct 2004 09:59:05 -0700, "robert_at_cbb"
> <robertatcbb@.discussions.microsoft.com> wrote:
>
to[vbcol=seagreen]
also[vbcol=seagreen]
that[vbcol=seagreen]
>

Maintenence Plan

We are running SQL server 2000 on Windows 2000 and have a
number of servers. We have set up scheduled backup
maintenence plans which are set to back our databases,
transaction logs to disk then delete the transaction logs
and backup files after so many days. The backups are
always ok but For some reason the Transaction logs and
backup files are not being deleted which causes the disk
to fill up and databases to crash. We have checked the
permissions on the backup folders to see if the SQL
service account might not have had permissions set
correctly but this is not the case. Can anyone help with
this.BigA,
Can you verify that a tape backup job does not have an open file lock on
the files? I have had this problem and the culprit was a tape backup job
copying the files to tape, and leaving the files in a "open" state.
sqlmaint is then unable to delete the files and "fails".
There are issues with MSDE, so check that you are not using MSDE.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
BigA wrote:
> We are running SQL server 2000 on Windows 2000 and have a
> number of servers. We have set up scheduled backup
> maintenence plans which are set to back our databases,
> transaction logs to disk then delete the transaction logs
> and backup files after so many days. The backups are
> always ok but For some reason the Transaction logs and
> backup files are not being deleted which causes the disk
> to fill up and databases to crash. We have checked the
> permissions on the backup folders to see if the SQL
> service account might not have had permissions set
> correctly but this is not the case. Can anyone help with
> this.|||We use Veritas Backup Exec and it's does backup open
files with a lock. So could this be the culprit? Would
this only happen if the tape backup was at the same time
as the Maintenence plan?
>--Original Message--
>BigA,
>Can you verify that a tape backup job does not have an
open file lock on
>the files? I have had this problem and the culprit was a
tape backup job
>copying the files to tape, and leaving the files in
a "open" state.
>sqlmaint is then unable to delete the files and "fails".
>There are issues with MSDE, so check that you are not
using MSDE.
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>BigA wrote:
have a[vbcol=seagreen]
logs[vbcol=seagreen]
disk[vbcol=seagreen]
the[vbcol=seagreen]
with[vbcol=seagreen]
>.
>|||BigA,
Yes, this is likely the culprit. Check your tape back windows do not
overlap your SQL Server backup jobs. The problem should only occur if
the maintenance plan is trying to delete a file whilst backup exec is
copying it to tape.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
BigA wrote:
> We use Veritas Backup Exec and it's does backup open
> files with a lock. So could this be the culprit? Would
> this only happen if the tape backup was at the same time
> as the Maintenence plan?
>|||Thanks for your fast response. I will give this a try.
sounds like it could be the answer.
>--Original Message--
>BigA,
>Yes, this is likely the culprit. Check your tape back
windows do not
>overlap your SQL Server backup jobs. The problem should
only occur if
>the maintenance plan is trying to delete a file whilst
backup exec is
>copying it to tape.
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>BigA wrote:
Would[vbcol=seagreen]
time[vbcol=seagreen]
>.
>

Maintenence Plan

We are running SQL server 2000 on Windows 2000 and have a
number of servers. We have set up scheduled backup
maintenence plans which are set to back our databases,
transaction logs to disk then delete the transaction logs
and backup files after so many days. The backups are
always ok but For some reason the Transaction logs and
backup files are not being deleted which causes the disk
to fill up and databases to crash. We have checked the
permissions on the backup folders to see if the SQL
service account might not have had permissions set
correctly but this is not the case. Can anyone help with
this.BigA,
Can you verify that a tape backup job does not have an open file lock on
the files? I have had this problem and the culprit was a tape backup job
copying the files to tape, and leaving the files in a "open" state.
sqlmaint is then unable to delete the files and "fails".
There are issues with MSDE, so check that you are not using MSDE.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
BigA wrote:
> We are running SQL server 2000 on Windows 2000 and have a
> number of servers. We have set up scheduled backup
> maintenence plans which are set to back our databases,
> transaction logs to disk then delete the transaction logs
> and backup files after so many days. The backups are
> always ok but For some reason the Transaction logs and
> backup files are not being deleted which causes the disk
> to fill up and databases to crash. We have checked the
> permissions on the backup folders to see if the SQL
> service account might not have had permissions set
> correctly but this is not the case. Can anyone help with
> this.|||We use Veritas Backup Exec and it's does backup open
files with a lock. So could this be the culprit? Would
this only happen if the tape backup was at the same time
as the Maintenence plan?
>--Original Message--
>BigA,
>Can you verify that a tape backup job does not have an
open file lock on
>the files? I have had this problem and the culprit was a
tape backup job
>copying the files to tape, and leaving the files in
a "open" state.
>sqlmaint is then unable to delete the files and "fails".
>There are issues with MSDE, so check that you are not
using MSDE.
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>BigA wrote:
>> We are running SQL server 2000 on Windows 2000 and
have a
>> number of servers. We have set up scheduled backup
>> maintenence plans which are set to back our databases,
>> transaction logs to disk then delete the transaction
logs
>> and backup files after so many days. The backups are
>> always ok but For some reason the Transaction logs and
>> backup files are not being deleted which causes the
disk
>> to fill up and databases to crash. We have checked
the
>> permissions on the backup folders to see if the SQL
>> service account might not have had permissions set
>> correctly but this is not the case. Can anyone help
with
>> this.
>.
>|||BigA,
Yes, this is likely the culprit. Check your tape back windows do not
overlap your SQL Server backup jobs. The problem should only occur if
the maintenance plan is trying to delete a file whilst backup exec is
copying it to tape.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
BigA wrote:
> We use Veritas Backup Exec and it's does backup open
> files with a lock. So could this be the culprit? Would
> this only happen if the tape backup was at the same time
> as the Maintenence plan?
>|||Thanks for your fast response. I will give this a try.
sounds like it could be the answer.
>--Original Message--
>BigA,
>Yes, this is likely the culprit. Check your tape back
windows do not
>overlap your SQL Server backup jobs. The problem should
only occur if
>the maintenance plan is trying to delete a file whilst
backup exec is
>copying it to tape.
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>BigA wrote:
>> We use Veritas Backup Exec and it's does backup open
>> files with a lock. So could this be the culprit?
Would
>> this only happen if the tape backup was at the same
time
>> as the Maintenence plan?
>.
>

Maintenence Plan

We are running SQL server 2000 on Windows 2000 and have a
number of servers. We have set up scheduled backup
maintenence plans which are set to back our databases,
transaction logs to disk then delete the transaction logs
and backup files after so many days. The backups are
always ok but For some reason the Transaction logs and
backup files are not being deleted which causes the disk
to fill up and databases to crash. We have checked the
permissions on the backup folders to see if the SQL
service account might not have had permissions set
correctly but this is not the case. Can anyone help with
this.
BigA,
Can you verify that a tape backup job does not have an open file lock on
the files? I have had this problem and the culprit was a tape backup job
copying the files to tape, and leaving the files in a "open" state.
sqlmaint is then unable to delete the files and "fails".
There are issues with MSDE, so check that you are not using MSDE.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
BigA wrote:
> We are running SQL server 2000 on Windows 2000 and have a
> number of servers. We have set up scheduled backup
> maintenence plans which are set to back our databases,
> transaction logs to disk then delete the transaction logs
> and backup files after so many days. The backups are
> always ok but For some reason the Transaction logs and
> backup files are not being deleted which causes the disk
> to fill up and databases to crash. We have checked the
> permissions on the backup folders to see if the SQL
> service account might not have had permissions set
> correctly but this is not the case. Can anyone help with
> this.
|||We use Veritas Backup Exec and it's does backup open
files with a lock. So could this be the culprit? Would
this only happen if the tape backup was at the same time
as the Maintenence plan?
>--Original Message--
>BigA,
>Can you verify that a tape backup job does not have an
open file lock on
>the files? I have had this problem and the culprit was a
tape backup job
>copying the files to tape, and leaving the files in
a "open" state.
>sqlmaint is then unable to delete the files and "fails".
>There are issues with MSDE, so check that you are not
using MSDE.[vbcol=seagreen]
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>BigA wrote:
have a[vbcol=seagreen]
logs[vbcol=seagreen]
disk[vbcol=seagreen]
the[vbcol=seagreen]
with
>.
>
|||BigA,
Yes, this is likely the culprit. Check your tape back windows do not
overlap your SQL Server backup jobs. The problem should only occur if
the maintenance plan is trying to delete a file whilst backup exec is
copying it to tape.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
BigA wrote:
> We use Veritas Backup Exec and it's does backup open
> files with a lock. So could this be the culprit? Would
> this only happen if the tape backup was at the same time
> as the Maintenence plan?
>
|||Thanks for your fast response. I will give this a try.
sounds like it could be the answer.
>--Original Message--
>BigA,
>Yes, this is likely the culprit. Check your tape back
windows do not
>overlap your SQL Server backup jobs. The problem should
only occur if
>the maintenance plan is trying to delete a file whilst
backup exec is[vbcol=seagreen]
>copying it to tape.
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>BigA wrote:
Would[vbcol=seagreen]
time
>.
>

Maintenance Plans

When you setup a maintenance plan to back up a database and you give it the
option to delete a database older than 1 day. Does it delete the old backup
before it creates the new backup?
After. There's no setting for this, so you cannot change this behavior. Maint plans are totally
reworked in 2005, though.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<Patricia> wrote in message news:OVpW%23yfFGHA.3936@.TK2MSFTNGP12.phx.gbl...
> When you setup a maintenance plan to back up a database and you give it the option to delete a
> database older than 1 day. Does it delete the old backup before it creates the new backup?
>
>
|||The clean up routines will run last unless you have edited the job and
changed the order.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
<Patricia> wrote in message news:OVpW%23yfFGHA.3936@.TK2MSFTNGP12.phx.gbl...
> When you setup a maintenance plan to back up a database and you give it
> the option to delete a database older than 1 day. Does it delete the old
> backup before it creates the new backup?
>
>

Maintenance Plans

1) Is it a good practice to use the Maintenance Plans to back up the
database, trans logs, and organize the index, and verify the data?
2) How often would it be good practice to run the recreating of index and
verifying the data?
3) Or it's better just create one jobs to backup database etc?
4) Are there any negative to using Maintenance Plans
Thank You
There are no one size fits all answer for these types of questions. If you have responsibility for
these things, then you have responsibility to understand how backup etc work in SQL Server, learn
how the maint wizard work and based on that make decisions whether maint wiz is good for your
organization. Regarding reindexing, I suggest you read
http://www.microsoft.com/technet/pro...ss2kidbp.mspx.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Victoria Morrison" <Victoria Morrison@.discussions.microsoft.com> wrote in message
news:CCA01C5B-D86A-4846-8682-50DBA0B24C37@.microsoft.com...
> 1) Is it a good practice to use the Maintenance Plans to back up the
> database, trans logs, and organize the index, and verify the data?
> 2) How often would it be good practice to run the recreating of index and
> verifying the data?
> 3) Or it's better just create one jobs to backup database etc?
> 4) Are there any negative to using Maintenance Plans
> Thank You
|||"Tibor Karaszi" wrote:

> There are no one size fits all answer for these types of questions. If you have responsibility for
> these things, then you have responsibility to understand how backup etc work in SQL Server, learn
> how the maint wizard work and based on that make decisions whether maint wiz is good for your
> organization. Regarding reindexing, I suggest you read
> http://www.microsoft.com/technet/pro...ss2kidbp.mspx.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Victoria Morrison" <Victoria Morrison@.discussions.microsoft.com> wrote in message
> news:CCA01C5B-D86A-4846-8682-50DBA0B24C37@.microsoft.com...
>
>

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...
>
|||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...
>

Maintenance Plans

1) Is it a good practice to use the Maintenance Plans to back up the
database, trans logs, and organize the index, and verify the data?
2) How often would it be good practice to run the recreating of index and
verifying the data?
3) Or it's better just create one jobs to backup database etc?
4) Are there any negative to using Maintenance Plans
Thank YouThere are no one size fits all answer for these types of questions. If you have responsibility for
these things, then you have responsibility to understand how backup etc work in SQL Server, learn
how the maint wizard work and based on that make decisions whether maint wiz is good for your
organization. Regarding reindexing, I suggest you read
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Victoria Morrison" <Victoria Morrison@.discussions.microsoft.com> wrote in message
news:CCA01C5B-D86A-4846-8682-50DBA0B24C37@.microsoft.com...
> 1) Is it a good practice to use the Maintenance Plans to back up the
> database, trans logs, and organize the index, and verify the data?
> 2) How often would it be good practice to run the recreating of index and
> verifying the data?
> 3) Or it's better just create one jobs to backup database etc?
> 4) Are there any negative to using Maintenance Plans
> Thank You|||"Tibor Karaszi" wrote:
> There are no one size fits all answer for these types of questions. If you have responsibility for
> these things, then you have responsibility to understand how backup etc work in SQL Server, learn
> how the maint wizard work and based on that make decisions whether maint wiz is good for your
> organization. Regarding reindexing, I suggest you read
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Victoria Morrison" <Victoria Morrison@.discussions.microsoft.com> wrote in message
> news:CCA01C5B-D86A-4846-8682-50DBA0B24C37@.microsoft.com...
> > 1) Is it a good practice to use the Maintenance Plans to back up the
> > database, trans logs, and organize the index, and verify the data?
> >
> > 2) How often would it be good practice to run the recreating of index and
> > verifying the data?
> >
> > 3) Or it's better just create one jobs to backup database etc?
> >
> > 4) Are there any negative to using Maintenance Plans
> >
> > Thank You
>
>

Maintenance Plans

When you setup a maintenance plan to back up a database and you give it the
option to delete a database older than 1 day. Does it delete the old backup
before it creates the new backup?After. There's no setting for this, so you cannot change this behavior. Maint plans are totally
reworked in 2005, though.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<Patricia> wrote in message news:OVpW%23yfFGHA.3936@.TK2MSFTNGP12.phx.gbl...
> When you setup a maintenance plan to back up a database and you give it the option to delete a
> database older than 1 day. Does it delete the old backup before it creates the new backup?
>
>|||The clean up routines will run last unless you have edited the job and
changed the order.
--
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
<Patricia> wrote in message news:OVpW%23yfFGHA.3936@.TK2MSFTNGP12.phx.gbl...
> When you setup a maintenance plan to back up a database and you give it
> the option to delete a database older than 1 day. Does it delete the old
> backup before it creates the new backup?
>
>

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

1) Is it a good practice to use the Maintenance Plans to back up the
database, trans logs, and organize the index, and verify the data?
2) How often would it be good practice to run the recreating of index and
verifying the data?
3) Or it's better just create one jobs to backup database etc?
4) Are there any negative to using Maintenance Plans
Thank YouThere are no one size fits all answer for these types of questions. If you h
ave responsibility for
these things, then you have responsibility to understand how backup etc work
in SQL Server, learn
how the maint wizard work and based on that make decisions whether maint wiz
is good for your
organization. Regarding reindexing, I suggest you read
http://www.microsoft.com/technet/pr...ver/default.asp
http://www.solidqualitylearning.com/
"Victoria Morrison" <Victoria Morrison@.discussions.microsoft.com> wrote in m
essage
news:CCA01C5B-D86A-4846-8682-50DBA0B24C37@.microsoft.com...
> 1) Is it a good practice to use the Maintenance Plans to back up the
> database, trans logs, and organize the index, and verify the data?
> 2) How often would it be good practice to run the recreating of index and
> verifying the data?
> 3) Or it's better just create one jobs to backup database etc?
> 4) Are there any negative to using Maintenance Plans
> Thank You|||"Tibor Karaszi" wrote:

> There are no one size fits all answer for these types of questions. If you
have responsibility for
> these things, then you have responsibility to understand how backup etc wo
rk in SQL Server, learn
> how the maint wizard work and based on that make decisions whether maint w
iz is good for your
> organization. Regarding reindexing, I suggest you read
> http://www.microsoft.com/technet/pr...ver/default.asp
> http://www.solidqualitylearning.com/
>
> "Victoria Morrison" <Victoria Morrison@.discussions.microsoft.com> wrote in
message
> news:CCA01C5B-D86A-4846-8682-50DBA0B24C37@.microsoft.com...
>
>

Maintenance Plans

When you setup a maintenance plan to back up a database and you give it the
option to delete a database older than 1 day. Does it delete the old backup
before it creates the new backup?After. There's no setting for this, so you cannot change this behavior. Main
t plans are totally
reworked in 2005, though.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<Patricia> wrote in message news:OVpW%23yfFGHA.3936@.TK2MSFTNGP12.phx.gbl...
> When you setup a maintenance plan to back up a database and you give it th
e option to delete a
> database older than 1 day. Does it delete the old backup before it create
s the new backup?
>
>|||The clean up routines will run last unless you have edited the job and
changed the order.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
<Patricia> wrote in message news:OVpW%23yfFGHA.3936@.TK2MSFTNGP12.phx.gbl...
> When you setup a maintenance plan to back up a database and you give it
> the option to delete a database older than 1 day. Does it delete the old
> backup before it creates the new backup?
>
>