Re: Weird ADO failure/crash behaviour
- From: "Daniel Crichton" <msnews@xxxxxxxxxxxxxxxxxx>
- Date: Thu, 9 Mar 2006 16:05:57 -0000
Stephen wrote on Thu, 9 Mar 2006 14:30:09 -0000:
My longest record is a Windows NT 4 SP6a Server running our mail system
(NTMail), which managed nearly 18 months uptime in a single stretch -
unfortunately we had a new UPS installed and so I had to turn it off
while the power was out, otherwise it would likely still be running on
that same stretch now ;)
I am running WindowsXP Professional SP2 at home.
I am Windows2000 Professional SP4 at work, and before that I was running
Windows NT SP6a.
I run XP Pro SP2 here at work and at home - I must admit I have a tendency
to leave my home PC on 24/7 (IRC for logging, and a small FTP site for a
close group of friends), and my work PC has a number of scheduled tasks that
run daily so I never turn it off, just reboot as and when needed. I've even
got an XP Pro PC running 24/7 processing product data and order data from
our suppliers - at some point those processes will get moved to a dedicated
server.
My normal practice at work is to leave the computer on at work during the
week, to power-off on Friday, and power-on on Monday. All I can say was
that when I was using Windows NT SP6a, it was hammered with program
development using Visual Studio 6.0 in C++, ADO, SQL Server 7.0
Enterprise, Query Analyser, MFC apps etc. This hammering was such that by
Thursday invariably it needed a reboot. Sometimes there was no choice, I
had complete lockup. Work is kitted out with bog-standard Dells. A week
without rebooting on NT 4.0, SP6a was rare, sometimes 2+ reboots was
required.
I gave up on Dells long ago. Servers are all HP Netservers and Compaq ML
Proliants (although I loathe the Netservers, all 3 of them had most of the
hardware replaced within the first 3 year warranty period, yet the Proliants
just keep on running with never a problem - one of them is an old PPro Dual
500MHz we use for development work that's build like a tank and just as
heavy :P)
With Windows2000, it has been much more stable. I have no had lockups
I
can recall. I have had the occasional glitch but it is rare. I have no
idea how Windows2000 would fare if I left my PC on weeks on end. It would
be an interesting test.
test.
My W2K desktop got rebooted every few weeks, but only due to patches.
Windows 2000 servers have so far been very stable, and rarely require a
reboot (only when critical patches come out, and even then only if it's a
really serious issue as most of these servers are on our internal LAN).
I can only say that maybe NT 4.0 does not find running the mail server or
file/print system too demanding and copes easy.
Possible. Although the mail server is also our primary DNS, and I've been
tinkering with it recently to run ethereal traces (needed to produce some
reports on traffic to our web servers so needed a machine in our DMZ).
Dan
.
- Follow-Ups:
- Re: Weird ADO failure/crash behaviour
- From: Stephen Howe
- Re: Weird ADO failure/crash behaviour
- References:
- Re: Weird ADO failure/crash behaviour
- From: Stephen Howe
- Re: Weird ADO failure/crash behaviour
- From: Daniel Crichton
- Re: Weird ADO failure/crash behaviour
- From: Stephen Howe
- Re: Weird ADO failure/crash behaviour
- Prev by Date: Re: Recordset & Sort
- Next by Date: Re: How to use LIKE operator with Filter prop of recordset for num fie
- Previous by thread: Re: Weird ADO failure/crash behaviour
- Next by thread: Re: Weird ADO failure/crash behaviour
- Index(es):
Relevant Pages
|
