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 |
|
AndreasMeyer
Starting Member
9 Posts |
 Posted - 2008-08-05 : 09:09:31
|
| Hello,I just migrated to SQL Server 2005.Now I have to re-configurate the Backups.Under Management, Maintenance Plans I created a MaintenancePlan_FullBackup thru the wizard and I just set the mark for full Backups.Further in "Databases" I chose "Specific Databases", "These databases" and checked the boxes for 3 databases on the server.As schedule I set Mo thru Fri at 18:40 p.m.First question:Under SQL Server Agent, Jobs a MaintenancePlan_FullBackup.Subplan_1 is created. Why that? For being able to add many Subplans to the same Maintenance Plan?I could RightClick the Subplan and choose "Start Job at step.." If I do that it immediately starts the job most likely since there is only one step.I rightclick the Subplan and choose History and there it tells me Success and run duration=4 seconds (or less since I started a few times already) and also:DTExec: The package execution returned DTSER_SUCCESS (0)... Elapsed 1.39 seconds. The package excecuted successfully. The step succeeded.However, no database is backed up.This is much to fast since one db is 17GB.At least in SQL-Server2000 I could execute jobs thru rightclicking them at any time. Is that different in SQL Server 2005 in that the package will only excecute at the scheduled time? My feeling says it should be the same and execute even though the schedule is different.Any idea of what is wrong?I could also rightclick the maintenance plan itself under Management, Maintenance Plans and choose execute. Looking up the history here shows a green checkmark with date and time but in the field duration a "00:00:00"; probably it only calls the subplan which is found really quick.Where can I read a more detailed logfile of what has been done?Can I set logging to verbose or some such?Reporting success while not backing anything up is an administrator's nightmare, really.Thanks for any advice.SincerelyAndreas |
|
|
AndreasMeyer
Starting Member
9 Posts |
Posted - 2008-08-05 : 09:43:11
|
| I rightclicked the MaintenancePlan and chose Modify.Then I rightclicked the object in the design window and chose Edit, clicked View T-SQL and copied the code up to the first database. I opened a query window on the database, copied in the code and it would create a backup!How come the package doesn't work within the maintenance plan as it should?Thank you for any hint.Andreas |
 |
|
|
AndreasMeyer
Starting Member
9 Posts |
Posted - 2008-08-05 : 11:34:28
|
| Hi,I threw the old MPlan away, created a new one which then worked.Only the heavens know why the other one ran with success without doing anything... |
|
|
|
cat_jesus
Aged Yak Warrior
547 Posts |
Posted - 2008-08-05 : 12:32:20
|
| I would recommend staying away from Maintenance plans. I am in the process of removing all maintenance plans and replacing them with Stored procedures. See http://weblogs.sqlteam.com/tarad/archive/2008/05/21/60606.aspx for an excellent backup SP written by Tara.Maintenance plans are such a pain.An infinite universe is the ultimate cartesian product. |
|
|
|
Ola Hallengren
Starting Member
33 Posts |
|
|
|
|
|
|
|
Mainten.PlanBak reports success without a backup?