Transaction Log Backup

Hi Sabina,

My theory is that there are likely other issues in the msdb database than just this one column configured incorrectly. Here are two options I can think of:

1.       Carefully fix the default value property of that one column so that it is set properly. Then, try your maintenance plan creation again.

2.       Rebuild the msdb database completely. There are instructions for doing that here: http://msdn.microsoft.com/en-us/library/dd207003(v=sql.105).aspx. There is a section in that link called, Creating a New msdb Database. Note the caution they list about what is lost when doing that. No data, just things like jobs, alerts, etc.  You could script many of those items through SSMS before rebuilding the Msdb database.

So, #1 would fix this one problem and may be worth trying first, although there is a good chance that is not the only issue. #2 would ensure msdb is in the appropriate state, but you’d have to recreate the objects Microsoft lists in the link above.

There may be other ideas that I’m not thinking of, but that’s what I’d probably be considering myself if I ran into this issue. I hope this helps.

Thanks,

David

_______________________________________________________
David Frederick
Database Applications Analyst
Segerstrom Center for the Arts
600 Town Center Drive, Costa Mesa, CA 92626
T (714) 556-2122 x 4067 E DFrederick@SCFTA.org

David, you are a life saver !!!   We are running the same version of SQL server.  And  the default value for the msx_plan was not set to 0.  What kind of repair  you 're referring to ?

Thank you so much,

Sabina (619.615.3904)

Privileged And Confidential Communication. This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC §§ 2510-2521), (b) may contain confidential and/or legally privileged information, and (c) are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Privileged And Confidential Communication. This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC §§ 2510-2521), (b) may contain confidential and/or legally privileged information, and (c) are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Hi Sabina,

My theory is that there are likely other issues in the msdb database than just this one column configured incorrectly. Here are two options I can think of:

1.       Carefully fix the default value property of that one column so that it is set properly. Then, try your maintenance plan creation again.

2.       Rebuild the msdb database completely. There are instructions for doing that here: http://msdn.microsoft.com/en-us/library/dd207003(v=sql.105).aspx. There is a section in that link called, Creating a New msdb Database. Note the caution they list about what is lost when doing that. No data, just things like jobs, alerts, etc.  You could script many of those items through SSMS before rebuilding the Msdb database.

So, #1 would fix this one problem and may be worth trying first, although there is a good chance that is not the only issue. #2 would ensure msdb is in the appropriate state, but you’d have to recreate the objects Microsoft lists in the link above.

There may be other ideas that I’m not thinking of, but that’s what I’d probably be considering myself if I ran into this issue. I hope this helps.

Thanks,

David

_______________________________________________________
David Frederick
Database Applications Analyst
Segerstrom Center for the Arts
600 Town Center Drive, Costa Mesa, CA 92626
T (714) 556-2122 x 4067 E DFrederick@SCFTA.org

David, you are a life saver !!!   We are running the same version of SQL server.  And  the default value for the msx_plan was not set to 0.  What kind of repair  you 're referring to ?

Thank you so much,

Sabina (619.615.3904)

Privileged And Confidential Communication. This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC §§ 2510-2521), (b) may contain confidential and/or legally privileged information, and (c) are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Privileged And Confidential Communication. This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC §§ 2510-2521), (b) may contain confidential and/or legally privileged information, and (c) are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!