Ok, These are a few stupid questions, but I couldnt find the answer anywhere. I am really sorry.
How do you upgrade from a notification server 2000 to a notification server 2005? And how much work is it?
Is it possible to write a .Net 2.0 application which supports both notification server 2000 and 2005?
The reason I ask this question is that we want to develop an application for notification services. I looked at the product (in 2005) and it gives a lot of oppurtinities. The only problem the API's and documentation are not that clear (for me).
Thanks in advance,
Jeroen van Onzen
With regards to the upgrade you're best referred to the steps outlined in the SQL Server 2005 books online, you can find them here:
If they aren't available to you, using the upgrade advisor in SQL 2005 the steps look basically like this:
- Upgrade your database server to SQL 2005
- Use the NS tools to upgrade your application to NS 2005
- Update a small change to your notify function
- Build your custom components (if any) against .NET 2.0
Yes, you have to use the .NET 2.0 clients to go against Notification Services 2005.
With regards to the documentation for the features you're interested (in 2005) are there any specific sections that aren't clear to you? Please let us know.
If you're new to NS altogether may I recommend the following books:
BTW, if you are interested in NS 2005 either through a new deployment or through upgrading an existing application, please email me as: firstname.lastname@example.org and we can discuss options through which we can provide you assitance.
2005年7月26日 16:40Thanks for your quick response. I am reading the book of Microsoft SQL Server 2000 Notification Server right now. It's a good book which make several things more clear.
I have three points where the documentation was not clear for me.
1) When following the tutorial deliverd with Microsoft SQL Server 2005 (9.00.1187.0), I stuck at lesson 7 and 11.
At the moment I am entering lesson 7, there is no tag <!---- Place QuantumDuration here ---> . I guessed (maybe I am wrong), that there is a small order change with lesson 8.
At the moment I arrive at lesson 11, i get several SQL errors when executing the code. The event provider in the example is not "WeatherSPEventProvider" but "WeatherSPs".
When I execute the SQL, there are no SQL errors, and everything seems to work fine. The only problem I have at the moment is there is no notification.html in my notifcation folder. There are two notification messages in the event log (at an unrelated time): "The scheduler failed to schedule a quantum." and "At least one monitoring interval was skipped". Probably 5 minutes to google, but i want to read the book first for going further with the tutorial.
2) When you have a subscription if the stock price raises over $50,-, what do you get with the following scenario:
Stock Price starts with: 49,- : No Notification
It raises to 51,- : I will recieve Notification
It stays on 51,-, will i get every interval a message, or is it just one message?
It raises to 52,-, will i get a new message?
It drops to 49,-, so i will receive no more notifications
It raises back to 51,-, will i get a new notification?
3) When is it necessary to create different "instances" of The Notification Service?
Jeroen van Onzen
P.S. Just to be sure: Is it possible to build a notification server where the user specifies a completely unknown query (with a single result cell), which should not drop or raise above a specified value?
In regards to the problems you experienced with the tutorial, there were some errors that, unfortunately, were caught too late to correct for the June CTP. These are described fully in the readme.txt file that comes with the product. You'll find instructions in the readme.txt file on how to get around these errors.
In answer to your question #2, you can build state-maintenance into your application to prevent over-notification like you've described. You use chronicle tables to do this. You mention that you have my SQL Server 2000 Notification Services book- you'll find a detailed description of Chronicles in Chapter 6.
Regarding instances (question #3), instances of NS are similar to instances of SQL server. Each instance is a separate, named deployment that you can configure and administer separately. Each instance has it's own set of subscribers (which are shared only among applications in the instance). You should create different instances when you want to isolate applications in terms of configuration, deployment, and security. Chapter 4 in my book explains instances in detail.
Hope this helps
Thanks for your quick responses,
Jeroen van Onzen