Hardware Question

This is a business rather than a technical question.
We have a legacy application that uses a jBase database (www.jbase.com) and
now want to install a SQL Server application on the same hardware. Both
applications need to serve web pages. The box is a dual pentium with 2GB of
memory.
Is that full of risk or are we most likely to be OK. Money is tight and
getting a new server won't be easy, but of course we don't want the whole
thing to crash either.
Many thanksHi Kim
Without knowing more about your system it is hard to answer. Using your
database server for anything other than SQL Server will be a compromise. The
level of compromise will be dependent on the current load and resources on
the server and on the network.
http://www.sql-server-performance.c...re_planning.asp gives some
information on what you should be aiming for.
Before installing SQL Server check out the current performance of the
server, see if there is more than sufficient memory, as SQL Server will grab
as much as it can! Setting the maximum memory for SQL Server will probably b
e
required (which may require purhasing more). Check disc activity, if you can
put the SQL Server log and datafiles on their own spindles then that will be
better, but if all your discs are currently being heavily used then it may b
e
worth seeking an alternative.
If you do install SQL Server, re-benchmark to see if there has been a
significant drop in performance and if that drop is acceptable.
Ideally you would try this on a similar server and not on a production
environment first.
John
"Kim Barnes" wrote:

> This is a business rather than a technical question.
> We have a legacy application that uses a jBase database (www.jbase.com) an
d
> now want to install a SQL Server application on the same hardware. Both
> applications need to serve web pages. The box is a dual pentium with 2GB o
f
> memory.
> Is that full of risk or are we most likely to be OK. Money is tight and
> getting a new server won't be easy, but of course we don't want the whole
> thing to crash either.
> Many thanks|||Many thanks John, that's a great response.
"John Bell" wrote:
[vbcol=seagreen]
> Hi Kim
> Without knowing more about your system it is hard to answer. Using your
> database server for anything other than SQL Server will be a compromise. T
he
> level of compromise will be dependent on the current load and resources on
> the server and on the network.
> http://www.sql-server-performance.c...re_planning.asp gives some
> information on what you should be aiming for.
> Before installing SQL Server check out the current performance of the
> server, see if there is more than sufficient memory, as SQL Server will gr
ab
> as much as it can! Setting the maximum memory for SQL Server will probably
be
> required (which may require purhasing more). Check disc activity, if you c
an
> put the SQL Server log and datafiles on their own spindles then that will
be
> better, but if all your discs are currently being heavily used then it may
be
> worth seeking an alternative.
> If you do install SQL Server, re-benchmark to see if there has been a
> significant drop in performance and if that drop is acceptable.
> Ideally you would try this on a similar server and not on a production
> environment first.
> John
> "Kim Barnes" wrote:
>