This is a discussion on Notification Services Updates within the SQL Server forums, part of the Microsoft SQL Server category; --> My 2007 NS skill is about zero and in lieue of having a full-time DBA, I"m trying to manage ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| My 2007 NS skill is about zero and in lieue of having a full-time DBA, I"m trying to manage a prod environment (on top of my other duties as Ops director). Anyway, evidently what my IT guy and dev person is telling me is that when we make an update to a service (say change it to send notifications every 5 minutes instead of 10), the process of reading in the XML file and doing the upgrade destroys all the history. This evidently is a problem since it means that some notifications that were sent out are possibly sent out again. Is this correct? Is there a way to avoid this? NS seems like a great idea, but in production seems it may be lacking. Or our knowledge? Help. -- Greg Moore SQL Server DBA Consulting Remote and Onsite available! Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html |