September 15, 2008 at 10:16 am
I just wanted to verify that this is working how I think it is.
It appears that if I create a maintenance plan and say Backup Type: FULL (for the Back Up Database Task), Database(s): ALL DATABASES and then go to View TSQL it shows me all the databases currently on the server.
So I save the plan.
Then I restore a database to the server that was NOT on the server when I created the maint plan.
I re-open the maint plan which still says "All Databases" and click "View T-SQL" and I do NOT see the newly restored database.
To get the newly restored database to be part of the plan I have to click off All Databases (selected for example) then click back on All Databases.
Then when I view the T-SQL it lists the newly restored database.
I assume this is a normal behavior and not some fluke?
I ALSO assume that if I have maint plans that say "re-org ALL indexes on ALL databases" that I'd have to do the same procedure for all of those as well to get them to include a newly added database?
Thanks!
September 15, 2008 at 10:20 am
As a test can you run the backup job to see if it picks up the new database without having to "tweak" the maintenance plan? Very curious as what you are describing would defeat the purpose of the option and I don't think I have seen that behavior before. So, I am wondering if what you are seeing is "cached" somehow....
Thanks in advance for any more information you find.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
September 15, 2008 at 10:56 am
Changes on Maintenance plan are not automatically reflected on Jobs so... it wouldn't surprise me.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.September 15, 2008 at 11:07 am
DavidB (9/15/2008)
As a test can you run the backup job to see if it picks up the new database without having to "tweak" the maintenance plan? Very curious as what you are describing would defeat the purpose of the option and I don't think I have seen that behavior before. So, I am wondering if what you are seeing is "cached" somehow....Thanks in advance for any more information you find.
I agree with what you are saying and that would be the smart course of action.
Sadly I can't do that at the moment as I only noticed it as I was moving the database to production and wanted to double check the maint plans to ensure they included the new database.
As for dev I can't mess with that one at the moment until we finish this roll out.
Next week I could play with it more, but at the moment I don't have any additional servers to mess with it on 🙁
Can someone here perhaps give it a shot on one of their test servers?
Also incase it matters my SQL Server version is:
Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply