dbTalk Databases Forums  

Re: Slow MSOLAP HTTP Results

Go Back dbTalk Databases Forums Databases microsoft.public.sqlserver.olap Re: Slow MSOLAP HTTP Results

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap


Discuss Re: Slow MSOLAP HTTP Results in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Dave Wickert [MSFT]
 
Posts: n/a

Default Re: Slow MSOLAP HTTP Results - 09-02-2004 , 03:39 PM





1) verify that you have SP3 installed on the Analysis server (it is a
separate download and install from the RDBMS).
2) have you updated your client machines to use the SP3 version of PTS?
(look in the SP3 distribution \msolap\install\pts for ptslite.exe and
ptsfull.exe)
3) is your Analysis server running Windows 2003? see the following two KB
articles
http://support.microsoft.com/default...b;en-us;822652
http://support.microsoft.com/default...b;en-us;818963
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"devin" <devin (AT) discussions (DOT) microsoft.com> wrote

Quote:
I am testing MSOLAP via HTTP connections to AS to determine if it is
feasible
for my companies high performance reporting needs. So far results have
been
returning much slower than with a direct connection (30 sec. vs. 2 sec.).
All testing so far has been on the internal network.

- I have IIS running on a different server from AS. I've seen conflicting
information on MSDN about whether this is recommended. Anyone have the
definitive word?
- I've noticed that each time I submit a query, there are multiple IIS log
records (~50) showing hits to msolap.asp and the security event log on the
Analysis Server shows a similar number of logon events. Is this normal?
If
not, is there a setting that can help this apparent performance issue?
- I am running MDAC 2.7. Is this sufficient?

Any other suggestions for tuning the connection would be much appreciated.



Reply With Quote
  #2  
Old   
devin
 
Posts: n/a

Default Re: Slow MSOLAP HTTP Results - 09-10-2004 , 07:17 PM





Unfortunately this did not resolve my issue. An additional symptom of this
performance degradation is that performance improves substantially when I
change pump.ServerName in msolap.asp from an FQDN to the network name for the
same server. However, our configuration requires the ability to specify FQDN
in msolap.asp.


"Dave Wickert [MSFT]" wrote:

Quote:
1) verify that you have SP3 installed on the Analysis server (it is a
separate download and install from the RDBMS).
2) have you updated your client machines to use the SP3 version of PTS?
(look in the SP3 distribution \msolap\install\pts for ptslite.exe and
ptsfull.exe)
3) is your Analysis server running Windows 2003? see the following two KB
articles
http://support.microsoft.com/default...b;en-us;822652
http://support.microsoft.com/default...b;en-us;818963
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"devin" <devin (AT) discussions (DOT) microsoft.com> wrote in message
news:F3D6A296-0440-4BE7-943C-BA1EF5061D31 (AT) microsoft (DOT) com...
I am testing MSOLAP via HTTP connections to AS to determine if it is
feasible
for my companies high performance reporting needs. So far results have
been
returning much slower than with a direct connection (30 sec. vs. 2 sec.).
All testing so far has been on the internal network.

- I have IIS running on a different server from AS. I've seen conflicting
information on MSDN about whether this is recommended. Anyone have the
definitive word?
- I've noticed that each time I submit a query, there are multiple IIS log
records (~50) showing hits to msolap.asp and the security event log on the
Analysis Server shows a similar number of logon events. Is this normal?
If
not, is there a setting that can help this apparent performance issue?
- I am running MDAC 2.7. Is this sufficient?

Any other suggestions for tuning the connection would be much appreciated.

Reply With Quote
  #3  
Old   
Dave Wickert [MSFT]
 
Posts: n/a

Default Re: Slow MSOLAP HTTP Results - 09-11-2004 , 01:54 AM


If you are changing the server name in msolap.asp, that means that you are
separating IIS and the Analysis server. In this case, the data pump will
attempt to use named pipes. You change from a FQDN to a netbios name (or
back to FQDN) may indicate that the named pipe is using some other network
protocol; or attempting to do additional domain authentication.

If you have a PSS support contract, I would open up a case and start an
investigation into your network configuration. There isn't much that
Analysis Services can do in this case -- it just layers on-top of named
pipes.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"devin" <devin (AT) discussions (DOT) microsoft.com> wrote

Quote:
Unfortunately this did not resolve my issue. An additional symptom of
this
performance degradation is that performance improves substantially when I
change pump.ServerName in msolap.asp from an FQDN to the network name for
the
same server. However, our configuration requires the ability to specify
FQDN
in msolap.asp.


"Dave Wickert [MSFT]" wrote:

1) verify that you have SP3 installed on the Analysis server (it is a
separate download and install from the RDBMS).
2) have you updated your client machines to use the SP3 version of PTS?
(look in the SP3 distribution \msolap\install\pts for ptslite.exe and
ptsfull.exe)
3) is your Analysis server running Windows 2003? see the following two
KB
articles
http://support.microsoft.com/default...b;en-us;822652
http://support.microsoft.com/default...b;en-us;818963
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no
rights.

"devin" <devin (AT) discussions (DOT) microsoft.com> wrote in message
news:F3D6A296-0440-4BE7-943C-BA1EF5061D31 (AT) microsoft (DOT) com...
I am testing MSOLAP via HTTP connections to AS to determine if it is
feasible
for my companies high performance reporting needs. So far results
have
been
returning much slower than with a direct connection (30 sec. vs. 2
sec.).
All testing so far has been on the internal network.

- I have IIS running on a different server from AS. I've seen
conflicting
information on MSDN about whether this is recommended. Anyone have
the
definitive word?
- I've noticed that each time I submit a query, there are multiple IIS
log
records (~50) showing hits to msolap.asp and the security event log on
the
Analysis Server shows a similar number of logon events. Is this
normal?
If
not, is there a setting that can help this apparent performance issue?
- I am running MDAC 2.7. Is this sufficient?

Any other suggestions for tuning the connection would be much
appreciated.



Reply With Quote
Reply

« Previous Thread | Next Thread »



Thread Tools
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.


Contact Us - dbTalk Databases Forums - Archive - Top