Reboot, how often?

Hello,
We have noticed that we begin developing system stability issues with our
database client systems (everything is running on Windows 2K... SQL Server
is on a Win 2k Server system and the clients are running Win 2k Pro) after a
little over a month. A reboot of the server system seems to straighten out
this issue.
Has anyone encountered an article or information about a recommended reboot
time period for Windows 2000 Server systems running SQL Server?
Thank you for any help.Ideally, you should never have to reboot the server, except when the power
goes out or the system software is upgraded in a way that requires a reboot.
Are you sure that your application(s) or user(s) aren't causing memory leaks
or spiraled CPU usage? Any hints in the event log that might correlate to
these "stability issues"? What are these issues, specifically?
We have a windows 2000 server with SQL 7.0 in production, that is used quite
heavily throughout the day by many clients in both the US and Europe, and
the last time it was rebooted was when we changed data centers. I also run
several SQL Server 2000 systems that have never been rebooted for "stability
issues"...
"Michael" <somone@.somewhere.com> wrote in message
news:ud0Jwn9RDHA.2460@.TK2MSFTNGP10.phx.gbl...
> Hello,
> We have noticed that we begin developing system stability issues with
our
> database client systems (everything is running on Windows 2K... SQL Server
> is on a Win 2k Server system and the clients are running Win 2k Pro) after
a
> little over a month. A reboot of the server system seems to straighten
out
> this issue.
> Has anyone encountered an article or information about a recommended
reboot
> time period for Windows 2000 Server systems running SQL Server?
> Thank you for any help.
>|||Having said that, Analysis Services can sometimes be a different issue
altogether. :-)
> We have a windows 2000 server with SQL 7.0 in production, that is used
quite
> heavily throughout the day by many clients in both the US and Europe, and
> the last time it was rebooted was when we changed data centers. I also
run
> several SQL Server 2000 systems that have never been rebooted for
"stability
> issues"...

really simple question

Hi Everyone,
I'd like to test developing in SQL on my peer network before installing
the application on my clients' servers. I am using VB.Net and MSDE as
my tools.
Question:
- Does MSDE have to be installed on each station in my peer-to-peer LAN?
or
Do I _only_ need to install it on the station with the actual database
files (mdf/ldf files)?
Thanks
Richard
hi Richard,
"Richard Fagen" <no_spam@.my_isp.com> ha scritto nel messaggio
news:%23G2LfjzEEHA.3784@.TK2MSFTNGP10.phx.gbl...
> Hi Everyone,
> I'd like to test developing in SQL on my peer network before installing
> the application on my clients' servers. I am using VB.Net and MSDE as
> my tools.
> Question:
> - Does MSDE have to be installed on each station in my peer-to-peer LAN?
> or
> Do I _only_ need to install it on the station with the actual database
> files (mdf/ldf files)?
>
as MSDE acts in a traditional client/server and multi-user situation, you
usually only have to install 1 instance of MSDE on the server that all
clients want to connect to.
if every pc on the lan hosts MSDE, than usually each of them will query the
local MSDE acting as a single user or desktop solution..
in the first scenario, only 1 MSDE server is available, every client will
connect to it and both queryes and results will be sent over the network..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.6.0 - DbaMgr ver 0.52.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply