Memory allocation

I'm getting ready to build a new SQL 2000 server. Due to budget constraints
,
I am going to be building SQL Standard on Windows 2000 Standard. I'm unclea
r
as to whether or not, in this scenario, I can allocate more than 2 GB of RAM
.
I know you can put a switch in the boot.ini if you're running Advanced
Server, but is this switch useable with Windows 2000 Standard?
Thanks,
MarshaThe Books Online <architec.chm::/8_ar_ts_8dbn.htm> states that SQL 2000 SE
has a 2GB memory limit. Also, the /3GB boot.ini switch is unsupported under
Windows 2000 Standard as described in
http://support.microsoft.com/kb/291988. The /3GB is available with Windows
2000 Standard but only for testing purposes.
Hope this helps.
Dan Guzman
SQL Server MVP
"Marsha" <Marsha@.discussions.microsoft.com> wrote in message
news:CD2B35E4-A9FA-48B8-A466-AF6E687321F3@.microsoft.com...
> I'm getting ready to build a new SQL 2000 server. Due to budget
> constraints,
> I am going to be building SQL Standard on Windows 2000 Standard. I'm
> unclear
> as to whether or not, in this scenario, I can allocate more than 2 GB of
> RAM.
> I know you can put a switch in the boot.ini if you're running Advanced
> Server, but is this switch useable with Windows 2000 Standard?
> Thanks,
> Marsha|||Thank you for your response.
"Marsha" wrote:

> I'm getting ready to build a new SQL 2000 server. Due to budget constrain
ts,
> I am going to be building SQL Standard on Windows 2000 Standard. I'm uncl
ear
> as to whether or not, in this scenario, I can allocate more than 2 GB of R
AM.
> I know you can put a switch in the boot.ini if you're running Advanced
> Server, but is this switch useable with Windows 2000 Standard?
> Thanks,
> Marsha|||Note that Windows 2003 Standard supports up to 4GB RAM, according to
http://www.microsoft.com/windowsser...s.msp
x.
However, SQL2000 Standard still only supports 2GB so it doesn't currently
help.
If you look to the future however, SQL2005 standard will support "unlimited"
RAM when run on 64-bit systems like the new AMD Opterons. This would require
Windows 2003/64 or whatever it's called. I've heard that MS is going to
offer a free upgrade from XP or W2k3 to the 64bit equivalent edition. So
depending on the memory limitations MS sets on W2k3/64 Standard you may be
able to use significantly more RAM in the not too distant future.
Here's a link to some SQL2005 info.
http://www.microsoft.com/sql/2005/p...005features.asp
Mike Kruchten
"Marsha" <Marsha@.discussions.microsoft.com> wrote in message
news:EFC6C0D6-514D-4729-B985-C0E800891D12@.microsoft.com...[vbcol=seagreen]
> Thank you for your response.
> "Marsha" wrote:
>

Memory allocation

