We have a server with SQL Server and Analysis services
installed on it. SQL Server does not need more than 1GB of
memory (Not much processing going on). The server has 4GB
of physical memory.

What settings should be applied to the following
environment settings for Analysis Services to be able to
use up to 2GB memory if needed and more than at least 1.2
GB ??

The problem was that we had a process that required more
than 1.2 GB memory but the memory went up to 1.2 GB and
not more.

Minimum allocated memory:
Memory Conservation Treshold:

Thanks for any help.

SQL Server 2000 Standard Edition support up to 2GB memory.

You may adjust your SQL memory configuration at SQL properties.



"David" <anonymous (AT) discussions (DOT) microsoft.com> wrote

Use the 3GB switch for this.

Goto the following file:
C:\boot.ini

and add the "\3GB" keyword there.

THere is something called as the 3 GB switch in MSAS.
U can search for more information on the net for that....
We had a similar problem wherein we seaearched and found
about this \3GB switch and it's implication.

Currently, our MSAS server uses close to 3 GB of memory :-)

Hope this helps!!

regards,
Chennakeshav Adya
MSAS - DW Specialist
Tata Consultancy Services
Pune - 411001
Phone: +91 20 4068160
e-mail:c_adya (AT) yahoo (DOT) com

http://support.microsoft.com/default...b;en-us;295443
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

<Adya.Chennakeshav (AT) morganstanley (DOT) com> wrote

Thanks..........I forgot to include that it is Windows
2000 and SQL Server 2000 Standard Editions....3GB Memory
does not apply........

For Sam, It is not SQL Server. It is Analysis Services
Memory..............

Thanks.

Then you are limited to 2GB in the 32-bit virtual address space.
I typically tell folks to really set it to 1.7GB or there abouts in the
server properties because you need virtual address space for the stack,
executable program segments, etc. So 1.7GB or so is probably a better
practical maximum.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"David." <anonymous (AT) discussions (DOT) microsoft.com> wrote

Thanks..................