Can SQL2KEE use 4GB on x64?

I thought I saw someone mention that SQL2KEE can access a full 4GB on x64.
Can someone verify this? Here are 2 links that appear to support this.
http://msdn.microsoft.com/library/de...onsumption.asp
http://msdn.microsoft.com/library/de...management.asp
Running 32-bit version of sqlserver does you no good. See this document for
details.
http://download.microsoft.com/downlo...Advantages.doc
-oj
"Mike Kruchten" <mrk@.fsisolutions.com> wrote in message
news:uyO2zO1eFHA.3836@.tk2msftngp13.phx.gbl...
>I thought I saw someone mention that SQL2KEE can access a full 4GB on x64.
>Can someone verify this? Here are 2 links that appear to support this.
> http://msdn.microsoft.com/library/de...onsumption.asp
> http://msdn.microsoft.com/library/de...management.asp
>
|||Well, being from March 2004 this document doesn't say anything about running
32-bit SQL2000 on x64 W2k3. The following quote from one of the links I
provided leads me to believe that SQL2000EE running in this environment will
be able to use a full 4GB of virtual memory.
On the x64 processor, each 32-bit application receives 4 GB virtual address
space in the WOW64 environment, if the application has the
IMAGE_FILE_LARGE_ADDRESS_AWARE flag set in the image header. If this flag is
not set, the 32-bit application receives 2 GB virtual address space.
"oj" <nospam_ojngo@.home.com> wrote in message
news:u7XB3Q6eFHA.3932@.TK2MSFTNGP12.phx.gbl...
> Running 32-bit version of sqlserver does you no good. See this document
> for details.
> http://download.microsoft.com/downlo...Advantages.doc
>
> --
> -oj
>
>
|||You're right. SQL2K (32bit) SP4 allows you to run it in WOW64. Though, I am
not sure if you can actually use up 4Gb. If you have windbg, you can try to
look it up *live* - don't have a x64 here else I would check it out for
sure.
-oj
"Mike Kruchten" <mrk@.fsisolutions.com> wrote in message
news:ukcPvG%23eFHA.1456@.TK2MSFTNGP15.phx.gbl...
> Well, being from March 2004 this document doesn't say anything about
> running 32-bit SQL2000 on x64 W2k3. The following quote from one of the
> links I provided leads me to believe that SQL2000EE running in this
> environment will be able to use a full 4GB of virtual memory.
>
> On the x64 processor, each 32-bit application receives 4 GB virtual
> address space in the WOW64 environment, if the application has the
> IMAGE_FILE_LARGE_ADDRESS_AWARE flag set in the image header. If this flag
> is not set, the 32-bit application receives 2 GB virtual address space.
>
>
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:u7XB3Q6eFHA.3932@.TK2MSFTNGP12.phx.gbl...
>
|||Is there any official work on this yet?
Daren
"Mike Kruchten" <mrk@.fsisolutions.com> wrote in message
news:uyO2zO1eFHA.3836@.tk2msftngp13.phx.gbl...
> I thought I saw someone mention that SQL2KEE can access a full 4GB on x64.
> Can someone verify this? Here are 2 links that appear to support this.
>
http://msdn.microsoft.com/library/de...onsumption.asp
>
http://msdn.microsoft.com/library/de...management.asp
>

Can SQL2KEE use 4GB on x64?

