Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
solart
Posting Yak Master
148 Posts |
 Posted - 2002-08-13 : 12:27:37
|
| I have several servers. Some of them run SQL 2K and some SQL 7. On all of them I use maintenance plans.My basic approach is to run full, differential, and log backups on a frequency appropriate for the database and its use. In general, to backup to disk. We use Arcserve to backup completed disk backups to tape, thus in practice actually keeping several full backup cycles.The jobs which run the maintenance plans are multiple step jobs. Some steps run when prior steps fail. Some steps run when prior steps succeed. Some steps kick of the execution of the next job. The maintenance plans are setup to delete obsolete backups, thus conserving disk space. Each backup is date/time stamped in its filename, which I find useful.I have had no problems over a several month time span, yet I see folks who preference is to not use maintenance plans.I would appreciate it if those whose preference is to not use maintenance plans would describe for me what they see as the negative aspects of using maintenance plans.I am concerned that maybe I am not considering all the facts and need to revise my approach.TIA solart |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2002-08-13 : 12:38:42
|
| Main problem is that they conceal what is happenning from the user.I have seen people creating maintenance plans and having no idea of what they are really doing and having problems thereby.I distrust anything with a gui (comes from the early days of the enterprise manager server crash ulility) and like to do everything via scripts. Then I have a record of what has been done (bad memory, working under influence of beer, not enough sleep, ...) - can do a compare against the next version to make sure I haven't changed anything accidentally and if it doesn't work can just change the bit necessary rather than starting from scratch.All the functions you have mentioned here you could do easily in sql.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy.Edited by - nr on 08/13/2002 12:40:16 |
 |
|
|
solart
Posting Yak Master
148 Posts |
Posted - 2002-08-13 : 12:55:55
|
| NR your point is well taken and considering your input, it seems that the use of scripts would allow the use of parameters which the maintenance plans do not provide access to (at least in a way maybe which is easily understood).I did fail to point out that when I create a maintenance plan, I never have it performing more than one function. Thereby I do know what the maintenance plan is doing (or suppose to be doing) |
|
|
|
Page47
Master Smack Fu Yak Hacker
2878 Posts |
Posted - 2002-08-13 : 13:01:45
|
quote:
I never have it performing more than one function.
I think part of nr's arguement is "How do you know?"Jay White{0} |
|
|
|
solart
Posting Yak Master
148 Posts |
Posted - 2002-08-13 : 15:32:10
|
| Thanks Jay. Between you and NR, I think the "light" has finally dawned.solart |
|
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
Posted - 2002-08-13 : 18:12:47
|
Also search MSKB for sqlmaint and you get 23 for SQL Server and 9 for SQl2000. Search google groups microsoft.public.sqlserver.* and you get 1150 hits. Says a lot  I prefer to know (or think I know  ) what's going on....HTHJasper Smith |
|
|
|
|
|
|
|
|
Maintenance Plans, What are disadvantages ?