"Missing" Data / Data Not Making It Into AS2005 Cube

All of the data in one of my fact tables in the relational db doesn't seem to be making into the cube. However, all of the data from our sales fact table is indeed making into the cube.

There is no filtering going on in the Named Query in the DSV that brings in this data. What could it be? The table's relationship? Dimension Usage?

I also developed a small test cube and was able to see all of the data. I would hate the thought of having to rebuild/redevelop the cube from scratch.

I've tried everything that I could think of.

Any thoughts?

Hello. One possible explanation can be that the service account, running SSAS2005, do not have permissions in your relational db. Are all you fact tables in the same database /data warehouse? Do you have several data source systems?

Regards

Thomas Ivarsson

|||I think I'm making progress on the troubleshooting.

I just deleted a lot of the dimensions in the Dimension Usage tab for this particular measure group. In doing so, all of the data is now there.

I will slowly add the dimension relationships back to see which one is the cause and then will try to understand why that is the case.|||I figured it out.

>2G ram & Standard Edition supported?

We have SQLServer standard edition running on a machine
with 2.2G of RAM. The sales faq appears to indicate that
SQLServer is not supported on a machine with more than 2G
of RAM. Is this the case?
Thanks,
Simon
http://www.microsoft.com/sql/howtobuy/faq.asp
Q. What is the maximum amount of RAM supported by SQL
Server 2000?
A. SQL Server 2000 Standard Edition supports up to 2
gigabytes (GB) of RAM. SQL Server 2000 Enterprise Edition
supports up to 64 GB of RAM.Simon
http://support.microsoft.com/defaul...kb;en-us;274750
"Simon Massey" <anonymous@.discussions.microsoft.com> wrote in message
news:3e9101c3e40f$4aa2c710$a301280a@.phx.gbl...

quote:

---

> We have SQLServer standard edition running on a machine
> with 2.2G of RAM. The sales faq appears to indicate that
> SQLServer is not supported on a machine with more than 2G
> of RAM. Is this the case?
> Thanks,
> Simon
> --
> http://www.microsoft.com/sql/howtobuy/faq.asp
> Q. What is the maximum amount of RAM supported by SQL
> Server 2000?
> A. SQL Server 2000 Standard Edition supports up to 2
> gigabytes (GB) of RAM. SQL Server 2000 Enterprise Edition
> supports up to 64 GB of RAM.
>

---

|||SQL Server Standard Edition is "supported" on machines with > 2GB, meaning
that MS will still give you technical support if you run it this way.
However Standard Edition only "supports" 2GB of RAM, meaning it will not use
more even if the machine has more installed.
To get SQL Server to use more than 2GB RAM you need the Enterprise Edition.
Note that the OS and other programs on that server could utilize the RAM,
like Analysis Services, Reporting Services or Notification Services.
Mike Kruchten
"Simon Massey" <anonymous@.discussions.microsoft.com> wrote in message
news:3e9101c3e40f$4aa2c710$a301280a@.phx.gbl...

quote:

---

> We have SQLServer standard edition running on a machine
> with 2.2G of RAM. The sales faq appears to indicate that
> SQLServer is not supported on a machine with more than 2G
> of RAM. Is this the case?
> Thanks,
> Simon
> --
> http://www.microsoft.com/sql/howtobuy/faq.asp
> Q. What is the maximum amount of RAM supported by SQL
> Server 2000?
> A. SQL Server 2000 Standard Edition supports up to 2
> gigabytes (GB) of RAM. SQL Server 2000 Enterprise Edition
> supports up to 64 GB of RAM.
>

---

>2G ram & Standard Edition supported?

We have SQLServer standard edition running on a machine
with 2.2G of RAM. The sales faq appears to indicate that
SQLServer is not supported on a machine with more than 2G
of RAM. Is this the case?
Thanks,
Simon
--
http://www.microsoft.com/sql/howtobuy/faq.asp
Q. What is the maximum amount of RAM supported by SQL
Server 2000?
A. SQL Server 2000 Standard Edition supports up to 2
gigabytes (GB) of RAM. SQL Server 2000 Enterprise Edition
supports up to 64 GB of RAM.Simon
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
"Simon Massey" <anonymous@.discussions.microsoft.com> wrote in message
news:3e9101c3e40f$4aa2c710$a301280a@.phx.gbl...
> We have SQLServer standard edition running on a machine
> with 2.2G of RAM. The sales faq appears to indicate that
> SQLServer is not supported on a machine with more than 2G
> of RAM. Is this the case?
> Thanks,
> Simon
> --
> http://www.microsoft.com/sql/howtobuy/faq.asp
> Q. What is the maximum amount of RAM supported by SQL
> Server 2000?
> A. SQL Server 2000 Standard Edition supports up to 2
> gigabytes (GB) of RAM. SQL Server 2000 Enterprise Edition
> supports up to 64 GB of RAM.
>|||SQL Server Standard Edition is "supported" on machines with > 2GB, meaning
that MS will still give you technical support if you run it this way.
However Standard Edition only "supports" 2GB of RAM, meaning it will not use
more even if the machine has more installed.
To get SQL Server to use more than 2GB RAM you need the Enterprise Edition.
Note that the OS and other programs on that server could utilize the RAM,
like Analysis Services, Reporting Services or Notification Services.
Mike Kruchten
"Simon Massey" <anonymous@.discussions.microsoft.com> wrote in message
news:3e9101c3e40f$4aa2c710$a301280a@.phx.gbl...
> We have SQLServer standard edition running on a machine
> with 2.2G of RAM. The sales faq appears to indicate that
> SQLServer is not supported on a machine with more than 2G
> of RAM. Is this the case?
> Thanks,
> Simon
> --
> http://www.microsoft.com/sql/howtobuy/faq.asp
> Q. What is the maximum amount of RAM supported by SQL
> Server 2000?
> A. SQL Server 2000 Standard Edition supports up to 2
> gigabytes (GB) of RAM. SQL Server 2000 Enterprise Edition
> supports up to 64 GB of RAM.
>

& in report parameter

Hi,
Using URL parameters, I pass in the following department parameter "Sales & Marketing". The problem is the "&", this causing reporting services to display an error. I assume reporting services thinks it the parameter delimiter.
I have tried URL encloding the string before I pass it in but I still get an error.
Any ideas?
ThanksWhat is the error. Passing an & is fine, and yes it must be encoded on the
URL.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"MikeMcD" <MikeMcD@.discussions.microsoft.com> wrote in message
news:B84B6DAA-93FA-44CF-9CEC-C062E1DED325@.microsoft.com...
> Hi,
> Using URL parameters, I pass in the following department parameter "Sales
& Marketing". The problem is the "&", this causing reporting services to
display an error. I assume reporting services thinks it the parameter
delimiter.
> I have tried URL encloding the string before I pass it in but I still get
an error.
> Any ideas?
> Thanks|||Yes, we need to encode the & when we pass it in the URL.
just search ur string for an & and replace it with %26.
This should work fine.
--
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.

#value in Cube Calculation

Hello all

GIven the following calculation

([Measures].[12 Month Total Sales],[Sales History].[Sales YM].[Year].lag(1))

were 12 Month Total Sales is a measure of Sale History why do I get #value for this calculation ?

Thanks for your assistance

My guess is that [Sales History].[Sales YM].[Year] is a level, and lag() only works on a member. Does this do what you want?

([Measures].[12 Month Total Sales],[Sales History].[Sales YM].currentmember.lag(1))

Chris

|||thank you