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:
>
Showing posts with label budget. Show all posts
Showing posts with label budget. Show all posts
Friday, March 30, 2012
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
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:
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:
Monday, March 12, 2012
MDX syntax error only on VS 2005
Hi, look im having this error frecuently on Visual Studio 2005, while executing a MDX query...
SELECT NON EMPTY { [Measures].[Budget Lead Count] } ON COLUMNS
FROM [LTL_Budget_Forecast] CELL PROPERTIES VALUE
but when I execute the same query on SQL Management Studio 2005, everything goes fine... and the query is executed successfully
Do you know what could be the problem here?
thx...
Regards,
-EWhat is the exact error you are getting? And where are you executing the query from? Is it in reporting services? The reporting services provider does some extra work and I would guess that the "non empty" clause on the columns would update reporting services as it requires a fixed set of columns.|||Thanks Darren,
the exact error displays as follows:
SQL Execution Error
Executed SQL Statement: SELECT NON EMPTY { [Measures].[Budget Lead Count] } ON COLUMNS
FROM [LTL_Budget_Forecast] CELL PROPERTIES VALUE
Error Source: .Net SqlClient Data Provider
Error Message: Incorrect syntax near '{'
Im executing this query on MS Visual Studio 2005, and my project is a Report Server Project|||
> Error Source: .Net SqlClient Data Provider
There's your problem. You should be using either the Analysis Services Provider or the OLEDB provider with the MSOLAP 9.0 OLE DB driver. The Analysis Services Provider gives you a friendlier MDX designer experience, so I would probably try that one first.
If you have both SQL and MDX based reports you will need to set up a second data source. If the report project only needs to run MDX queries, the you will need to change the details of the current data source.
|||Thanks a lot Darren, I solved that problem setting up a second data source...Regards,
-E
Subscribe to:
Posts (Atom)