"Todd C" <ToddC@discussions.microsoft.com> wrote in message
news:D60A3AE1-0B15-41B3-B4F3-CEF13EB62BFD@microsoft.com...
> Sarah:
>
> When a NS Instance gets created, the databases it creates get copied from
> the Model. It may be flooded with unused schemas. My guess is that you had
> a
> whole bunch of users pre-defined in your Model database when it got
> upgraded
> to SQL 2005, so each user had its own schema, which really are not needed.
>
>
> Just a thought: Are you using SQL Server 2000 or 2005? If the latter, then
> try this:
>
> Open your Model database using SQL Server Management Studio. Expand the
> Security node, then expand the Schemas node. Delete all schemas listed
> except
> the following 4:
>>dbo
>>guest
>>INFORMATION_SCHEMA
>>sys
>
> HTH
> --
> Todd C
>
> [If this response was helpful, please indicate by clicking the appropriate
> answer at the bottom]
>
>
> "Sarah Kingswell" wrote:
>
>> Okay some more news for you on this.. Microsoft have come back to me and
>> explained that 'by design' the sql notification services can only handle
>> a
>> maximum of 25 schemes. HELP!!!! Customer needs this working tomorrow.
>> :-)
>>
>> "Sarah Kingswell" <skingswell@xonitek.co.uk> wrote in message
>> news:eS22XabgHHA.4188@TK2MSFTNGP02.phx.gbl...
>> > Thanks for the advice, I guess I need to get this.
>> >
>> > Our app returns the following error
>> >
>> > The program cannot complete the scheme due to the limit of completed
>> > schemes. You can delete one of the existing completed schemes and then
>> > complete the scheme.
>> >
>> > According to a microsoft technet article the cause is because the
>> > number
>> > of deployed notification schemes is limited in SQL Server Notification
>> > Services. We have 40 completed schemes running but I need over 50!
>> >
>> > Does this help?
>> >
>> >
>> >
>> > "Joe Webb" <joew@webbtechsolutions.com> wrote in message
>> > news:pan.2007.04.18.12.30.35.785841@webbtechsolutions.com...
>> >> On Wed, 18 Apr 2007 05:02:00 -0700, Todd C wrote:
>> >>
>> >>> You really can't configure SSNS by flipping switches in Property
>> >>> Dialog
>> >>> boxes
>> >>> like you do with SQL Server. You need to modify the Instance
>> >>> Configuration
>> >>> File (ICF)and Application Diefinition FIle (ADF), both of which are
>> >>> XML
>> >>> documents.
>> >>>
>> >>> Do yourself a favor and spend the $12 to get Joe Webb's book an the
>> >>> subject
>> >>> before you start messing around with and xml files.
>> >>>
>> >>> http://www.amazon.com/exec/obidos/tg/detail/-/0972688811/qid=1126887917/sr=2-2/ref=pd_bbs_b_2_2/104-8731986-9020765?v=glance&s=books
>> >>>
>> >>>
>> >>> Can you elaborate on "maximum number of events"?
>> >>
>> >> Thanks Todd! I'm glad you've found the book useful. :)
>> >>
>> >> Sarah -
>> >>
>> >> Todd's right; SSNS v2.0 is not integrated into Enterprise Manager. All
>> >> configuration changes must be made by altering the XML-based
>> >> configuration
>> >> files (ICF and ADF) and running NSControl to update the
>> >> instance/application.
>> >>
>> >> SSNS 2005 is fully integrated into SQL Server. It no longer requires
>> >> and
>> >> extended stored procedure and it can be managed through Management
>> >> Studio.
>> >> But, probably not in the way you are hoping. You still must make
>> >> changes
>> >> to the configuration files and then apply them through Management
>> >> Studio
>> >> or through the NSControl utility.
>> >>
>> >> There is the concept of an event throttle, but I'd doubt that's really
>> >> what you're referring to. Can you elaborate a bit on what's causing
>> >> you
>> >> some grief?
>> >>
>> >> Joe
>> >>
>> >>
>> >> --
>> >> Joe Webb
>> >> SQL Server MVP
>> >> http://www.sqlns.com
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>>
>>
>>

On Wed, 18 Apr 2007 15:40:38 +0100, Sarah Kingswell wrote:

