about subscribers

i have millions of subscribers,

any good idea to manage those subscribers efficently?

thanks

Same old, same old... Query optimization (the most important thing!!!...).

And remember that you can add custom indexes to NS tables.

Also, if possible, break your application into several separate applications based on the module's functionality, and run them separately, maybe even on separate machines.

Also, for performance, use SQL Server server machine for the SQL stuff only, and move the NS service and all other resources-hungry stuff (custom event providers, content formatters, etc.) to other server(s).

Use subscription expiration to remove all "old" subscriptions, and once in a while prompt your customers to confirm their old subscriptions (that they still want to receive their alerts AND confirm email addresses, cell phone #s, etc.). Maybe, even distribute your own notification with the request for confirmation; do it a few times; if someone does not reply, remove this subscriber.

|||

Thanks for that,and

Any good idea about how to create subscribers quickly,especially millions of subscribers

|||

For SSNS in 2000, you have to use the API.

In SSNS 2005, you can insert into subscriber views. Here's an example.

http://sqlns.blogspot.com/2005/10/creating-subscribers-in-2005.html

HTH...

Joe

about emailchannel?

I use email to notify my subscribers,but how to define my email format?

any idea?

thanks in advance

I'm not sure what exactly you mean by mail format...

If you are talking about "building" a custom email message with all data from your notification class, you need to create your custom content formatter.

If you have a Shyam Pather's book (2000 or 2005), which is a must-have for everyone working with SQL-NS, building your own custom content formatter is VERY easy if you just modify the sample from the book.

Also, you can use the built-in XSLT content formatter, but I personally found it much easier to build my own one, using C#. Just for your reference, creating a custom content formatter prototype took me just a few hours, so it's not as bad as it may sound...