my sql2000 manual says that sql server minimises vm swapp [thus de-creasing
overall memory usage swapp+phys] trying to dedicate disk i/o mostly to
database access.

but what if swapp is not located on same drive as database files are?
then swapping is not in collision with database read/write, since they not
occur on the same drive.
maybe i may increase overall sql server performances using dedicated swapp
drive [small volume, but very fast], and increasing using of memory
swapping?

am i right, and how to setup sqlserver2000 to allocate more memory
[swapp+phys] than it would do by default?

thnx

"sali" <sali@euroherc.hr> je napisao u poruci interesnoj
grupi:%23P2LllKBHHA.1196@TK2MSFTNGP03.phx.gbl...
> my sql2000 manual says that sql server minimises vm swapp [thus
> de-creasing overall memory usage swapp+phys] trying to dedicate disk i/o
> mostly to database access.
>
> but what if swapp is not located on same drive as database files are?
> then swapping is not in collision with database read/write, since they not
> occur on the same drive.

just for conclusion:
aftere additional searching the knowledgebase i found that this question is
totaly wrong [at least in the context of sqlserver architect]

www.sql-server-performance.com gave me answers about this [and many future]
question