I thought I saw someone mention that SQL2KEE can access a full 4GB on x64.
Can someone verify this? Here are 2 links that appear to support this.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/win64/win64/performance_and_memory_consumption.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/win64/win64/memory_management.aspRunning 32-bit version of sqlserver does you no good. See this document for
details.
http://download.microsoft.com/download/0/4/7/047da8d3-aa80-452a-9148-40a7e8a7048a/SQL64bitAdvantages.doc
-oj
"Mike Kruchten" <mrk@.fsisolutions.com> wrote in message
news:uyO2zO1eFHA.3836@.tk2msftngp13.phx.gbl...
>I thought I saw someone mention that SQL2KEE can access a full 4GB on x64.
>Can someone verify this? Here are 2 links that appear to support this.
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/win64/win64/performance_and_memory_consumption.asp
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/win64/win64/memory_management.asp
>|||Well, being from March 2004 this document doesn't say anything about running
32-bit SQL2000 on x64 W2k3. The following quote from one of the links I
provided leads me to believe that SQL2000EE running in this environment will
be able to use a full 4GB of virtual memory.
---
On the x64 processor, each 32-bit application receives 4 GB virtual address
space in the WOW64 environment, if the application has the
IMAGE_FILE_LARGE_ADDRESS_AWARE flag set in the image header. If this flag is
not set, the 32-bit application receives 2 GB virtual address space.
"oj" <nospam_ojngo@.home.com> wrote in message
news:u7XB3Q6eFHA.3932@.TK2MSFTNGP12.phx.gbl...
> Running 32-bit version of sqlserver does you no good. See this document
> for details.
> http://download.microsoft.com/download/0/4/7/047da8d3-aa80-452a-9148-40a7e8a7048a/SQL64bitAdvantages.doc
>
> --
> -oj
>
>|||You're right. SQL2K (32bit) SP4 allows you to run it in WOW64. Though, I am
not sure if you can actually use up 4Gb. If you have windbg, you can try to
look it up *live* - don't have a x64 here else I would check it out for
sure.
--
-oj
"Mike Kruchten" <mrk@.fsisolutions.com> wrote in message
news:ukcPvG%23eFHA.1456@.TK2MSFTNGP15.phx.gbl...
> Well, being from March 2004 this document doesn't say anything about
> running 32-bit SQL2000 on x64 W2k3. The following quote from one of the
> links I provided leads me to believe that SQL2000EE running in this
> environment will be able to use a full 4GB of virtual memory.
>
> ---
> On the x64 processor, each 32-bit application receives 4 GB virtual
> address space in the WOW64 environment, if the application has the
> IMAGE_FILE_LARGE_ADDRESS_AWARE flag set in the image header. If this flag
> is not set, the 32-bit application receives 2 GB virtual address space.
>
>
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:u7XB3Q6eFHA.3932@.TK2MSFTNGP12.phx.gbl...
>> Running 32-bit version of sqlserver does you no good. See this document
>> for details.
>> http://download.microsoft.com/download/0/4/7/047da8d3-aa80-452a-9148-40a7e8a7048a/SQL64bitAdvantages.doc
>>
>> --
>> -oj
>>
>|||Is there any official work on this yet?
Daren
"Mike Kruchten" <mrk@.fsisolutions.com> wrote in message
news:uyO2zO1eFHA.3836@.tk2msftngp13.phx.gbl...
> I thought I saw someone mention that SQL2KEE can access a full 4GB on x64.
> Can someone verify this? Here are 2 links that appear to support this.
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/win64/win64/performance_and_memory_consumption.asp
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/win64/win64/memory_management.asp
>

Can SQL2KEE use 4GB on x64?

