Another option is to wrap up all the SQLNS calls you need to have the
clients call in an web service; then the clients can call the web
service instead of calling the SQLNS API directly. I've used this in a
number of instances with success.
SQL Server MVP
Get up to speed quickly with SQLNS
I support PASS, the Professional Association for SQL Server.
On Wed, 05 Apr 2006 16:05:33 -0400, ramadu <[email protected]> wrote:
>Thanks for that, sudhakar & kate ...
>yes, I did see the previous posts on this after I put this in.
>Unfortunately, I cannot have my clients install notification services
>client components in their machines. I did, however, overcome this
>problem by installing a remoting service on the server.
>Was this a good idea?
>> you would have to initialize the NSinstance object just by specifying
>> the Instance name
>> before doing that you need to install the Notification services client
>> components on the client machine where you would access the NSinstance
>> b) register the NS server and application with your client by using
>> the nscontrol register command , specifying the instance name and the
>> server name as command line arguments.
>> I went thru a similar scenario , in my case I had web app though.
>> for more info go to BOL and check on Deployment of NS .