> Does splitting the db to another server save resources on the Witango
> server?
>
> I would assume it saves disk reads, but would it save cpu usage? For example
> , if the search action has "ordered by" columns or a join?
Web servers and database servers have different performance patterns, so
separating them allows each to use the available system resources
appropriately.
> I don't know anything about ODBC. Not sure if the DB engine is part of OBDC.
ODBC ('Open Database Connectivity') is a Microsoft standard that is widely
accepted as a way to talk to databases. Microsoft now calls it 'MDAC', and
they have more on their website about it.
> Is there a way to locate the DB Engine on the second server to move that
> processing to the 2nd server?
ODBC does this, as does JDBC.
> What is the tradeoff of having to transmit the results back to the web and
> Witango server assuming over the network?
On current network standards, not a lot. Most of your query results will be
quite small, and in typical internet hosting installations, the bottleneck
will be your user's connection. Corporate LANs are a different beast, but
you won't find many where userland has a faster network than the data
center. Across most applications, the web server will have more work to do
than the database server.
In general there are significant performance and operational
(management/redundancy etc) benefits.
Regards,
Jason.
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
