n just one of these
resources utilisation is the bottleneck then start by splitting them on
different servers.
Jan
-Original Message-From: Fogelson, Steve
[mailto:[EMAIL PROTECTED]Sent: Thursday,
October 30, 2003 02:44To:
'[EMAIL PROTECTED]'Subject: RE: Witango-Talk: database on
another s
Title: RE: Witango-Talk: database on another
server
So that's what you get for asking a simple question Alan - a
bucket load of info about all sorts of stuff - isn't this list
great?
:-)
So the answer is: yes it'll work, and work pretty well; and as
long as you keep the same database names
Title: RE: Witango-Talk: database on another server
Gareth,
I
don't advocate putting the servers on separate network segments connected over a
internet wanconnection. On the contrary, the closer they are physically
the better (behind theups segment etc.). But as far as ODBC is concerned
One point that I want to remind all readers about is that not all databases and/or database servers work the same way. There may be restrictions placed on them that prevent a setup in which they reside on a separate piece of hardware. The one that sticks on in my mind is MS Access which cannot be
You
are right, Steve. For this to work there needs to beboth client and server
side ODBC connectors. Which should bethe caseformost
commersially availabledb server services of today, the server side ODBC in
many casesintegrated intothe db server service (not available as a
separate
Alan
I've done this using R:Tango and the databases reside on Netware.
I haven't tried this with databases on NT4 but this is how I've got it working for
Netware.
Create a user on Netware and give that user full rights to the database folder
Login using the Netware client (must
Title: Re: Witango-Talk: database on another
server
It is a matter of setting up a DSN via TCP as opposed to your
usual direct connections on the server. Simply create a new DSN which
points to the IP address of the other server and set the appropriate
port for whichever database you are using
Hi
Alan,
Maybe
I misunderstood the question, but if you are going to have WiTango on one server
and the db on another then just (re)configure the ODBC System DSN drivers on the
WiTango server to point to the distant db server.
The
Witango service doesn't know where the database
ubject: RE:
Witango-Talk: database on another server
Hi
Alan,
Maybe I misunderstood the question, but if you are going to have
WiTango on one server and the db on another then just (re)configure the ODBC
System DSN drivers on the WiTango server to point to the distant db
My experience on Windows 2K and Tango 2000 is that there are large
performance benefits by having the database on a different box. I have
noticed this with environments other than Witango as well... When we
deployed our classified ad system originally on Windows it had many
performance
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
11 matches
Mail list logo
