Hi there,
I'm maintaining a database which is used mainly during officehours.
Plenty of time to do maintenance and batchprocesses. In the near future
we are going to a 24/7 situation, and I wonder what impact this has on
hour maintenance and batchjobs. I can think of solutions myself, like
looking for lowest activitytimes to plan batchjobs and maintenance,
maybe create a copy of the database to run batchjobs on. Still, anyone
know of solutions to tackle these things? Is there a site maybe where a
change to 24/7 availability is describes? Any ppl with experiences with
such a process? Advice?
Tnx,
Hans Brouwer
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!One thing is you might consider is to not reorganize data (assuming you do in the first place) using
DBCC DBREINDEX, instead consider using DBCC INDEXDEFRAG.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Hans Brouwer" <hansbrouwer@.hotmail.com> wrote in message
news:OFU5T4ylDHA.2068@.TK2MSFTNGP09.phx.gbl...
> Hi there,
> I'm maintaining a database which is used mainly during officehours.
> Plenty of time to do maintenance and batchprocesses. In the near future
> we are going to a 24/7 situation, and I wonder what impact this has on
> hour maintenance and batchjobs. I can think of solutions myself, like
> looking for lowest activitytimes to plan batchjobs and maintenance,
> maybe create a copy of the database to run batchjobs on. Still, anyone
> know of solutions to tackle these things? Is there a site maybe where a
> change to 24/7 availability is describes? Any ppl with experiences with
> such a process? Advice?
> Tnx,
> Hans Brouwer
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!|||Hi Hans,
As I understand, since 24/7 requires high availability, lengthy maintenance
operations during working hours are not recommended. I think clustering may
worth consideration.
This article discusses the technology of clustering, and the steps involved
in setting up a cluster for an e-commerce site. It also examines how
clustering has been implemented in the sample Duwamish Online store.
Building a Highly Available Database Cluster
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnduwon/htm
l/d5clustering.asp
This article describes ways to reduce or eliminate downtime in a Microsoft
Commerce Server 2000 environment. It focuses primarily on the hardware and
software needed to create a Commerce Server site with no single point of
failure.
Planning for Reliability and High Availability - SQL Server Availability
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dncomsrv/ht
ml/planavailability.asp
For additional information regarding this issue, please refer to the
following articles:
Microsoft SQL Server MegaServers: Achieving Software Scale-Out
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/htm
l/megasrvs.asp
Designing Federated Database Servers for High Availability
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/optimsql/cm
_fedserv_8dq1.asp
High-Availability Solutions Using Microsoft Windows 2000 Cluster Service
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbiz2k2/ht
ml/bts_2002clustering.asp
Thanks for using MSDN newsgroup.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Showing posts with label maintenance. Show all posts
Showing posts with label maintenance. Show all posts
Thursday, March 8, 2012
Saturday, February 25, 2012
2005 SP2: failed to modify maintenance paln
After upgrading to SP2, I created a maintenance plan in the management studio using the wizard. The plan executes OK. But when I tried to modify it, I got the following error, and cannot load and modify:
Value cannot be null.
Parameter name: component (System.Design)
Please help ASAP.
Ed
Can you please submit this as a defect on Microsoft Connect? Please include steps to reproduce the problem, screen shots, and as much details information about the error message (sometimes you can copy the "stack trace" which is very useful to our dev team).
Microsoft Connect:
http://connect.microsoft.com/SQLServer/Feedback/
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
2005 SP2: failed to modify maintenance paln
After upgrading to SP2, I created a maintenance plan in the management studio using the wizard. The plan executes OK. But when I tried to modify it, I got the following error, and cannot load and modify:
Value cannot be null.
Parameter name: component (System.Design)
Please help ASAP.
Ed
Can you please submit this as a defect on Microsoft Connect? Please include steps to reproduce the problem, screen shots, and as much details information about the error message (sometimes you can copy the "stack trace" which is very useful to our dev team).
Microsoft Connect:
http://connect.microsoft.com/SQLServer/Feedback/
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
Thursday, February 16, 2012
2005 Maintenance Plans
Hi,
can anyone tell me if it is possible to cycle the backup files. They just
seem to append, but I wany to cycle them based on a 7 day period.
TIAwhen you say cycle, i believe you want to delete bkup files older than
a week or something, if in that case you have to use another task
called maintenance cleanup task..which will do that for you
can anyone tell me if it is possible to cycle the backup files. They just
seem to append, but I wany to cycle them based on a 7 day period.
TIAwhen you say cycle, i believe you want to delete bkup files older than
a week or something, if in that case you have to use another task
called maintenance cleanup task..which will do that for you
2005 Maintenance Plans
Hi,
can anyone tell me if it is possible to cycle the backup files. They just
seem to append, but I wany to cycle them based on a 7 day period.
TIA
when you say cycle, i believe you want to delete bkup files older than
a week or something, if in that case you have to use another task
called maintenance cleanup task..which will do that for you
can anyone tell me if it is possible to cycle the backup files. They just
seem to append, but I wany to cycle them based on a 7 day period.
TIA
when you say cycle, i believe you want to delete bkup files older than
a week or something, if in that case you have to use another task
called maintenance cleanup task..which will do that for you
2005 Maintenance Plans
Hi,
can anyone tell me if it is possible to cycle the backup files. They just
seem to append, but I wany to cycle them based on a 7 day period.
TIAwhen you say cycle, i believe you want to delete bkup files older than
a week or something, if in that case you have to use another task
called maintenance cleanup task..which will do that for you
can anyone tell me if it is possible to cycle the backup files. They just
seem to append, but I wany to cycle them based on a 7 day period.
TIAwhen you say cycle, i believe you want to delete bkup files older than
a week or something, if in that case you have to use another task
called maintenance cleanup task..which will do that for you
2005 Maintenance Plan or Security bug?
Curious if this scenario is by design or a possible bug. As recommended by MS best practices for SQL 2000 we always removed the BUILTIN\Administrators login. After doing the same on our 2005 installations it appears to have caused errors in the edit\view functionality in the Maintenance Plans and jobs. One example is to open a plan in modify mode and then select the logging button. - 'Unhandled exception has occured in a component in your application' (have debug file)
Another error occurs when attempting to edit a step of the Maintenance Plan job. Select the subplan step > edit > select any tab other than General and this error occurs.
TITLE: SSIS Execution Properties
The LoadFromSQLServer method has encountered OLE DB error code 0x80040E4D (Login failed for user 'domain\xxxxx'.). The SQL statement that was issued has failed.
I re-added the BUILTIN\Administrator to one 2005 instance and it corrected the errors completely. We are running Enterprise edition on W2K3 SP1 server using mixed mode auth. I do have Admin rights to the servers so it appears that windows security is being used for some maintenance plan functionality rather than the sql security. The errors could be reproduced running the Management Studio locally or remote connected as sa.
Any insight to this weirdness would be appreciated.
Allison
Check that you SQL Services have explicit access granted and aren't going through BUILTIN admins|||Not sure exactly what you mean by 'have explicit access' but I did add the SQL Services start up account (domain account with server admin rights) as a sysadmin and it did not correct the problem.
All jobs execute with out the start up account having an explicit sql login.
Allison|||The (Login failed for user 'domain\xxxxx'.) is this a literal posting or have you blocked out the name of the account the SQL agent uses?
|||Might be that something in your plan accesses a location that doesn't exist or no permissions a granted for the user opening the plan...there should be useful information in the paramters passed to the LoadFromSQLServer method that could resolve this.
|||Yes I did block it out of the message but it was not the SQL Services account in the error message it was my user account. So what you are saying is that I can create a maintenance plan but when I attempt to edit it my credentials, not the service credentials are being checked?
Not sure hove to look at the parameters for LoadFromSQLServer.
Thanks
A|||Yes, when you automate a job it will run under a specified or agent account. When you are editing it, your account is being used to access the objects involved.
2005 Maintenance Plan Best Practices?
Does anyone have a link to resources or suggestions on best practices for
setting up proper maintenance plans with SQL 2005 (Workgroup)?
We have a new 2005 database that we are preparing for production and want to
make sure we cover off all the bases in setting up our maintenance plan.
This will be for an online reservation system that will process approx
300-600 transactions per day. The system needs to be live 24/7/365 or as
near to this as possible.
The initial database is expected to be around 600MB is size with approx 40
tables and grow from there with new transactions.
What we be a good plan for such a system for a starting point? Is a single
daily plan sufficient or should we be setting up multiple plans to handle
backups, tuning, shrinking, etc separately?
Any suggestions/comments would be appreciated.What ever you do don't shrink the database. See here:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
How often you do backups are dependent on how much data you can afford to
loose. While this is for 2000 the principles still hold true.
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
Andrew J. Kelly SQL MVP
"ML" <schooner@.accesswave.ca> wrote in message
news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
> to make sure we cover off all the bases in setting up our maintenance
> plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a
> single daily plan sufficient or should we be setting up multiple plans to
> handle backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
>
>|||On Aug 6, 1:13 pm, "ML" <schoo...@.accesswave.ca> wrote:
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want to
> make sure we cover off all the bases in setting up our maintenance plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a single
> daily plan sufficient or should we be setting up multiple plans to handle
> backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
There is this: http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops4.mspx|||"ML" <schooner@.accesswave.ca> wrote in message
news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
> to make sure we cover off all the bases in setting up our maintenance
> plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a
> single daily plan sufficient or should we be setting up multiple plans to
> handle backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
>
Thank you for the comment so far. I think we will start off with daily full
backups and transaction log backups every 15 mins.
For the database integrity check, is it best to run this before or after a
full backup?
In terms of the other maintenance tasks (rebuild indexes, update statistics,
etc) how often should these typically be run?|||As you probably realize, there are not simple "one size fits all" answers to these question. Reading
up on the subject is what I recommend:
> For the database integrity check, is it best to run this before or after a full backup?
http://blogs.msdn.com/sqlserverstorageengine/archive/2006/07/23/675963.aspx
And other articles on that blog.
> In terms of the other maintenance tasks (rebuild indexes, update statistics, etc) how often should
> these typically be run?
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
Above article hasn't been updated for 2005, but basic concepts still applies.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"ML" <schooner@.accesswave.ca> wrote in message news:OabaWpN2HHA.1124@.TK2MSFTNGP06.phx.gbl...
> "ML" <schooner@.accesswave.ca> wrote in message news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
>> Does anyone have a link to resources or suggestions on best practices for setting up proper
>> maintenance plans with SQL 2005 (Workgroup)?
>> We have a new 2005 database that we are preparing for production and want to make sure we cover
>> off all the bases in setting up our maintenance plan.
>> This will be for an online reservation system that will process approx 300-600 transactions per
>> day. The system needs to be live 24/7/365 or as near to this as possible.
>> The initial database is expected to be around 600MB is size with approx 40 tables and grow from
>> there with new transactions.
>> What we be a good plan for such a system for a starting point? Is a single daily plan sufficient
>> or should we be setting up multiple plans to handle backups, tuning, shrinking, etc separately?
>> Any suggestions/comments would be appreciated.
> Thank you for the comment so far. I think we will start off with daily full backups and
> transaction log backups every 15 mins.
> For the database integrity check, is it best to run this before or after a full backup?
> In terms of the other maintenance tasks (rebuild indexes, update statistics, etc) how often should
> these typically be run?
>
setting up proper maintenance plans with SQL 2005 (Workgroup)?
We have a new 2005 database that we are preparing for production and want to
make sure we cover off all the bases in setting up our maintenance plan.
This will be for an online reservation system that will process approx
300-600 transactions per day. The system needs to be live 24/7/365 or as
near to this as possible.
The initial database is expected to be around 600MB is size with approx 40
tables and grow from there with new transactions.
What we be a good plan for such a system for a starting point? Is a single
daily plan sufficient or should we be setting up multiple plans to handle
backups, tuning, shrinking, etc separately?
Any suggestions/comments would be appreciated.What ever you do don't shrink the database. See here:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
How often you do backups are dependent on how much data you can afford to
loose. While this is for 2000 the principles still hold true.
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
Andrew J. Kelly SQL MVP
"ML" <schooner@.accesswave.ca> wrote in message
news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
> to make sure we cover off all the bases in setting up our maintenance
> plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a
> single daily plan sufficient or should we be setting up multiple plans to
> handle backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
>
>|||On Aug 6, 1:13 pm, "ML" <schoo...@.accesswave.ca> wrote:
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want to
> make sure we cover off all the bases in setting up our maintenance plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a single
> daily plan sufficient or should we be setting up multiple plans to handle
> backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
There is this: http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops4.mspx|||"ML" <schooner@.accesswave.ca> wrote in message
news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
> to make sure we cover off all the bases in setting up our maintenance
> plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a
> single daily plan sufficient or should we be setting up multiple plans to
> handle backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
>
Thank you for the comment so far. I think we will start off with daily full
backups and transaction log backups every 15 mins.
For the database integrity check, is it best to run this before or after a
full backup?
In terms of the other maintenance tasks (rebuild indexes, update statistics,
etc) how often should these typically be run?|||As you probably realize, there are not simple "one size fits all" answers to these question. Reading
up on the subject is what I recommend:
> For the database integrity check, is it best to run this before or after a full backup?
http://blogs.msdn.com/sqlserverstorageengine/archive/2006/07/23/675963.aspx
And other articles on that blog.
> In terms of the other maintenance tasks (rebuild indexes, update statistics, etc) how often should
> these typically be run?
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
Above article hasn't been updated for 2005, but basic concepts still applies.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"ML" <schooner@.accesswave.ca> wrote in message news:OabaWpN2HHA.1124@.TK2MSFTNGP06.phx.gbl...
> "ML" <schooner@.accesswave.ca> wrote in message news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
>> Does anyone have a link to resources or suggestions on best practices for setting up proper
>> maintenance plans with SQL 2005 (Workgroup)?
>> We have a new 2005 database that we are preparing for production and want to make sure we cover
>> off all the bases in setting up our maintenance plan.
>> This will be for an online reservation system that will process approx 300-600 transactions per
>> day. The system needs to be live 24/7/365 or as near to this as possible.
>> The initial database is expected to be around 600MB is size with approx 40 tables and grow from
>> there with new transactions.
>> What we be a good plan for such a system for a starting point? Is a single daily plan sufficient
>> or should we be setting up multiple plans to handle backups, tuning, shrinking, etc separately?
>> Any suggestions/comments would be appreciated.
> Thank you for the comment so far. I think we will start off with daily full backups and
> transaction log backups every 15 mins.
> For the database integrity check, is it best to run this before or after a full backup?
> In terms of the other maintenance tasks (rebuild indexes, update statistics, etc) how often should
> these typically be run?
>
2005 Maintenance Plan Best Practices?
Does anyone have a link to resources or suggestions on best practices for
setting up proper maintenance plans with SQL 2005 (Workgroup)?
We have a new 2005 database that we are preparing for production and want to
make sure we cover off all the bases in setting up our maintenance plan.
This will be for an online reservation system that will process approx
300-600 transactions per day. The system needs to be live 24/7/365 or as
near to this as possible.
The initial database is expected to be around 600MB is size with approx 40
tables and grow from there with new transactions.
What we be a good plan for such a system for a starting point? Is a single
daily plan sufficient or should we be setting up multiple plans to handle
backups, tuning, shrinking, etc separately?
Any suggestions/comments would be appreciated.
What ever you do don't shrink the database. See here:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
How often you do backups are dependent on how much data you can afford to
loose. While this is for 2000 the principles still hold true.
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
Andrew J. Kelly SQL MVP
"ML" <schooner@.accesswave.ca> wrote in message
news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
> to make sure we cover off all the bases in setting up our maintenance
> plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a
> single daily plan sufficient or should we be setting up multiple plans to
> handle backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
>
>
|||"ML" <schooner@.accesswave.ca> wrote in message
news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
> to make sure we cover off all the bases in setting up our maintenance
> plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a
> single daily plan sufficient or should we be setting up multiple plans to
> handle backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
>
Thank you for the comment so far. I think we will start off with daily full
backups and transaction log backups every 15 mins.
For the database integrity check, is it best to run this before or after a
full backup?
In terms of the other maintenance tasks (rebuild indexes, update statistics,
etc) how often should these typically be run?
|||As you probably realize, there are not simple "one size fits all" answers to these question. Reading
up on the subject is what I recommend:
> For the database integrity check, is it best to run this before or after a full backup?
http://blogs.msdn.com/sqlserverstorageengine/archive/2006/07/23/675963.aspx
And other articles on that blog.
> In terms of the other maintenance tasks (rebuild indexes, update statistics, etc) how often should
> these typically be run?
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
Above article hasn't been updated for 2005, but basic concepts still applies.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"ML" <schooner@.accesswave.ca> wrote in message news:OabaWpN2HHA.1124@.TK2MSFTNGP06.phx.gbl...
> "ML" <schooner@.accesswave.ca> wrote in message news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Thank you for the comment so far. I think we will start off with daily full backups and
> transaction log backups every 15 mins.
> For the database integrity check, is it best to run this before or after a full backup?
> In terms of the other maintenance tasks (rebuild indexes, update statistics, etc) how often should
> these typically be run?
>
setting up proper maintenance plans with SQL 2005 (Workgroup)?
We have a new 2005 database that we are preparing for production and want to
make sure we cover off all the bases in setting up our maintenance plan.
This will be for an online reservation system that will process approx
300-600 transactions per day. The system needs to be live 24/7/365 or as
near to this as possible.
The initial database is expected to be around 600MB is size with approx 40
tables and grow from there with new transactions.
What we be a good plan for such a system for a starting point? Is a single
daily plan sufficient or should we be setting up multiple plans to handle
backups, tuning, shrinking, etc separately?
Any suggestions/comments would be appreciated.
What ever you do don't shrink the database. See here:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
How often you do backups are dependent on how much data you can afford to
loose. While this is for 2000 the principles still hold true.
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
Andrew J. Kelly SQL MVP
"ML" <schooner@.accesswave.ca> wrote in message
news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
> to make sure we cover off all the bases in setting up our maintenance
> plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a
> single daily plan sufficient or should we be setting up multiple plans to
> handle backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
>
>
|||"ML" <schooner@.accesswave.ca> wrote in message
news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
> to make sure we cover off all the bases in setting up our maintenance
> plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a
> single daily plan sufficient or should we be setting up multiple plans to
> handle backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
>
Thank you for the comment so far. I think we will start off with daily full
backups and transaction log backups every 15 mins.
For the database integrity check, is it best to run this before or after a
full backup?
In terms of the other maintenance tasks (rebuild indexes, update statistics,
etc) how often should these typically be run?
|||As you probably realize, there are not simple "one size fits all" answers to these question. Reading
up on the subject is what I recommend:
> For the database integrity check, is it best to run this before or after a full backup?
http://blogs.msdn.com/sqlserverstorageengine/archive/2006/07/23/675963.aspx
And other articles on that blog.
> In terms of the other maintenance tasks (rebuild indexes, update statistics, etc) how often should
> these typically be run?
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
Above article hasn't been updated for 2005, but basic concepts still applies.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"ML" <schooner@.accesswave.ca> wrote in message news:OabaWpN2HHA.1124@.TK2MSFTNGP06.phx.gbl...
> "ML" <schooner@.accesswave.ca> wrote in message news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Thank you for the comment so far. I think we will start off with daily full backups and
> transaction log backups every 15 mins.
> For the database integrity check, is it best to run this before or after a full backup?
> In terms of the other maintenance tasks (rebuild indexes, update statistics, etc) how often should
> these typically be run?
>
2005 Maintenance Plan Best Practices?
Does anyone have a link to resources or suggestions on best practices for
setting up proper maintenance plans with SQL 2005 (Workgroup)?
We have a new 2005 database that we are preparing for production and want to
make sure we cover off all the bases in setting up our maintenance plan.
This will be for an online reservation system that will process approx
300-600 transactions per day. The system needs to be live 24/7/365 or as
near to this as possible.
The initial database is expected to be around 600MB is size with approx 40
tables and grow from there with new transactions.
What we be a good plan for such a system for a starting point? Is a single
daily plan sufficient or should we be setting up multiple plans to handle
backups, tuning, shrinking, etc separately?
Any suggestions/comments would be appreciated.What ever you do don't shrink the database. See here:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
How often you do backups are dependent on how much data you can afford to
loose. While this is for 2000 the principles still hold true.
http://www.microsoft.com/technet/pr...in/sqlops0.mspx
Andrew J. Kelly SQL MVP
"ML" <schooner@.accesswave.ca> wrote in message
news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
> to make sure we cover off all the bases in setting up our maintenance
> plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a
> single daily plan sufficient or should we be setting up multiple plans to
> handle backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
>
>|||On Aug 6, 1:13 pm, "ML" <schoo...@.accesswave.ca> wrote:
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
to
> make sure we cover off all the bases in setting up our maintenance plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a singl
e
> daily plan sufficient or should we be setting up multiple plans to handle
> backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
There is this: http://www.microsoft.com/technet/pr...br />
ps4.mspx|||"ML" <schooner@.accesswave.ca> wrote in message
news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
> to make sure we cover off all the bases in setting up our maintenance
> plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a
> single daily plan sufficient or should we be setting up multiple plans to
> handle backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
>
Thank you for the comment so far. I think we will start off with daily full
backups and transaction log backups every 15 mins.
For the database integrity check, is it best to run this before or after a
full backup?
In terms of the other maintenance tasks (rebuild indexes, update statistics,
etc) how often should these typically be run?|||As you probably realize, there are not simple "one size fits all" answers to
these question. Reading
up on the subject is what I recommend:
> For the database integrity check, is it best to run this before or after a full ba
ckup?
http://blogs.msdn.com/sqlserverstor.../23/675963.aspx
And other articles on that blog.
> In terms of the other maintenance tasks (rebuild indexes, update statistic
s, etc) how often should
> these typically be run?
http://www.microsoft.com/technet/pr...n/ss2kidbp.mspx
Above article hasn't been updated for 2005, but basic concepts still applies
.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"ML" <schooner@.accesswave.ca> wrote in message news:OabaWpN2HHA.1124@.TK2MSFTNGP06.phx.gbl...
> "ML" <schooner@.accesswave.ca> wrote in message news:%23abfUZG2HHA.728@.TK2M
SFTNGP05.phx.gbl...
> Thank you for the comment so far. I think we will start off with daily fu
ll backups and
> transaction log backups every 15 mins.
> For the database integrity check, is it best to run this before or after a
full backup?
> In terms of the other maintenance tasks (rebuild indexes, update statistic
s, etc) how often should
> these typically be run?
>
setting up proper maintenance plans with SQL 2005 (Workgroup)?
We have a new 2005 database that we are preparing for production and want to
make sure we cover off all the bases in setting up our maintenance plan.
This will be for an online reservation system that will process approx
300-600 transactions per day. The system needs to be live 24/7/365 or as
near to this as possible.
The initial database is expected to be around 600MB is size with approx 40
tables and grow from there with new transactions.
What we be a good plan for such a system for a starting point? Is a single
daily plan sufficient or should we be setting up multiple plans to handle
backups, tuning, shrinking, etc separately?
Any suggestions/comments would be appreciated.What ever you do don't shrink the database. See here:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
How often you do backups are dependent on how much data you can afford to
loose. While this is for 2000 the principles still hold true.
http://www.microsoft.com/technet/pr...in/sqlops0.mspx
Andrew J. Kelly SQL MVP
"ML" <schooner@.accesswave.ca> wrote in message
news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
> to make sure we cover off all the bases in setting up our maintenance
> plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a
> single daily plan sufficient or should we be setting up multiple plans to
> handle backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
>
>|||On Aug 6, 1:13 pm, "ML" <schoo...@.accesswave.ca> wrote:
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
to
> make sure we cover off all the bases in setting up our maintenance plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a singl
e
> daily plan sufficient or should we be setting up multiple plans to handle
> backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
There is this: http://www.microsoft.com/technet/pr...br />
ps4.mspx|||"ML" <schooner@.accesswave.ca> wrote in message
news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
> to make sure we cover off all the bases in setting up our maintenance
> plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a
> single daily plan sufficient or should we be setting up multiple plans to
> handle backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
>
Thank you for the comment so far. I think we will start off with daily full
backups and transaction log backups every 15 mins.
For the database integrity check, is it best to run this before or after a
full backup?
In terms of the other maintenance tasks (rebuild indexes, update statistics,
etc) how often should these typically be run?|||As you probably realize, there are not simple "one size fits all" answers to
these question. Reading
up on the subject is what I recommend:
> For the database integrity check, is it best to run this before or after a full ba
ckup?
http://blogs.msdn.com/sqlserverstor.../23/675963.aspx
And other articles on that blog.
> In terms of the other maintenance tasks (rebuild indexes, update statistic
s, etc) how often should
> these typically be run?
http://www.microsoft.com/technet/pr...n/ss2kidbp.mspx
Above article hasn't been updated for 2005, but basic concepts still applies
.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"ML" <schooner@.accesswave.ca> wrote in message news:OabaWpN2HHA.1124@.TK2MSFTNGP06.phx.gbl...
> "ML" <schooner@.accesswave.ca> wrote in message news:%23abfUZG2HHA.728@.TK2M
SFTNGP05.phx.gbl...
> Thank you for the comment so far. I think we will start off with daily fu
ll backups and
> transaction log backups every 15 mins.
> For the database integrity check, is it best to run this before or after a
full backup?
> In terms of the other maintenance tasks (rebuild indexes, update statistic
s, etc) how often should
> these typically be run?
>
Saturday, February 11, 2012
2005 beta Backup problems
Hi there,
I've created a maintenance plan in SQL2005 bet 2 (not default instance)
scheduled to run everyday but it never runs, I've all the services running.
When I choose to execute in the moment it says it had success after 5 seconds
but nothing happens really.
Is this a limitation of the beta release? Or am I doing something wrong?
I've another instance instaled in the same server (but with sql2000
version-default instance) and the maintenance plans work fine.
thanks in advance.
Nelson
Please re-post this on the beta newsgroups.
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Nelson Andr" <NelsonAndr@.discussions.microsoft.com> wrote in message
news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> Hi there,
> I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> scheduled to run everyday but it never runs, I've all the services
> running.
> When I choose to execute in the moment it says it had success after 5
> seconds
> but nothing happens really.
> Is this a limitation of the beta release? Or am I doing something wrong?
> I've another instance instaled in the same server (but with sql2000
> version-default instance) and the maintenance plans work fine.
> thanks in advance.
> Nelson
>
|||Where can I find it? I've searched the whole microsoft site and couldn't find
any reference to a sql2005 beta newsgroup
"Wayne Snyder" wrote:
> Please re-post this on the beta newsgroups.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
>
>
|||http://communities.microsoft.com/new...=sqlserver2005
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nelson André" wrote:
[vbcol=seagreen]
> Where can I find it? I've searched the whole microsoft site and couldn't find
> any reference to a sql2005 beta newsgroup
> "Wayne Snyder" wrote:
I've created a maintenance plan in SQL2005 bet 2 (not default instance)
scheduled to run everyday but it never runs, I've all the services running.
When I choose to execute in the moment it says it had success after 5 seconds
but nothing happens really.
Is this a limitation of the beta release? Or am I doing something wrong?
I've another instance instaled in the same server (but with sql2000
version-default instance) and the maintenance plans work fine.
thanks in advance.
Nelson
Please re-post this on the beta newsgroups.
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Nelson Andr" <NelsonAndr@.discussions.microsoft.com> wrote in message
news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> Hi there,
> I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> scheduled to run everyday but it never runs, I've all the services
> running.
> When I choose to execute in the moment it says it had success after 5
> seconds
> but nothing happens really.
> Is this a limitation of the beta release? Or am I doing something wrong?
> I've another instance instaled in the same server (but with sql2000
> version-default instance) and the maintenance plans work fine.
> thanks in advance.
> Nelson
>
|||Where can I find it? I've searched the whole microsoft site and couldn't find
any reference to a sql2005 beta newsgroup
"Wayne Snyder" wrote:
> Please re-post this on the beta newsgroups.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
>
>
|||http://communities.microsoft.com/new...=sqlserver2005
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nelson André" wrote:
[vbcol=seagreen]
> Where can I find it? I've searched the whole microsoft site and couldn't find
> any reference to a sql2005 beta newsgroup
> "Wayne Snyder" wrote:
2005 beta Backup problems
Hi there,
I've created a maintenance plan in SQL2005 bet 2 (not default instance)
scheduled to run everyday but it never runs, I've all the services running.
When I choose to execute in the moment it says it had success after 5 seconds
but nothing happens really.
Is this a limitation of the beta release? Or am I doing something wrong?
I've another instance instaled in the same server (but with sql2000
version-default instance) and the maintenance plans work fine.
thanks in advance.
NelsonPlease re-post this on the beta newsgroups.
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> Hi there,
> I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> scheduled to run everyday but it never runs, I've all the services
> running.
> When I choose to execute in the moment it says it had success after 5
> seconds
> but nothing happens really.
> Is this a limitation of the beta release? Or am I doing something wrong?
> I've another instance instaled in the same server (but with sql2000
> version-default instance) and the maintenance plans work fine.
> thanks in advance.
> Nelson
>|||Where can I find it? I've searched the whole microsoft site and couldn't find
any reference to a sql2005 beta newsgroup
"Wayne Snyder" wrote:
> Please re-post this on the beta newsgroups.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> > Hi there,
> > I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> > scheduled to run everyday but it never runs, I've all the services
> > running.
> > When I choose to execute in the moment it says it had success after 5
> > seconds
> > but nothing happens really.
> > Is this a limitation of the beta release? Or am I doing something wrong?
> > I've another instance instaled in the same server (but with sql2000
> > version-default instance) and the maintenance plans work fine.
> > thanks in advance.
> > Nelson
> >
>
>|||http://communities.microsoft.com/newsgroups/default.asp?icp=sqlserver2005
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nelson André" wrote:
> Where can I find it? I've searched the whole microsoft site and couldn't find
> any reference to a sql2005 beta newsgroup
> "Wayne Snyder" wrote:
> > Please re-post this on the beta newsgroups.
> >
> > --
> > Wayne Snyder MCDBA, SQL Server MVP
> > Mariner, Charlotte, NC
> > (Please respond only to the newsgroup.)
> >
> > I support the Professional Association for SQL Server ( PASS) and it's
> > community of SQL Professionals.
> > "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> > news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> > > Hi there,
> > > I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> > > scheduled to run everyday but it never runs, I've all the services
> > > running.
> > > When I choose to execute in the moment it says it had success after 5
> > > seconds
> > > but nothing happens really.
> > > Is this a limitation of the beta release? Or am I doing something wrong?
> > > I've another instance instaled in the same server (but with sql2000
> > > version-default instance) and the maintenance plans work fine.
> > > thanks in advance.
> > > Nelson
> > >
> >
> >
> >
I've created a maintenance plan in SQL2005 bet 2 (not default instance)
scheduled to run everyday but it never runs, I've all the services running.
When I choose to execute in the moment it says it had success after 5 seconds
but nothing happens really.
Is this a limitation of the beta release? Or am I doing something wrong?
I've another instance instaled in the same server (but with sql2000
version-default instance) and the maintenance plans work fine.
thanks in advance.
NelsonPlease re-post this on the beta newsgroups.
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> Hi there,
> I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> scheduled to run everyday but it never runs, I've all the services
> running.
> When I choose to execute in the moment it says it had success after 5
> seconds
> but nothing happens really.
> Is this a limitation of the beta release? Or am I doing something wrong?
> I've another instance instaled in the same server (but with sql2000
> version-default instance) and the maintenance plans work fine.
> thanks in advance.
> Nelson
>|||Where can I find it? I've searched the whole microsoft site and couldn't find
any reference to a sql2005 beta newsgroup
"Wayne Snyder" wrote:
> Please re-post this on the beta newsgroups.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> > Hi there,
> > I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> > scheduled to run everyday but it never runs, I've all the services
> > running.
> > When I choose to execute in the moment it says it had success after 5
> > seconds
> > but nothing happens really.
> > Is this a limitation of the beta release? Or am I doing something wrong?
> > I've another instance instaled in the same server (but with sql2000
> > version-default instance) and the maintenance plans work fine.
> > thanks in advance.
> > Nelson
> >
>
>|||http://communities.microsoft.com/newsgroups/default.asp?icp=sqlserver2005
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nelson André" wrote:
> Where can I find it? I've searched the whole microsoft site and couldn't find
> any reference to a sql2005 beta newsgroup
> "Wayne Snyder" wrote:
> > Please re-post this on the beta newsgroups.
> >
> > --
> > Wayne Snyder MCDBA, SQL Server MVP
> > Mariner, Charlotte, NC
> > (Please respond only to the newsgroup.)
> >
> > I support the Professional Association for SQL Server ( PASS) and it's
> > community of SQL Professionals.
> > "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> > news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> > > Hi there,
> > > I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> > > scheduled to run everyday but it never runs, I've all the services
> > > running.
> > > When I choose to execute in the moment it says it had success after 5
> > > seconds
> > > but nothing happens really.
> > > Is this a limitation of the beta release? Or am I doing something wrong?
> > > I've another instance instaled in the same server (but with sql2000
> > > version-default instance) and the maintenance plans work fine.
> > > thanks in advance.
> > > Nelson
> > >
> >
> >
> >
2005 beta Backup problems
Hi there,
I've created a maintenance plan in SQL2005 bet 2 (not default instance)
scheduled to run everyday but it never runs, I've all the services running.
When I choose to execute in the moment it says it had success after 5 second
s
but nothing happens really.
Is this a limitation of the beta release? Or am I doing something wrong?
I've another instance instaled in the same server (but with sql2000
version-default instance) and the maintenance plans work fine.
thanks in advance.
NelsonPlease re-post this on the beta newsgroups.
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Nelson Andr" <NelsonAndr@.discussions.microsoft.com> wrote in message
news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> Hi there,
> I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> scheduled to run everyday but it never runs, I've all the services
> running.
> When I choose to execute in the moment it says it had success after 5
> seconds
> but nothing happens really.
> Is this a limitation of the beta release? Or am I doing something wrong?
> I've another instance instaled in the same server (but with sql2000
> version-default instance) and the maintenance plans work fine.
> thanks in advance.
> Nelson
>|||Where can I find it? I've searched the whole microsoft site and couldn't fin
d
any reference to a sql2005 beta newsgroup
"Wayne Snyder" wrote:
> Please re-post this on the beta newsgroups.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
>
>|||http://communities.microsoft.com/ne...p=sqlserver2005
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nelson André" wrote:
[vbcol=seagreen]
> Where can I find it? I've searched the whole microsoft site and couldn't f
ind
> any reference to a sql2005 beta newsgroup
> "Wayne Snyder" wrote:
>
I've created a maintenance plan in SQL2005 bet 2 (not default instance)
scheduled to run everyday but it never runs, I've all the services running.
When I choose to execute in the moment it says it had success after 5 second
s
but nothing happens really.
Is this a limitation of the beta release? Or am I doing something wrong?
I've another instance instaled in the same server (but with sql2000
version-default instance) and the maintenance plans work fine.
thanks in advance.
NelsonPlease re-post this on the beta newsgroups.
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Nelson Andr" <NelsonAndr@.discussions.microsoft.com> wrote in message
news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> Hi there,
> I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> scheduled to run everyday but it never runs, I've all the services
> running.
> When I choose to execute in the moment it says it had success after 5
> seconds
> but nothing happens really.
> Is this a limitation of the beta release? Or am I doing something wrong?
> I've another instance instaled in the same server (but with sql2000
> version-default instance) and the maintenance plans work fine.
> thanks in advance.
> Nelson
>|||Where can I find it? I've searched the whole microsoft site and couldn't fin
d
any reference to a sql2005 beta newsgroup
"Wayne Snyder" wrote:
> Please re-post this on the beta newsgroups.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
>
>|||http://communities.microsoft.com/ne...p=sqlserver2005
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nelson André" wrote:
[vbcol=seagreen]
> Where can I find it? I've searched the whole microsoft site and couldn't f
ind
> any reference to a sql2005 beta newsgroup
> "Wayne Snyder" wrote:
>
Thursday, February 9, 2012
2005 backup
I am going through the maintenance plan to create a schedules backup.
Everything seems fine until the final stages of the backup schedule setup when the system gives the following error.
create failed for jobStep SubPlan.
p.s I am not sure how to attached a snapshot of the error message.
Thanks
You need to install SQL Server Integration Services. Run setup and then install .2005 - Remove Old Backups
Is there a way to remove backups older than a certain number of days with a
generic 2005 maintenance plan. I looked through the basic tasks available
and I did not see this option. There is an option to remove old history
(i.e. logs) but I did not see a task to remove old backups.
This functionality was available with the SQL Server 2000 maintenance plans.
Thanks!You didn't look hard enough<g>. There is a task for exactly that, deleting
old backup files. It is called the "Maintenance Cleanup Task".
Andrew J. Kelly SQL MVP
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:OcWhvIbBGHA.736@.TK2MSFTNGP10.phx.gbl...
> Is there a way to remove backups older than a certain number of days with
> a generic 2005 maintenance plan. I looked through the basic tasks
> available and I did not see this option. There is an option to remove old
> history (i.e. logs) but I did not see a task to remove old backups.
> This functionality was available with the SQL Server 2000 maintenance
> plans.
> Thanks!
>|||Hi Cgal,
As Andrew has mentioned, there does exists the Maintenance Task for
cleaning up backup files in the SQL 2005's Maintenance Plan items... (also
available in sql server 2000 through the maintenance plan creation
wizard...).
Create a new maintenance plan in sql2005 management studio, and in the
"Maintenance Plan Task" toolbox, choose the "Maintenance cleanup task",
there has setting for removing backup files of certain age of time....
#Maintenance Cleanup Task (Maintenance Plan)
http://msdn2.microsoft.com/en-us/library/ms177182.aspx
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
| From: "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com>
| References: <OcWhvIbBGHA.736@.TK2MSFTNGP10.phx.gbl>
| Subject: Re: 2005 - Remove Old Backups
| Date: Tue, 20 Dec 2005 18:07:16 -0500
| Lines: 22
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
| X-RFC2646: Format=Flowed; Response
| Message-ID: <e2cIhobBGHA.3156@.TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: c-24-128-28-245.hsd1.nh.comcast.net 24.128.28.245
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:414948
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| You didn't look hard enough<g>. There is a task for exactly that,
deleting
| old backup files. It is called the "Maintenance Cleanup Task".
|
| --
| Andrew J. Kelly SQL MVP
|
|
| "Cgal" <cgallelli@.newsgroups.nospam> wrote in message
| news:OcWhvIbBGHA.736@.TK2MSFTNGP10.phx.gbl...
| > Is there a way to remove backups older than a certain number of days
with
| > a generic 2005 maintenance plan. I looked through the basic tasks
| > available and I did not see this option. There is an option to remove
old
| > history (i.e. logs) but I did not see a task to remove old backups.
| >
| > This functionality was available with the SQL Server 2000 maintenance
| > plans.
| >
| > Thanks!
| >
| >
|
|
|
generic 2005 maintenance plan. I looked through the basic tasks available
and I did not see this option. There is an option to remove old history
(i.e. logs) but I did not see a task to remove old backups.
This functionality was available with the SQL Server 2000 maintenance plans.
Thanks!You didn't look hard enough<g>. There is a task for exactly that, deleting
old backup files. It is called the "Maintenance Cleanup Task".
Andrew J. Kelly SQL MVP
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:OcWhvIbBGHA.736@.TK2MSFTNGP10.phx.gbl...
> Is there a way to remove backups older than a certain number of days with
> a generic 2005 maintenance plan. I looked through the basic tasks
> available and I did not see this option. There is an option to remove old
> history (i.e. logs) but I did not see a task to remove old backups.
> This functionality was available with the SQL Server 2000 maintenance
> plans.
> Thanks!
>|||Hi Cgal,
As Andrew has mentioned, there does exists the Maintenance Task for
cleaning up backup files in the SQL 2005's Maintenance Plan items... (also
available in sql server 2000 through the maintenance plan creation
wizard...).
Create a new maintenance plan in sql2005 management studio, and in the
"Maintenance Plan Task" toolbox, choose the "Maintenance cleanup task",
there has setting for removing backup files of certain age of time....
#Maintenance Cleanup Task (Maintenance Plan)
http://msdn2.microsoft.com/en-us/library/ms177182.aspx
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
| From: "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com>
| References: <OcWhvIbBGHA.736@.TK2MSFTNGP10.phx.gbl>
| Subject: Re: 2005 - Remove Old Backups
| Date: Tue, 20 Dec 2005 18:07:16 -0500
| Lines: 22
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
| X-RFC2646: Format=Flowed; Response
| Message-ID: <e2cIhobBGHA.3156@.TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: c-24-128-28-245.hsd1.nh.comcast.net 24.128.28.245
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:414948
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| You didn't look hard enough<g>. There is a task for exactly that,
deleting
| old backup files. It is called the "Maintenance Cleanup Task".
|
| --
| Andrew J. Kelly SQL MVP
|
|
| "Cgal" <cgallelli@.newsgroups.nospam> wrote in message
| news:OcWhvIbBGHA.736@.TK2MSFTNGP10.phx.gbl...
| > Is there a way to remove backups older than a certain number of days
with
| > a generic 2005 maintenance plan. I looked through the basic tasks
| > available and I did not see this option. There is an option to remove
old
| > history (i.e. logs) but I did not see a task to remove old backups.
| >
| > This functionality was available with the SQL Server 2000 maintenance
| > plans.
| >
| > Thanks!
| >
| >
|
|
|
2005 - Remove Old Backups
Is there a way to remove backups older than a certain number of days with a
generic 2005 maintenance plan. I looked through the basic tasks available
and I did not see this option. There is an option to remove old history
(i.e. logs) but I did not see a task to remove old backups.
This functionality was available with the SQL Server 2000 maintenance plans.
Thanks!
You didn't look hard enough<g>. There is a task for exactly that, deleting
old backup files. It is called the "Maintenance Cleanup Task".
Andrew J. Kelly SQL MVP
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:OcWhvIbBGHA.736@.TK2MSFTNGP10.phx.gbl...
> Is there a way to remove backups older than a certain number of days with
> a generic 2005 maintenance plan. I looked through the basic tasks
> available and I did not see this option. There is an option to remove old
> history (i.e. logs) but I did not see a task to remove old backups.
> This functionality was available with the SQL Server 2000 maintenance
> plans.
> Thanks!
>
|||Hi Cgal,
As Andrew has mentioned, there does exists the Maintenance Task for
cleaning up backup files in the SQL 2005's Maintenance Plan items... (also
available in sql server 2000 through the maintenance plan creation
wizard...).
Create a new maintenance plan in sql2005 management studio, and in the
"Maintenance Plan Task" toolbox, choose the "Maintenance cleanup task",
there has setting for removing backup files of certain age of time....
#Maintenance Cleanup Task (Maintenance Plan)
http://msdn2.microsoft.com/en-us/library/ms177182.aspx
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
| From: "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com>
| References: <OcWhvIbBGHA.736@.TK2MSFTNGP10.phx.gbl>
| Subject: Re: 2005 - Remove Old Backups
| Date: Tue, 20 Dec 2005 18:07:16 -0500
| Lines: 22
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
| X-RFC2646: Format=Flowed; Response
| Message-ID: <e2cIhobBGHA.3156@.TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: c-24-128-28-245.hsd1.nh.comcast.net 24.128.28.245
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGP12.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:414948
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| You didn't look hard enough<g>. There is a task for exactly that,
deleting
| old backup files. It is called the "Maintenance Cleanup Task".
|
| --
| Andrew J. Kelly SQL MVP
|
|
| "Cgal" <cgallelli@.newsgroups.nospam> wrote in message
| news:OcWhvIbBGHA.736@.TK2MSFTNGP10.phx.gbl...
| > Is there a way to remove backups older than a certain number of days
with
| > a generic 2005 maintenance plan. I looked through the basic tasks
| > available and I did not see this option. There is an option to remove
old
| > history (i.e. logs) but I did not see a task to remove old backups.
| >
| > This functionality was available with the SQL Server 2000 maintenance
| > plans.
| >
| > Thanks!
| >
| >
|
|
|
generic 2005 maintenance plan. I looked through the basic tasks available
and I did not see this option. There is an option to remove old history
(i.e. logs) but I did not see a task to remove old backups.
This functionality was available with the SQL Server 2000 maintenance plans.
Thanks!
You didn't look hard enough<g>. There is a task for exactly that, deleting
old backup files. It is called the "Maintenance Cleanup Task".
Andrew J. Kelly SQL MVP
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:OcWhvIbBGHA.736@.TK2MSFTNGP10.phx.gbl...
> Is there a way to remove backups older than a certain number of days with
> a generic 2005 maintenance plan. I looked through the basic tasks
> available and I did not see this option. There is an option to remove old
> history (i.e. logs) but I did not see a task to remove old backups.
> This functionality was available with the SQL Server 2000 maintenance
> plans.
> Thanks!
>
|||Hi Cgal,
As Andrew has mentioned, there does exists the Maintenance Task for
cleaning up backup files in the SQL 2005's Maintenance Plan items... (also
available in sql server 2000 through the maintenance plan creation
wizard...).
Create a new maintenance plan in sql2005 management studio, and in the
"Maintenance Plan Task" toolbox, choose the "Maintenance cleanup task",
there has setting for removing backup files of certain age of time....
#Maintenance Cleanup Task (Maintenance Plan)
http://msdn2.microsoft.com/en-us/library/ms177182.aspx
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
| From: "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com>
| References: <OcWhvIbBGHA.736@.TK2MSFTNGP10.phx.gbl>
| Subject: Re: 2005 - Remove Old Backups
| Date: Tue, 20 Dec 2005 18:07:16 -0500
| Lines: 22
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
| X-RFC2646: Format=Flowed; Response
| Message-ID: <e2cIhobBGHA.3156@.TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: c-24-128-28-245.hsd1.nh.comcast.net 24.128.28.245
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGP12.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:414948
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| You didn't look hard enough<g>. There is a task for exactly that,
deleting
| old backup files. It is called the "Maintenance Cleanup Task".
|
| --
| Andrew J. Kelly SQL MVP
|
|
| "Cgal" <cgallelli@.newsgroups.nospam> wrote in message
| news:OcWhvIbBGHA.736@.TK2MSFTNGP10.phx.gbl...
| > Is there a way to remove backups older than a certain number of days
with
| > a generic 2005 maintenance plan. I looked through the basic tasks
| > available and I did not see this option. There is an option to remove
old
| > history (i.e. logs) but I did not see a task to remove old backups.
| >
| > This functionality was available with the SQL Server 2000 maintenance
| > plans.
| >
| > Thanks!
| >
| >
|
|
|
2005 - Remove Old Backups
Is there a way to remove backups older than a certain number of days with a
generic 2005 maintenance plan. I looked through the basic tasks available
and I did not see this option. There is an option to remove old history
(i.e. logs) but I did not see a task to remove old backups.
This functionality was available with the SQL Server 2000 maintenance plans.
Thanks!You didn't look hard enough<g>. There is a task for exactly that, deleting
old backup files. It is called the "Maintenance Cleanup Task".
--
Andrew J. Kelly SQL MVP
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:OcWhvIbBGHA.736@.TK2MSFTNGP10.phx.gbl...
> Is there a way to remove backups older than a certain number of days with
> a generic 2005 maintenance plan. I looked through the basic tasks
> available and I did not see this option. There is an option to remove old
> history (i.e. logs) but I did not see a task to remove old backups.
> This functionality was available with the SQL Server 2000 maintenance
> plans.
> Thanks!
>|||Hi Cgal,
As Andrew has mentioned, there does exists the Maintenance Task for
cleaning up backup files in the SQL 2005's Maintenance Plan items... (also
available in sql server 2000 through the maintenance plan creation
wizard...).
Create a new maintenance plan in sql2005 management studio, and in the
"Maintenance Plan Task" toolbox, choose the "Maintenance cleanup task",
there has setting for removing backup files of certain age of time....
#Maintenance Cleanup Task (Maintenance Plan)
http://msdn2.microsoft.com/en-us/library/ms177182.aspx
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
| From: "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com>
| References: <OcWhvIbBGHA.736@.TK2MSFTNGP10.phx.gbl>
| Subject: Re: 2005 - Remove Old Backups
| Date: Tue, 20 Dec 2005 18:07:16 -0500
| Lines: 22
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
| X-RFC2646: Format=Flowed; Response
| Message-ID: <e2cIhobBGHA.3156@.TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: c-24-128-28-245.hsd1.nh.comcast.net 24.128.28.245
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:414948
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| You didn't look hard enough<g>. There is a task for exactly that,
deleting
| old backup files. It is called the "Maintenance Cleanup Task".
|
| --
| Andrew J. Kelly SQL MVP
|
|
| "Cgal" <cgallelli@.newsgroups.nospam> wrote in message
| news:OcWhvIbBGHA.736@.TK2MSFTNGP10.phx.gbl...
| > Is there a way to remove backups older than a certain number of days
with
| > a generic 2005 maintenance plan. I looked through the basic tasks
| > available and I did not see this option. There is an option to remove
old
| > history (i.e. logs) but I did not see a task to remove old backups.
| >
| > This functionality was available with the SQL Server 2000 maintenance
| > plans.
| >
| > Thanks!
| >
| >
|
|
|
generic 2005 maintenance plan. I looked through the basic tasks available
and I did not see this option. There is an option to remove old history
(i.e. logs) but I did not see a task to remove old backups.
This functionality was available with the SQL Server 2000 maintenance plans.
Thanks!You didn't look hard enough<g>. There is a task for exactly that, deleting
old backup files. It is called the "Maintenance Cleanup Task".
--
Andrew J. Kelly SQL MVP
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:OcWhvIbBGHA.736@.TK2MSFTNGP10.phx.gbl...
> Is there a way to remove backups older than a certain number of days with
> a generic 2005 maintenance plan. I looked through the basic tasks
> available and I did not see this option. There is an option to remove old
> history (i.e. logs) but I did not see a task to remove old backups.
> This functionality was available with the SQL Server 2000 maintenance
> plans.
> Thanks!
>|||Hi Cgal,
As Andrew has mentioned, there does exists the Maintenance Task for
cleaning up backup files in the SQL 2005's Maintenance Plan items... (also
available in sql server 2000 through the maintenance plan creation
wizard...).
Create a new maintenance plan in sql2005 management studio, and in the
"Maintenance Plan Task" toolbox, choose the "Maintenance cleanup task",
there has setting for removing backup files of certain age of time....
#Maintenance Cleanup Task (Maintenance Plan)
http://msdn2.microsoft.com/en-us/library/ms177182.aspx
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
| From: "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com>
| References: <OcWhvIbBGHA.736@.TK2MSFTNGP10.phx.gbl>
| Subject: Re: 2005 - Remove Old Backups
| Date: Tue, 20 Dec 2005 18:07:16 -0500
| Lines: 22
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
| X-RFC2646: Format=Flowed; Response
| Message-ID: <e2cIhobBGHA.3156@.TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: c-24-128-28-245.hsd1.nh.comcast.net 24.128.28.245
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:414948
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| You didn't look hard enough<g>. There is a task for exactly that,
deleting
| old backup files. It is called the "Maintenance Cleanup Task".
|
| --
| Andrew J. Kelly SQL MVP
|
|
| "Cgal" <cgallelli@.newsgroups.nospam> wrote in message
| news:OcWhvIbBGHA.736@.TK2MSFTNGP10.phx.gbl...
| > Is there a way to remove backups older than a certain number of days
with
| > a generic 2005 maintenance plan. I looked through the basic tasks
| > available and I did not see this option. There is an option to remove
old
| > history (i.e. logs) but I did not see a task to remove old backups.
| >
| > This functionality was available with the SQL Server 2000 maintenance
| > plans.
| >
| > Thanks!
| >
| >
|
|
|
Subscribe to:
Posts (Atom)