Hi,

Can any one working and using Yukon AS2005 have felt any limitations of
AS2005 compared to the features in AS2000.

Regards,
Prasanna

I think it's still too early to say, some functionality has changed quite
significantly since the June CTP and is still changing so any criticisms made
now might not be valid at RTM. Also, it's very easy to think something's
worse just because it forces you to work in a different way to how you're
used to: for example when I first started using Business Intelligence
Developer Studio (with its need to deploy changes after you've made them) I
used to prefer Analysis Manager, but now I'm used to it I wouldn't go back.

Chris

--
Blog at:
http://spaces.msn.com/members/cwebbbi/


"pras" wrote:

Only true when you work in the Project mode. I, personally, prefer to work
in Online mode, where any changes you make are saved directly to the
server - this is closer model to what Analysis Manager provided.

--
==============================*=================== =
Mosha Pasumansky - http://www.mosha.com/msolap
Analysis Services blog at http://www.sqljunkies.com/WebL*og/mosha
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==============================*=================== =

Hi,
Thanks for the response.
Yes AS2005 has very good features compared to AS2000.
I have some below queries need to answered.

1. Since AS2005 doesn't support DSO. if i need to create dynamic
partitions how
should i go about.
2. Earlier cube could have been archived with upto 2 GB of data so
anyone could
analyze.Now with AS2005 one has to deploy first and then process
the data then only
one can analyze the data.
3. I am not convinced well with Proactive caching what advantages you
get with it the cubes in hand is it olny for processing the data or
will it help in querying also.
4. The browser ships with BI Studio what is the maximum capacity till
it works fine

I may still have some more queries which i will post it later

Regards,
Prasanna

Well, I think that Mosha described some options which would minimize the
AS 2005 drillthrough impact for users:

- Hide the degenerate dimension, so they don't see it

- No performance impact, when not accessing it

So, the only "overhead" that I can see is your own learning curve -
users can still use MDX DrillThrough statement, with configurable fields
returned, as in AS 2000. But if you find this overhead greater than that
for building a bespoke app, you can certainly choose the latter.


- Deepak

Deepak Puri
Microsoft MVP - SQL Server

*** Sent via Developersdex http://www.developersdex.com ***

Hi,
i was building a dimension for product using Adventure Works DW
database.


Steps i followed are
1. Dim product as main table for the Product table for the standard
dimension.
2. Selected productkey as the main key


3. Selected DimProductCategory, DimProductSubCategory the related
tables.


4. Selected Attributes


a. English product Category name
b. English Product Sub Category name
c. English product name
d. Color
e. Style
f. Weight


5. Selected dimension type as regular


6. No parent child relation ship specified as it is standard
dimension


7. Next Pane Dimension contains no hierarchies


8. Named the dimension as Product, Click finish


9. Created product hierarchy containing
a. product Category (renamed from "English
product"Category name)
b. Product SubCategroy (rename from English Product Sub
Category name)
c. Product name (renamed from English product name)


10. process the dimension


11. It is giving me series of errors
a. The following system error occurred: No mapping between
account names and security IDs was done.


( I COULD NOT really understand what it is speaking of)


b. Errors in the high-level relational engine. A connection
could not be made to the data source with the DataSourceID
of 'Adventure Works DW', Name of ''.


( I HAVE CREATED DATASOURCE 'Adventure Works DW' allready)


c. Errors in the OLAP storage engine: An error occurred while
the dimension, with the ID of 'Dim Product', Name of 'Dim
Product' was being processed.


d. Errors in the OLAP storage engine: An error occurred while
the 'English Product Name' attribute of the 'Dim Product'
dimension from the 'Analysis Services Project2' database
was being processed.
e. Errors in the OLAP storage engine: An error occurred while
the 'Color' attribute of the 'Dim Product' dimension from
the 'Analysis Services Project2' database was being
processed.
f. Errors in the OLAP storage engine: An error occurred while
the 'Weight' attribute of the 'Dim Product' dimension from
the 'Analysis Services Project2' database was being
processed.


i could not understand what are all these errors


Can any one explain what is the simple mistake which has happened


Regards,
Prasanna

The simple answer for this. Right click the data source Open and in the

Impersonation information select the radio button " use the service
account". this might be beacuse the Olapservice runs under Local
System account


Regards,
Prasanna