I'm getting ready to build a new SQL 2000 server. Due to budget constraints,
I am going to be building SQL Standard on Windows 2000 Standard. I'm unclear
as to whether or not, in this scenario, I can allocate more than 2 GB of RAM.
I know you can put a switch in the boot.ini if you're running Advanced
Server, but is this switch useable with Windows 2000 Standard?
Thanks,
MarshaThe Books Online <architec.chm::/8_ar_ts_8dbn.htm> states that SQL 2000 SE
has a 2GB memory limit. Also, the /3GB boot.ini switch is unsupported under
Windows 2000 Standard as described in
http://support.microsoft.com/kb/291988. The /3GB is available with Windows
2000 Standard but only for testing purposes.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Marsha" <Marsha@.discussions.microsoft.com> wrote in message
news:CD2B35E4-A9FA-48B8-A466-AF6E687321F3@.microsoft.com...
> I'm getting ready to build a new SQL 2000 server. Due to budget
> constraints,
> I am going to be building SQL Standard on Windows 2000 Standard. I'm
> unclear
> as to whether or not, in this scenario, I can allocate more than 2 GB of
> RAM.
> I know you can put a switch in the boot.ini if you're running Advanced
> Server, but is this switch useable with Windows 2000 Standard?
> Thanks,
> Marsha|||Thank you for your response.
"Marsha" wrote:
> I'm getting ready to build a new SQL 2000 server. Due to budget constraints,
> I am going to be building SQL Standard on Windows 2000 Standard. I'm unclear
> as to whether or not, in this scenario, I can allocate more than 2 GB of RAM.
> I know you can put a switch in the boot.ini if you're running Advanced
> Server, but is this switch useable with Windows 2000 Standard?
> Thanks,
> Marsha|||Note that Windows 2003 Standard supports up to 4GB RAM, according to
http://www.microsoft.com/windowsserver2003/evaluation/features/compareeditions.mspx.
However, SQL2000 Standard still only supports 2GB so it doesn't currently
help.
If you look to the future however, SQL2005 standard will support "unlimited"
RAM when run on 64-bit systems like the new AMD Opterons. This would require
Windows 2003/64 or whatever it's called. I've heard that MS is going to
offer a free upgrade from XP or W2k3 to the 64bit equivalent edition. So
depending on the memory limitations MS sets on W2k3/64 Standard you may be
able to use significantly more RAM in the not too distant future.
Here's a link to some SQL2005 info.
http://www.microsoft.com/sql/2005/productinfo/sql2005features.asp
Mike Kruchten
"Marsha" <Marsha@.discussions.microsoft.com> wrote in message
news:EFC6C0D6-514D-4729-B985-C0E800891D12@.microsoft.com...
> Thank you for your response.
> "Marsha" wrote:
>> I'm getting ready to build a new SQL 2000 server. Due to budget
>> constraints,
>> I am going to be building SQL Standard on Windows 2000 Standard. I'm
>> unclear
>> as to whether or not, in this scenario, I can allocate more than 2 GB of
>> RAM.
>> I know you can put a switch in the boot.ini if you're running Advanced
>> Server, but is this switch useable with Windows 2000 Standard?
>> Thanks,
>> Marsha

Memory allocation

I'm getting ready to build a new SQL 2000 server. Due to budget constraints,
I am going to be building SQL Standard on Windows 2000 Standard. I'm unclear
as to whether or not, in this scenario, I can allocate more than 2 GB of RAM.
I know you can put a switch in the boot.ini if you're running Advanced
Server, but is this switch useable with Windows 2000 Standard?
Thanks,
Marsha
The Books Online <architec.chm::/8_ar_ts_8dbn.htm> states that SQL 2000 SE
has a 2GB memory limit. Also, the /3GB boot.ini switch is unsupported under
Windows 2000 Standard as described in
http://support.microsoft.com/kb/291988. The /3GB is available with Windows
2000 Standard but only for testing purposes.
Hope this helps.
Dan Guzman
SQL Server MVP
"Marsha" <Marsha@.discussions.microsoft.com> wrote in message
news:CD2B35E4-A9FA-48B8-A466-AF6E687321F3@.microsoft.com...
> I'm getting ready to build a new SQL 2000 server. Due to budget
> constraints,
> I am going to be building SQL Standard on Windows 2000 Standard. I'm
> unclear
> as to whether or not, in this scenario, I can allocate more than 2 GB of
> RAM.
> I know you can put a switch in the boot.ini if you're running Advanced
> Server, but is this switch useable with Windows 2000 Standard?
> Thanks,
> Marsha
|||Thank you for your response.
"Marsha" wrote:

