"HMSSkeptical" wrote:

> Hi All,
>
> Have apps on user XP PCs running Server2000 MSDE - sharing into db on MS
> Server 2003 x64 file server with SQL Server 2000 Std Edition Single CPU
> Unlimited users (with all latest hotfixes Build 8.00.2249, using the 32 bit
> version x86 ).
>
> Server 2000 Std Edition was configured to 32 users at setup. We have about
> 14 active users running multithreaded apps that could have as many as 15
> request to the SQL server at a time. We (possibly stupidly) assumed  that 32
> users meant support for lots of connections per user.
>
> We are seeing lots of timeout messages:
>
>  getConnection{} failed
>
> SqlConnectionFactoryImpl.getConnection: Timeout expired The timeout period
> expired prior to completion of the operation or the server is not responding
>
> When logged into the device that Server 2000 0is running on, the Event
> Viewer rarely shows any hint of a problem, other than an occasional SQL
> Server stopped.
>
> When trying to stop, and then restart, using the SQL ServerManager from the
> tray, the "stopping" part never completes. We have to kill tasks using Task
> Manager.
>
> Comments ? Ideas ? Solutions ?  If we need to revise the number of users
> upward, how do we do this ?  Reinstall (on top of existing) did not allow
> respecification of number of users.

"HMSSkeptical" wrote:

> Hi,
>
> First, asuume a large level of ignorance on this end. Didn't know we could
> leave it at "0". A big question is how to reset ? As I mentioned, I tried a
> re-install (over existing, not uninstall/reinstall - didn't want to clobber
> existing DB files) and was not asked for number of users.
>
> My guess is that no hotfixes have ever been applied on the MDSE side; that
> may be a contributor but unknown. On the user side (the MSDE side) they have
> no explicit control over number of connections. Driven by app requirements.
>
> We also see the timeouts when trying to do the initial connection to the Std
> Edition DB on the file server, so I'm pretty sure the problem is on that
> side.
>
> Is there a way to increase the timeout limit ? I've been trying to find
> something in the Enterprise Manager that lets me do local client
> configuration tasks and can't find anything.
>
> Regards
>
> "HMSSkeptical" wrote:
>
> > Hi All,
> >
> > Have apps on user XP PCs running Server2000 MSDE - sharing into db on MS
> > Server 2003 x64 file server with SQL Server 2000 Std Edition Single CPU
> > Unlimited users (with all latest hotfixes Build 8.00.2249, using the 32 bit
> > version x86 ).
> >
> > Server 2000 Std Edition was configured to 32 users at setup. We have about
> > 14 active users running multithreaded apps that could have as many as 15
> > request to the SQL server at a time. We (possibly stupidly) assumed  that 32
> > users meant support for lots of connections per user.
> >
> > We are seeing lots of timeout messages:
> >
> >  getConnection{} failed
> >
> > SqlConnectionFactoryImpl.getConnection: Timeout expired The timeout period
> > expired prior to completion of the operation or the server is not responding
> >
> > When logged into the device that Server 2000 0is running on, the Event
> > Viewer rarely shows any hint of a problem, other than an occasional SQL
> > Server stopped.
> >
> > When trying to stop, and then restart, using the SQL ServerManager from the
> > tray, the "stopping" part never completes. We have to kill tasks using Task
> > Manager.
> >
> > Comments ? Ideas ? Solutions ?  If we need to revise the number of users
> > upward, how do we do this ?  Reinstall (on top of existing) did not allow
> > respecification of number of users.

"Rick Sawtell" wrote:

> >> First, asuume a large level of ignorance on this end. Didn't know we
> >> could
> >> leave it at "0". A big question is how to reset ? As I mentioned, I tried
> >> a
> >> re-install (over existing, not uninstall/reinstall - didn't want to
> >> clobber
> >> existing DB files) and was not asked for number of users.
>
> exec sp_configure 'show advanced options', 1
> GO
>
> RECONFIGURE
> GO
>
> exec sp_configure 'user connections', 0
> GO
>
> RECONFIGURE
> GO
>
> There is probably a way to do it through one of the GUI's as well, but I
> find those tedious at the best of times.
>
> In addition to this, you may want to bump up your "max worker threads" value
> as well.  Google around or check the BOL for more information on this
> setting.
>
>
>
>
> >> We also see the timeouts when trying to do the initial connection to the
> >> Std
> >> Edition DB on the file server, so I'm pretty sure the problem is on that
> >> side.
>
> If you have multiple apps trying to make 15 connections each and you are set
> up for only 32 connections, then I could see this as a problem.
>
>
> >> Is there a way to increase the timeout limit ? I've been trying to find
> >> something in the Enterprise Manager that lets me do local client
> >> configuration tasks and can't find anything.
>
> Yes, but I think the default timeout is either 0 (forever) or 600 (10
> minutes).
> Take a look at the sp_configure option for remote query timeout (s)
>
>
> Good luck
>
>
> Rick Sawtell
>
>
>
>
>
>

"HMSSkeptical" <HMSSkepti***@discussions.microsoft.com> wrote in message
news:736DF663-D171-49D0-894B-337DB12DF587@microsoft.com...
> Hi again,
>
> OK, we tried your suggestions; we'll see if things get better shortly. A
> couple of ancillary questions:
>
> 1) Are the hotfixes REALLY cumulative as it says at the top of  the hotfix
> web page, or should we be applying individual hotfixes if they look like
> they
> could affecet performance ?
>
> 2) Have you ever run across a circumstance where the SQL Server just seems
> to go zombie and must be Kill Process Tree'd from Task Manager and
> restarted ?
>
> That's what we see. No hint in the log files of anything odd. It just goes
> stupid.
>
> Best regards, and thanx !
>
>

"Rick Sawtell" wrote:

>
> "HMSSkeptical" <HMSSkepti***@discussions.microsoft.com> wrote in message
> news:736DF663-D171-49D0-894B-337DB12DF587@microsoft.com...
> > Hi again,
> >
> > OK, we tried your suggestions; we'll see if things get better shortly. A
> > couple of ancillary questions:
> >
> > 1) Are the hotfixes REALLY cumulative as it says at the top of  the hotfix
> > web page, or should we be applying individual hotfixes if they look like
> > they
> > could affecet performance ?
> >
> > 2) Have you ever run across a circumstance where the SQL Server just seems
> > to go zombie and must be Kill Process Tree'd from Task Manager and
> > restarted ?
> >
> > That's what we see. No hint in the log files of anything odd. It just goes
> > stupid.
> >
> > Best regards, and thanx !
> >
> >
>
> At least for SQL Server, cumulative, means cumulative.
>
> As for the going zombie.  Check other processes etc.  Do you have anti-virus
> running on the server?  Are you having networking issues of any type (DNS,
> NICs, bandwidth etc.).   Check the disk queue lengths to ensure that you are
> not overloading the disk drives etc. etc. etc.   There are a lot of things
> that could be causing these slowdowns.  Do you have unnecessary services
> running on your SQL Server box.  Is it the AD domain controller?  Is it
> running print spooler.
>
> Rick Sawtell
>
>
>