| Author |
Topic |
|
lebedev
Posting Yak Master
126 Posts |
 Posted - 2010-01-11 : 12:03:40
|
| We have created a Maintenance Plan in SQL Server 2005 Management Studio. The plan performs periodic backups and has a schedule assigned to it. When we migrated the plan to a new server by storing it on the file system using Integration Services and reimporting on the new server. However, the schedule attached to the plan was lost and we had to recreate it manually, which is not ideal.I am looking for suggestions on how to implement a maintenance plan that can be automatically migrated to a new server. Should I use "maintenance plan", "job agents", "pure T-SQL", or some other features?Thanks.P.S. We are using SQL Server 2005 and 2008. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
lebedev
Posting Yak Master
126 Posts |
Posted - 2010-01-11 : 16:13:18
|
| Thanks, I was kind of leaning towards custom code as well. Let's assume we have a stored procedure which does the maintenance. How do you suggest we schedule it for execution? Should we create an agent job for it and schedule the job in T-SQL?Thanks. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
lebedev
Posting Yak Master
126 Posts |
Posted - 2010-01-11 : 17:23:27
|
| It's ok, you answered my question even without understanding it. The essence of the question was whether or not there are other SQL Server mechanisms besides SQL Agent jobs that can be used for scheduling. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
lebedev
Posting Yak Master
126 Posts |
Posted - 2010-01-11 : 17:31:10
|
| The question was about "other SQL Server mechanisms". I understand that you recommend SQL Agent jobs.Thanks, Tara. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
Implementation options for a maintenance plan