> Hi
>
> Customer is using SQL 2000. I take it your suggestion will not work on this
> version. I may have a solution this end which involves reducing the number
> or required schemas. Customer is going live tomorrow on a new web project
> and I need to get this running even if it is a temporary workaround. I will
> have a look at the suggested reading material after the site are in and
> running. Cheers for all your help.
>
> Sarah
>
> "Todd C" <ToddC@discussions.microsoft.com> wrote in message
> news:D60A3AE1-0B15-41B3-B4F3-CEF13EB62BFD@microsoft.com...
>> Sarah:
>>
>> When a NS Instance gets created, the databases it creates get copied from
>> the Model. It may be flooded with unused schemas. My guess is that you had
>> a
>> whole bunch of users pre-defined in your Model database when it got
>> upgraded
>> to SQL 2005, so each user had its own schema, which really are not needed.
>>
>>
>> Just a thought: Are you using SQL Server 2000 or 2005? If the latter, then
>> try this:
>>
>> Open your Model database using SQL Server Management Studio. Expand the
>> Security node, then expand the Schemas node. Delete all schemas listed
>> except
>> the following 4:
>>>dbo
>>>guest
>>>INFORMATION_SCHEMA
>>>sys
>>
>> HTH
>> --
>> Todd C
>>
>> [If this response was helpful, please indicate by clicking the appropriate
>> answer at the bottom]
>>
>>
>> "Sarah Kingswell" wrote:
>>
>>> Okay some more news for you on this.. Microsoft have come back to me and
>>> explained that 'by design' the sql notification services can only handle
>>> a
>>> maximum of 25 schemes. HELP!!!! Customer needs this working tomorrow.
>>> :-)
>>>
>>> "Sarah Kingswell" <skingswell@xonitek.co.uk> wrote in message
>>> news:eS22XabgHHA.4188@TK2MSFTNGP02.phx.gbl...
>>> > Thanks for the advice, I guess I need to get this.
>>> >
>>> > Our app returns the following error
>>> >
>>> > The program cannot complete the scheme due to the limit of completed
>>> > schemes. You can delete one of the existing completed schemes and then
>>> > complete the scheme.
>>> >
>>> > According to a microsoft technet article the cause is because the
>>> > number
>>> > of deployed notification schemes is limited in SQL Server Notification
>>> > Services. We have 40 completed schemes running but I need over 50!
>>> >
>>> > Does this help?
>>> >
>>> >
>>> >
>>> > "Joe Webb" <joew@webbtechsolutions.com> wrote in message
>>> > news:pan.2007.04.18.12.30.35.785841@webbtechsolutions.com...
>>> >> On Wed, 18 Apr 2007 05:02:00 -0700, Todd C wrote:
>>> >>
>>> >>> You really can't configure SSNS by flipping switches in Property
>>> >>> Dialog
>>> >>> boxes
>>> >>> like you do with SQL Server. You need to modify the Instance
>>> >>> Configuration
>>> >>> File (ICF)and Application Diefinition FIle (ADF), both of which are
>>> >>> XML
>>> >>> documents.
>>> >>>
>>> >>> Do yourself a favor and spend the $12 to get Joe Webb's book an the
>>> >>> subject
>>> >>> before you start messing around with and xml files.
>>> >>>
>>> >>> http://www.amazon.com/exec/obidos/tg/detail/-/0972688811/qid=1126887917/sr=2-2/ref=pd_bbs_b_2_2/104-8731986-9020765?v=glance&s=books
>>> >>>
>>> >>>
>>> >>> Can you elaborate on "maximum number of events"?
>>> >>
>>> >> Thanks Todd! I'm glad you've found the book useful. :)
>>> >>
>>> >> Sarah -
>>> >>
>>> >> Todd's right; SSNS v2.0 is not integrated into Enterprise Manager. All
>>> >> configuration changes must be made by altering the XML-based
>>> >> configuration
>>> >> files (ICF and ADF) and running NSControl to update the
>>> >> instance/application.
>>> >>
>>> >> SSNS 2005 is fully integrated into SQL Server. It no longer requires
>>> >> and
>>> >> extended stored procedure and it can be managed through Management
>>> >> Studio.
>>> >> But, probably not in the way you are hoping. You still must make
>>> >> changes
>>> >> to the configuration files and then apply them through Management
>>> >> Studio
>>> >> or through the NSControl utility.
>>> >>
>>> >> There is the concept of an event throttle, but I'd doubt that's really
>>> >> what you're referring to. Can you elaborate a bit on what's causing
>>> >> you
>>> >> some grief?
>>> >>
>>> >> Joe
>>> >>
>>> >>
>>> >> --
>>> >> Joe Webb
>>> >> SQL Server MVP
>>> >> http://www.sqlns.com
>>> >>
>>> >>
>>> >>
>>> >>
>>> >
>>> >
>>>
>>>
>>>