17 minutes is a long time. My typical experience is in the 5 - 7 minute
range, which in my opinion is still too slow. But this can be affected by
the computer and processing load.
I do not know of any QFE for this issue, and I don't think it has been added
to SP1 at this time. I have opened a new bug and reported your experience.
Diane Larsen [MSFT]
SQL Server User Education
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
"Vince Sefcik" <[email protected]> wrote in message
> Thanks, Diane. I did as you suggested and the update did finally
> after seventeen (17) minutes! I sure hope the bugs are addressed soon,
> because it would be grief to have to wait this long just to have the
> compiler report a minor typographical error in a Select statement.
> I think I may have to look at an alternative development process. I have
> VB.NET program that exports and imports all Subscribers and Subscriptions.
> So, I might just have to update the program to also export and import my
> chron tables and then use nscontrol delete/create (with an export prior to
> the delete and an import after the create) instead of nscontrol update.
> This will probably keep me going until the bug fix is available. I
> certainly would like to know if a patch will be available before Service
> Pack 1 is released.
> Again, thanks for your help.
> "Diane Larsen [MSFT]" <[email protected]> wrote in message
> news:%[email protected]
> > It can take several minutes to update an instance. This is not a great
> > experience. The reason is known (it has to do with some lower-level code
> > used by NS), and bugs have been filed.
> > Let it run for several minutes. It should complete. (It has every time
> > me.)
> > When using SQL Server Managment Studio, I often multitask and don't
> > realize
> > that a secondary window has popped up that requires me to click OK. I
> > thought I should mention that.
> > --
> > Diane Larsen [MSFT]
> > Technical Writer
> > SQL Server User Education
> > 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.
> > "Vince Sefcik" <[email protected]> wrote in message
> > news:[email protected]
> >> I have an application that has run under NS 2.0 for over a year. I
> > updated
> >> it many times using "nscontrol update" without a problem. I recently
> >> converted the application to NS 2005 ande SQL Server 2005. After
> > the
> >> necessary changes (e.g., change Notify function to Insert Into), I was
> > able
> >> to run "nscontrol create" and built the instance and application
> > databases,
> >> added a subscriber and subscription and it ran fine.
> >> I then needed to update the application using "nscontrol update" and
> >> nscontrol never completes. Regardless of whether I run nscontrol as a
> >> command-line or via Management Studio, the same happens: I get the
> >> message
> >> "Examining instance : ...", CPU cycles at 15%-40% (used by
> > and
> >> the process never ends. If I kill the process, re-enable all
> > and
> >> restart the Windows instance service, it works fine (with the
> > configuration
> >> prior to running "nscontrol update"). If I recreate the databases
> >> "nscontrol delete" and "nscontrol create", everthing works OK. But,
> >> "nscontrol update" never gets past the "Examining instance" step.
> >> I'm using SQL Server 2005 Developer edition.
> >> Any suggestions on how to track down why "nscontrol update" never gets
> > past
> >> "Examining instance.."?