"MarkSW" <MarkSW@discussions.microsoft.com> wrote in message
news:C604990E-0229-4483-8055-329F1A88AE3B@microsoft.com...
> This happens each time I remove a DefaultValue FieldTypeMod in an
nsupdate.
> I'm inclined to say it might be a bug.
>
> "MarkSW" wrote:
>
> > Could an update that modified the FieldTypeMods of one field in a
> > Subscription Schema cause this to happen. It just did on my development
> > machine. Unit test of inserting a subscription now fails because the SP
has
> > disappeared.
> >
> > I can document this and specify that all schema modifications require a
> > delete and create, except that that would hose all of the Subscription
> > information. Is this possibly happening? Is there a workaround?
> >
> > Here is the Exception info. dump:
> >
> > Exception Type: Microsoft.SqlServer.NotificationServices.NSException
> > Message: Notification Services failed to insert the new subscription.
> > InstanceName: RIPerNotif
> > ApplicationName: RINSPER
> > SubscriptionClassName: RINSPERSubscriptions
> > SubscriberId: 4001000000002315
> > SubscriptionId: 0
> > StoredProcedureName: NSInsertRINSPERSubscriptionsSubscription
> > SqlServerError:
> > Source: .Net SqlClient Data Provider
> > Number: 2812
> > State: 62
> > Class: 16
> > Server:
> > Message: Could not find stored procedure
> > 'NSInsertRINSPERSubscriptionsSubscription'.
> > Procedure:
> > Line Number: 0
> > ...
> > ...
> > StackTrace Information
> > *********************************************
> > at Microsoft.SqlServer.NotificationServices.Subscription.Add()
> >
> >
> >

"Shyam Pather [MSFT]" wrote:

> Mark,
> When you make a change to your application that changes the schema of the
> subscriptions table, NS re-creates the table from scratch (it does not
> attempt to alter the table). To prevent loss of valuable subscription data,
> it renames the existing table to NS<SubscriptionClassName>SubscriptionsOld.
> After the update, you must copy the data from the Old subscriptions table
> back into the new one (which is named
> NS<SubscriptionClassName>Subscriptions) and delete the Old table. If you
> don't delete the table, the next update will fail because of a name
> collision when it again tries to rename the existing table.
>
> I know this process is a bit clumsy - we're looking at improving it in the
> next version - but this is the way NS2.0 is designed to work. This is
> described in the Books Online.
>
> If you delete the Old table (after saving any data in it you might need),
> your update will probably succeed and then you should be fine again.
> -shyam
>
> --
> Learn more about SQL-NS:
> http://www.amazon.com/exec/obidos/tg/detail/-/0672326647/
> ---------------------------------------------
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm.
> ---------------------------------------------
> "MarkSW" <MarkSW@discussions.microsoft.com> wrote in message
> news:C604990E-0229-4483-8055-329F1A88AE3B@microsoft.com...
> > This happens each time I remove a DefaultValue FieldTypeMod in an
> nsupdate.
> > I'm inclined to say it might be a bug.
> >
> > "MarkSW" wrote:
> >
> > > Could an update that modified the FieldTypeMods of one field in a
> > > Subscription Schema cause this to happen. It just did on my development
> > > machine. Unit test of inserting a subscription now fails because the SP
> has
> > > disappeared.
> > >
> > > I can document this and specify that all schema modifications require a
> > > delete and create, except that that would hose all of the Subscription
> > > information. Is this possibly happening? Is there a workaround?
> > >
> > > Here is the Exception info. dump:
> > >
> > > Exception Type: Microsoft.SqlServer.NotificationServices.NSException
> > > Message: Notification Services failed to insert the new subscription.
> > > InstanceName: RIPerNotif
> > > ApplicationName: RINSPER
> > > SubscriptionClassName: RINSPERSubscriptions
> > > SubscriberId: 4001000000002315
> > > SubscriptionId: 0
> > > StoredProcedureName: NSInsertRINSPERSubscriptionsSubscription
> > > SqlServerError:
> > > Source: .Net SqlClient Data Provider
> > > Number: 2812
> > > State: 62
> > > Class: 16
> > > Server:
> > > Message: Could not find stored procedure
> > > 'NSInsertRINSPERSubscriptionsSubscription'.
> > > Procedure:
> > > Line Number: 0
> > > ...
> > > ...
> > > StackTrace Information
> > > *********************************************
> > > at Microsoft.SqlServer.NotificationServices.Subscription.Add()
> > >
> > >
> > >
>
>