Note: Forums will be making significant UX changes to address key usability improvements surrounding search, discoverability and navigation. To learn more about these changes please visit the announcement which can be found HERE.
Notification Services Scaled out deployment question.

Unanswered Notification Services Scaled out deployment question.

  • Tuesday, November 25, 2008 7:30 PM
     
     

    Hello all,

     

    So we have a client that wants to run notification services on a scaled out deployment. Meaning our application database and the notification services database are all on the DB server. While the notification SERVICE and instance along with our application live on the application server.

     

    ApplicationServer =  APP1

    Database Server = DB1

     

    We deployed the NS service on app1, created the instance on DB1 and the NS databases obviously live in DEV1.

     

    We followed the following documentation:

    http://msdn.microsoft.com/en-us/library/ms171337(SQL.90).aspx

     

    And no matter what , we get enabled pending state, or the service would start stating that meta data for the instance isn't available. Is there another guide that goes a little more step-by-step for us lay folk to understand?

     

    And one last question, in a remote/scaled out deployment, where does NSHOST point to? the DB side or APP side?

     

    Thanks.

     

All Replies

  • Tuesday, February 03, 2009 9:21 PM
    Moderator
     
     
    A status of enable pending usually means that the service hasn't started.

    Will the service start?

    HTH...

    Joe

    Joe Webb, SQL Server MVP | http://weblogs.sqlteam.com/joew/