I thought I saw someone mention that SQL2KEE can access a full 4GB on x64.
Can someone verify this? Here are 2 links that appear to support this.
http://msdn.microsoft.com/library/d...consumption.asp
http://msdn.microsoft.com/library/d..._management.aspRunning 32-bit version of sqlserver does you no good. See this document for
details.
http://download.microsoft.com/downl...tAdvantages.doc
-oj
"Mike Kruchten" <mrk@.fsisolutions.com> wrote in message
news:uyO2zO1eFHA.3836@.tk2msftngp13.phx.gbl...
>I thought I saw someone mention that SQL2KEE can access a full 4GB on x64.
>Can someone verify this? Here are 2 links that appear to support this.
> http://msdn.microsoft.com/library/d...consumption.asp
> http://msdn.microsoft.com/library/d..._management.asp
>|||Well, being from March 2004 this document doesn't say anything about running
32-bit SQL2000 on x64 W2k3. The following quote from one of the links I
provided leads me to believe that SQL2000EE running in this environment will
be able to use a full 4GB of virtual memory.
---
On the x64 processor, each 32-bit application receives 4 GB virtual address
space in the WOW64 environment, if the application has the
IMAGE_FILE_LARGE_ADDRESS_AWARE flag set in the image header. If this flag is
not set, the 32-bit application receives 2 GB virtual address space.
"oj" <nospam_ojngo@.home.com> wrote in message
news:u7XB3Q6eFHA.3932@.TK2MSFTNGP12.phx.gbl...
> Running 32-bit version of sqlserver does you no good. See this document
> for details.
> http://download.microsoft.com/downl...tAdvantages.doc
>
> --
> -oj
>
>|||You're right. SQL2K (32bit) SP4 allows you to run it in WOW64. Though, I am
not sure if you can actually use up 4Gb. If you have windbg, you can try to
look it up *live* - don't have a x64 here else I would check it out for
sure.
-oj
"Mike Kruchten" <mrk@.fsisolutions.com> wrote in message
news:ukcPvG%23eFHA.1456@.TK2MSFTNGP15.phx.gbl...
> Well, being from March 2004 this document doesn't say anything about
> running 32-bit SQL2000 on x64 W2k3. The following quote from one of the
> links I provided leads me to believe that SQL2000EE running in this
> environment will be able to use a full 4GB of virtual memory.
>
> ---
> On the x64 processor, each 32-bit application receives 4 GB virtual
> address space in the WOW64 environment, if the application has the
> IMAGE_FILE_LARGE_ADDRESS_AWARE flag set in the image header. If this flag
> is not set, the 32-bit application receives 2 GB virtual address space.
>
>
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:u7XB3Q6eFHA.3932@.TK2MSFTNGP12.phx.gbl...
>|||Is there any official work on this yet?
Daren
"Mike Kruchten" <mrk@.fsisolutions.com> wrote in message
news:uyO2zO1eFHA.3836@.tk2msftngp13.phx.gbl...
> I thought I saw someone mention that SQL2KEE can access a full 4GB on x64.
> Can someone verify this? Here are 2 links that appear to support this.
>
http://msdn.microsoft.com/library/d...consumption.asp
>
http://msdn.microsoft.com/library/d...ent.asp

>

Can someone help explain?

Hi,

I am working with several tables, but for now I just mention 4 : one is fact table (named Usage), and 3 dimensional tables Periods, Products, and Regions. The fact table contains references to the dimensional tables. Table Periods contain two other columns month and year.

I created a cube containing columns from those 4 tables. Deployment was successful. Trouble comes when I want to create a mining structure using Time Series containing these columns :

- Period
- Amount (of money)
- Product name
- Region name

When I choose to use cube (instead of table) as source for mining structure, I'm forced to choose only one dimension (among the Periods, Products, and Regions). Whatever dimension I choose I end up being unable to use the column period as the Time-Key column. Effectively I cannot use Time Series method since I cannot use the column period.

(1) Why is this so [why Visual Studio forced us to use only one dimension from the cube] ?
(2) Why Visual Studio eliminates the column period, column that has relationship with the
time dimension?
(3) What is the use of Cube anyway to the mining? Is there still any use for it?
(4) What is the solution to that kind of problem I face?

Thank you,

Bernaridho
Dear all,

I have not received any answer why can I use only one dimension when using a cube to mine data. Can someone help explain please? The details are ini my previous posting.

Thank you,

Bernaridho
|||

#1. The current design on OLAP-based mining structures requires that case-level columns be member properties of the key - this is a strict way of making sure that the attributes refer to the same entity (the case) and the requirement is met if all the case columns come from the same dimension.

#2. The data mining engine does not have time intelligence in terms of recognizing the special status of the time dimension so unless there is explicit relationship through inclusion of the case dimension and time dimension in a measuregroup, the dimension cannot be included (as a nested table).

#3. Building mining models on top of cubes is useful when you already have the data in that form (and you don't want to or don't have access to the source data) and also for applying the results of data mining back to the cube to slice/dice the fact data with the hierarchies discovered by the model. For instance, you could build a cluster model and slice your facts by the clusters.

#4. In your case, it might be better to build your time series model directly on the source (relational) data since you will have much more flexibility in that case.

|||

You can also use DMX to create the models. DMX allows the form

INSERT INTO <mining model>(<columns>)

<MDX statement>

In this form it uses the flattening semantics of MDX to populate the mining model. This way you can create any arbitrary dataset as input into the mining model.

|||Are there any more details to this question?