Re: crash on virtual dimensions
aaron_kempf_at_hotmail.com
Date: 12/21/04
- Next message: John Tai: "connection pooling in xmla"
- Previous message: Peter Yang [MSFT]: "Re: STDEV aggregate from fact table"
- In reply to: Mosha Pasumansky [MS]: "Re: crash on virtual dimensions"
- Next in thread: aaron_kempf_at_hotmail.com: "Re: crash on virtual dimensions"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 20 Dec 2004 17:57:49 -0800
SQL authentication doesn't work for SQL Server to anywhere. it just isn't
functional-- because it isn't secure.
it isn't secure-- people chew me out for wanting to use it. this product
has been out 4 years.. can't you fix it??
i just wish that you guys woudl fix it-- make it so that it is secure.
i've worked in a lot of environs-- like novell-- and SQL authentication is
just SOOOOOO Much easier to use than NT authentication.
ADP (access data projects) are the best product that MS has ever put out..
I've developed dozens of them.. And it is _REALLY_ buggy.
It is basically a way for access developers to start writing all of their
queries on the SQL side.. it is very important.. and it is very powerful.
I swear that every beancounter in the world should be developing their
reports in ADP; but somehow it's not getting traction.
I swear the product is buggy-- i have a whole list-- but it's like they're
not taking me seriously.
i've worked with as400/RPG developers; and I've seen the pain that they go
thru in order to create forms and reports against a database. that's all im
talking about.. a simple platform for Small and Medium Businesses to enter
data into a database. It is maybe scalable enoug to go to 50 or 100 users;
and it is fast (if written correctly)
ADP is that same market. It is critically important. Just a simple
mechanism for getting data into the database (bound SQL Server platform) and
pulling it out via reporting.
it is about 10x more powerful than reporting services.. but it is really
buggy.. and i'm tired of hearing excuses about why it is buggy; and when it
is getting fixed.
I can't get anyone in the Office dept to fix problems i find.. and I've
encountered the create proc bug every day. My co-workers make sprocs using
the create proc syntax.. and it just craps out on me when i go to use it in
ADP.
It's like-- if i create proc with create proc or create procedure-- it
should work either way.
I just love usign ADP for reporting; and it breaks my heart that you guys
aren't taking it seriously-- i assume that is because you guys think that RS
is going to replace Access Reporting.. and I dont' know if that is going to
happen.
"Mosha Pasumansky [MS]" <moshap@online.microsoft.com> wrote in message
news:eNx4eft5EHA.3504@TK2MSFTNGP12.phx.gbl...
> Aaron, I tried to address your comments below:
>
> > But you guys can't honestly believe that this Analysis Manager is
bugfree.
> > It is barely usable.
>
> We don't beleive it is absolutely bug free. But I disagree with your
> assertion that it is barely usable.
>
> > I just want to know why you guys ship products without testing.
> > I want to know why you guys can't fix bugs. I want to know why you
guys
> > don't stumble into these sort of usability issusses.. You guys don't
TEST
> > YOUR PRODUCTS ENOUGH.
>
> I think it is unfair to say that we ship products without testing. I
agree,
> that perhaps some areas are not tested enough. However we can and do fix
> bugs - either in service packs (BTW Beta of SP4 is about to come out) or
> out-of-band as hotfixes.
>
> > Use them in real-world scenarios...
>
> We now have special team inside SQL BI organization, which has single
> purpose - use BI products in the real-world scenarios. This team is
> different from the test organization in a sense that it doesn't test
> specific features - it uses the product the way customers would use it and
> see whether it works as a whole. I think this is exactly what you are
> refering to.
>
> > A:) WHEN YOU CHANGE A DATASOURCE, IT DOESN'T CHANGE THE LABEL. IN
ANALYSIS
> > MANAGER. YOU SETUP A CUBE BASED ON A SERVER NAMED HOXOOCAARKEM AND THEN
> YOU
> > GO TO CHANGE IT TO PRODSQL1-- THE LABEL DOESN'T CHANGE. The datasource
> was
> > changed to point to PRODSQL1, but the label still says 'HOXOOCAARKEM'.
> I've
> > bitched about this in a hundred different places; and never heard a
REASON
> > that Microsoft can't grace us with a product that works.
>
> I agree that this is very annoying. The reason is that design of DSO and
> repository schema fundamentally doesn't allow object renaming, because
names
> are used as keys. So it is not really possible to fix in AS2K. In AS2005
> however, we introduced to every object name and id - and name can change
as
> many times as you want, because id is the real key.
>
> > WHATEVER HAPPENED TO THE QUALITY OF YOUR PRODUCTS?
> > I love OLAP and SQL Server more than anything else in the world-- i just
> > think that you guys are letting your guard down; and I wish that you
guys
> > would start taking this seriously. MY CAREER IS TIED TO YOUR QUALITY DB
> > PRODUCTS AND YOU GUYS AREN'T TAKING THIS SERIOUSLY.
>
> I feel your pain - and I do want to assure you, that we are not letting
the
> guard down, and we do take the quality of the products seriously. What you
> described above, however, is not a product defect, but rather design
> limitation, which, while annoying, doesn't take away functionality, i.e.
you
> can change the datasource, just not its name.
>
> > B:) Can't you make a driver that won't let itself get overwritten??
Can't
> > you include OLAP drivers via Windows Update, or something???
> > Upgrading 50k desktops to Office 2003 isn't an option.
>
> We cannot put msolap80.dll to the Windows Update, because it is not part
of
> Windows. However we do make both ptslite.exe and ptsfull.exe freely
> available on microsoft.com, and they are there exactly for this purpose -
> being able to distrubute OLAP drivers without installing Office 2003.
>
> > Why is it that you guys can't create a stand-alone client.. Where if
> someone
> > needs AM on thier machine, they could just run the AM install; instead
of
> > needing to run AM install and then SQL AS SP3-- that is just a joke.
Make
> > one installer; that installs the products-- instead of having to confuse
> > developers.
>
> I am not sure I got this point: Do you suggest that we produce new setup
> which will install SP4 directly, instead of first running RTM version of
> setup and then applying SP4 on top of it ?
>
> > B.5) You guys need to start allowig OWC downloads in one place:
> > www.microsoft.com/owc You can't drop XP downloads of OWC just because
you
> > want to sell 2003. I HONESTLY can't find the download anywhere. I
> finally
> > found the correct version via Office XP SP3-- but I don't think that an
> > end-user could do that. It's not OUR fault that you guys are greedy and
> are
> > coming out with too many versions of Office. But Office 2002 isn't 2
> years
> > old; and you guys aren't supporting it basically.
>
> I have forwarded your feedback to the Office team.
>
> > C). I DEMAND-- I DEMAND-- THE ABILITY TO USE OLAP IN ACCESS REPORTS.
RS
> > ISN'T SOLVING PROBLEMS. RS SUCKS. ALLOW ACCESS MDB AND ADP TO CONSUME
> MD
> > DATASETS. Make some wizards for doing it, or somethign. an add-in..
> > anything.
>
> Sorry, I don't know what ADP is. Alternative solution to "RS SUCKS"
problem
> would be to fix RS. Perhaps you can tell us what are the problems with RS
> and we will see how they can be addressed. I suggest you do it in a
separate
> post and copy microsoft.public.sqlserver.reportingsvcs newsgroup as well.
>
> > D). ARE THERE _REALLY_ SYNTAX DIFFERENCES BETWEEN MDX IN RS AND MDX VIA
> 'Mdx
> > Sample Application'. I swear; I've seen MDX work in MDX sample
> application;
> > but not in RS-- Is this true, Why is it true; and why do you guys put up
> > with this??
>
> There are no syntax differences in MDX between MDX Sample application and
> RS, but there is a difference in a way those two application request a
> result. MDX Sample works with MDDataSet, while RS requests flattened
rowset.
> So the same MDX statement should work in both, just the way the results
look
> will be different. It is possible, that if you put too many members on
> COLUMNS axis, RS is not able to deal with it though.
>
> > E). Can't you make SQL2005 able to browse SQL2000 cubes? WE DESERVE A
> DECENT
> > IDE FOR WRITING MDX
>
> Well, the AS2005 OLAP driver is able to connect and work against AS2K
cubes,
> so I interpret your question as making AS2005 IDEs to connect and manage
> AS2K cubes. For BI Development Studio this would be close to impossible to
> do, since it relies on new Yukon DDL for metadata operations which isn't
> available in AS2K
>
> > F). WHAT IS UP WITH ACCESS ADP? SOMEONE SAID IT IS BEING DEPECRATED--
IT
> IS
> > BUGGY AS HELL. TRY THIS:
>
> Again, I don't know what ADP is, but I assume that this is something in
> Access. You probably need to tell about those bugs in Access newsgroup.
>
> > FIX SQL AUTHENTICATION IN SQL2000. FIX IT RIGHT NOW. PROTECT IT. SECURE
> IT.
> > WINDOWS AUTHENTICATION _SUX_ FOR A LOT OF THINGS; AND I AM SICK AND
TIRED
> OF
> > NOT HAVING A DECENT, SECURE WAY TO GET TO MY DATA.
>
> Not sure what this refers to. Are you saying that there is a problem with
> SQL Authentication in SQL Server 2000, or are you saying that it is a
> problem that Analyisis Services only supports Windows Authentication ?
>
> Thanks,
> Mosha.
>
> --
> ==================================================
> Mosha Pasumansky - http://www.mosha.com/msolap
> Analysis Services blog at http://www.sqljunkies.com/WebLog/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.
> ==================================================
>
>
- Next message: John Tai: "connection pooling in xmla"
- Previous message: Peter Yang [MSFT]: "Re: STDEV aggregate from fact table"
- In reply to: Mosha Pasumansky [MS]: "Re: crash on virtual dimensions"
- Next in thread: aaron_kempf_at_hotmail.com: "Re: crash on virtual dimensions"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
