Re: HELP I am about to quit on AS2005
- From: "Peter de Heer" <peter@xxxxx>
- Date: Wed, 17 Jan 2007 10:21:43 +0100
Hi Deepak,
Thanks for replying.
"Deepak Puri" <deepak_puri@xxxxxxxxxxxxxxx> wrote in message
news:OjU0RfZOHHA.2312@xxxxxxxxxxxxxxxxxxxxxxx
Hi Peter,
Since your list of gripes is rather expansive, below are the responses
that readily come to mind. But if you haven't taken an SSAS class or
read a book, the learning curve's going to be harder to negotiate:
* I miss 'reverse engeneer' functinality for a deployed solution, so it
can
me modified and/or learned from. This is a basic feature in all design
software, so why not here?
http://msdn2.microsoft.com/en-us/library/ms365361.aspx
SQL Server 2005 Books Online
How to: Create an Analysis Services Project Based on an Existing
Analysis Services Database
New: 14 April 2006
You can create a new project in Business Intelligence Development Studio
by using the Import Analysis Services 9.0 Database template. Creating a
new project by using the Import Analysis Services 9.0 Database template
creates a project containing all of the objects in the existing Analysis
Services 9.0 Database. These objects can then be modified within the
project, without immediately affecting the existing database, and the
modified object in the project can then be deployed to the same Analysis
Services database or to a newly created Analysis Services database for
comparison testing.
..
This functionality is not where I expected and implicitly limited in use
compared to what I am used to. I do welcome it tho and will try using it.
What I would have expected was an ability to add to an existing project
parts of an already deployed solution.
* The graphical representation of tables (with interconnecting lines) in
VS2005 is a joke. Try to arrange tables in a logical manner with
straight
lines. There is an auto layout function I found, but I find it all to
work
very unnatural and it usualy ends up doing unintended things such as
forcing
loops instead of a staight line where even a child can see what my
intenton
is.
http://msdn2.microsoft.com/en-us/library/ms174848.aspx
SQL Server 2005 Books Online
Working with Diagrams in a Data Source View (Analysis Services)
..
To reduce the visual clutter when you only want to view a subset of the
tables in the data source view, you can define sub-diagrams (simply
called diagrams) consisting of selected subsets of the tables, views,
and named queries in the data source view. You can use diagrams to group
items in the data source view according to business or solution needs.
You can group related tables and named queries in separate diagrams for
business purposes, and to make it easier to understand a data source
view that contains many tables, views, and named queries. The same table
or named query can be included in multiple diagrams except for the <All
Tables> diagram. In the <All Tables> diagram, all objects that are
contained in the data source view are shown exactly once.
..
This I am aware of this, but why even bother adding manual 'layouting' in a
crappy and frustrating way when they only thing to gets things close to
presentable is the auto layout function. In addition to this why 'hide' is
in a menu when the contect sensitive menu is next to empty?
* Attributes that do not form a hierarchy (even if one level), cannot be
put
on any of the axes in an MDX query. They can be presented using
properties,
but not in a way that allows reporting. For base tables this is pretty
wasteful and an unnececary restriction.
When you need to place an attribute on MDX query axes, why wouldn't you
enable its attribute hierarchy? The need for .Properties() should be
greatly reduced:
Because it is the most compact form to store data?
Because it does not require pre-determined sorting?
Because it is the most natuaral to what is being modelled?
Just because something that is not agreggated (different property) and not
Indexed the way hierarchies are doesnt mean they should not be placable on
an axis. Let alone that there is no need to incorporate a 'properties'
construct to access these fields. Just a 'Key.attributename' would have
sufficed!
So yeah, the properties function has no reason to exist, but that doesn't
mean properties don't or that they need to be so limited in use. I will look
deeper into the membervalue option, even tho I suspect it will force me to
create 'bloated' hierarchies where none is conceptualy needed.
http://sqljunkies.com/WebLog/mosha/archive/2005/10/11/mdx_functions_as20
05.aspx
MDX functions in Analysis Services 2005
..
Bad/Deprecated functions
Some functions are supported by AS2005 for backward compatibility
purposes, but either deprecated (which means that they could be removed
in the future release) or simply bad to use. The worst offenders are
listed below
..
Properties
Use of .Properties should be avoided as much as possible. Filtering by
member properties should be rewritten by using CrossJoin (or Exists).
Lookups should be rewritten by using related attributes and
MemberValue. There are very few reasons to use .Properties.
..
- Deepak
Deepak Puri
Microsoft MVP - SQL Server
*** Sent via Developersdex http://www.developersdex.com ***
.
- References:
- Re: HELP I am about to quit on AS2005
- From: Peter de Heer
- Re: HELP I am about to quit on AS2005
- From: Deepak Puri
- Re: HELP I am about to quit on AS2005
- Prev by Date: Re: Newbie Question on Measures
- Next by Date: newbie question re many-to-many fact modelling
- Previous by thread: Re: HELP I am about to quit on AS2005
- Next by thread: Re: Why does SQL management studio keep "locking up"?
- Index(es):
Relevant Pages
|