> I'm getting ready to build a new SQL 2000 server. Due to budget constraints,
> I am going to be building SQL Standard on Windows 2000 Standard. I'm unclear
> as to whether or not, in this scenario, I can allocate more than 2 GB of RAM.
> I know you can put a switch in the boot.ini if you're running Advanced
> Server, but is this switch useable with Windows 2000 Standard?
> Thanks,
> Marsha
|||Note that Windows 2003 Standard supports up to 4GB RAM, according to
http://www.microsoft.com/windowsserv...editions.mspx.
However, SQL2000 Standard still only supports 2GB so it doesn't currently
help.
If you look to the future however, SQL2005 standard will support "unlimited"
RAM when run on 64-bit systems like the new AMD Opterons. This would require
Windows 2003/64 or whatever it's called. I've heard that MS is going to
offer a free upgrade from XP or W2k3 to the 64bit equivalent edition. So
depending on the memory limitations MS sets on W2k3/64 Standard you may be
able to use significantly more RAM in the not too distant future.
Here's a link to some SQL2005 info.
http://www.microsoft.com/sql/2005/pr...05features.asp
Mike Kruchten
"Marsha" <Marsha@.discussions.microsoft.com> wrote in message
news:EFC6C0D6-514D-4729-B985-C0E800891D12@.microsoft.com...[vbcol=seagreen]
> Thank you for your response.
> "Marsha" wrote:

MDX query

I'm building a report from SSAS 2005 with three parameters.

start date

end date

project stream

I would filter only the non empty project stream in the actual cost fact table included in the time interval specified with the first two paramenters.

SSRS automatically compose an MDX query that I try to modify to get what I want:

WITHMEMBER [Measures].[ParameterCaption] AS'[PROJECT].[STREAM].CURRENTMEMBER.MEMBER_CAPTION'MEMBER [Measures].[ParameterValue] AS'[PROJECT].[STREAM].CURRENTMEMBER.UNIQUENAME'MEMBER [Measures].[ParameterLevel] AS'[PROJECT].[STREAM].CURRENTMEMBER.LEVEL.ORDINAL'

SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel], [Measures].[EUR] } ONCOLUMNS ,

NONEMPTY [PROJECT].[STREAM].ALLMEMBERSONROWS

FROM [PMO_MDB]

WHERE { STRTOMEMBER(@.FY_MONTH_START) : STRTOMEMBER(@.FY_MONTH_END)}

In this way I get all project streams and I'm not able to filter away the empty cell (using the [Measures].[EUR] defined in the actual cost fact table). In fact SSRS put some intrisict member properties on columns as calculated measure !

There is another way to extract the same info but filtering away the empty cell ?

Cosimo

Take a look at the EXISTING function. I believe you could use it on your row axis to limit Project.Stream members to those associated with a fact entry.

Bryan

|||

Thanks Brjan ... I tried but I get the same result also using EXISTING !

I think the problem is that SSRS put on columns as a calculated measure some properties.

There is another way to extract such properies ?

I try the dimension properties clause ... but nothing happen !

Cosimo

|||

Sorry. I meant the EXISTS function. (The names are so similar I always screw them up.) Here is an example of what I'm describing:

Code Snippet

select

[Measures].[Reseller Sales Amount] on 0,

EXISTS(

[Product].[SubCategory].Members,

{ STRTOMEMBER("[Date].[Date].[June 1, 2003]") : STRTOMEMBER("[Date].[Date].[June 30, 2004]")},

'Reseller Sales'

) on 1

from [Adventure Works]

WHERE { STRTOMEMBER("[Date].[Date].[June 1, 2003]") : STRTOMEMBER("[Date].[Date].[June 30, 2004]")}

For comparison:

Code Snippet

select

[Measures].[Reseller Sales Amount] on 0,

[Product].[SubCategory].Memberson 1

from [Adventure Works]

WHERE { STRTOMEMBER("[Date].[Date].[June 1, 2003]") : STRTOMEMBER("[Date].[Date].[June 30, 2004]")}

Sorry for the confusion,

Bryan

MDX Object Model for Building Queries?

Is there an MDX object model (API) for building queries in code? Even an unsupported one? What is BIDS using behind the scenes?

Thanks

There is no MDX object model other than ADOMD.NET. The parts of ADOMD.NET which allow to build MDX expressions are implemented only in AdomdServer implementation of ADOMD.NET which is to be used inside stored procedures.