My setup:
dual xeon dualcore 2.8 x64 8G RAM, SAN, Win 2003 Standard x64 , SQL2005 EE
x64 + AS 2005 x64, SP 1 + post SP1 hotfix.


I have some OLAP databses (5) installed on the AS server wich are working
good. The problem is that when I change something in one database
(role||deploy) the whole AS2005 is somehow locked!!!
The save process for a role can take up to 2-10 mins in one database and in
the mentime all other databases are locked! no query is working, no
connection with the manangement studio from other users to AS is working.
The processor is 12.5% (1 exec unit: 100%, 7exec units: 1%)

I understand that the database on wich I save the changes *can* get locked
during the process but, why the *others* databases get locked also???!!.

The settings of the server (AS) are the default one.

This is a productive system and when I change a role the whole system freeze
until the saving is finished, even if the role is made in a TestOLAPDB where
I have the only access.

Does anyone have such problems? Do you have AS2005 databases with more than
150 roles on prod. system?

Does anyone have any ideea?

Thanks,
Radu

I've installed AS2005 32 bit version on a 3.8G xeon 4G RAM and restored the
OLAP database.

There changing/saving a role takes 3sec!!!! On the 64 bit maschine 2 mins!!!

What can it be ?

Thanks, Radu



"Radu Colceriu" <radu_colceriu (AT) hotmail (DOT) com> wrote

does the system takes the same time if the 2 servers have a cold cache?
have you somebody connected or active sessions on the server?

to test, stop the service, start it, apply your new security and verify the
time taken. (stopping the service will insure you that nobody and nothing is
in the cache)



"Radu Colceriu" <radu_colceriu (AT) hotmail (DOT) com> wrote

Can you check on both 32-bit and 64-bit, what is the size of the file
master.vmp in the data folder?

I've seen one or two situations where this file becomes very large and
causes an unexpected slowdown during Commit -- perhaps on x64 something
worsens the problem...

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Jéjé" <willgart_A_ (AT) hotmail_A_ (DOT) com> wrote

Hi,

@Jeje: no it's not a cold cache thing.... the query times are ok. Only the
management is slow. It is looking like a looking or something.

@Akshai : on the 32 bit the mvp is 1M and on 64 bit is 2.5M. On both servers
I'm the only one accessing it. (not live yet).

What is strange is that on the 64bit in the Data directory I have o lot of
..tmp file like ({uuid}.tmp and {uuid}.sbmp.tmp) and I cannot delete them
even with the AS service stopped.

Any ideeas?
Thanks,
Radu

P.S. I will try in the next days to reinstall the AS ... hope I get no
problems with the uninstall 'cause SQL2005 is working wonderful.





"Akshai Mirchandani [MS]" <akshaim (AT) online (DOT) microsoft.com> wrote

the question is not cold cache and warm cache during query time.
the question is:
when you apply your security does the cache is warm or cold?

do this:
save the script which apply the security into an XMLA script
stop both servers 32bits and 64bits
start both servers
run your XMLA script on both server
how many time the XMLA command takes on both servers?


"Radu Colceriu" <radu_colceriu (AT) hotmail (DOT) com> wrote

Hi Jeje,

I've tried what you have suggested and there is no difference:

I saved the create role XMLA on both servers then I restarted the AS
services (actually restarted the srv) , connected (taked +2-3sec) with
management studio and then executed the scripts.

the 32 bit: 4 sec
the 64 bit 1:49

the OLAP databses were restored from the same backup file
the OLAP databases access the same SQL2005
both servers are on the same array with diffrernt LUNs
i am the only user in the system

I'm really confused an I presume there is some screwed up installation or
the AS have some issues with dual dual-core xeon x64.

I appreciate your involvement,
Thanks,

Radu



"Jéjé" <willgart_A_ (AT) hotmail_A_ (DOT) com> wrote

I think you should try this (but be very careful because this is not really
a recommended action):
- Stop the Analysis Server
- Rename the data folder you have: <installpath>\data to
<installpath>\data_backup
- Restart the server
- A new data folder should have been created at <installpath>\data
- Restore the backup of the database
- Try the operation again

I believe that what has happened is that your master version map has somehow
gotten filled with lots of object versions. AS uses the DOM in MSXML to
access this file and I believe the size of this file could be contributing
to the poor performance of the commit operation.

Starting from an empty data folder should show if this theory is true for
you. I also have some suspicions that the x64 DOM is for some reason slower
than the x86 DOM but I haven't seen any real evidence of this yet...

It should be possible to delete these files once the server is stopped -- I
would check to see which process is holding handles to them (you can
download a tool from sysinternals called Handle which lets you determine
this):
http://www.sysinternals.com/Utilities/Handle.html

It may turn out that you have another process like an anti-virus or
something like that causing interference on the data folder -- and perhaps
causing Commit to also slow down...

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Radu Colceriu" <radu_colceriu (AT) hotmail (DOT) com> wrote

Hallo Akshai ,

Thanks for the hints.

I will try tommorow renaming the data folder and then let you know how it
was working.

The deleting of the temp files was somehow strange. I was connected with
remotedesktop with an user with administrator rights on the server (after
server restart and as2005 service not started) and I could not delete the
files O.O. I got a message like write protected / disk full / used by other
process. Then I've connected with \\srvname\d$\data... and I could delete
them.... Anyway deleting the temp file did not solve the performance
problem.


Thanks,
Radu

"Akshai Mirchandani [MS]" <akshaim (AT) online (DOT) microsoft.com> wrote

Hello Akshai,


I've tested with your suggestions: renamed that data dir, started the as
service and then restored the databases. I've got an improvement of about 3
sec in role creation (from 1:48)

Anyway using your suggestion I've discovered something very interesting.
I have 6 OLAP databases on the server. One of them is called "MIS" and the
other "PROV". When I delete this 2 databases I got a role creation time of
approx 5 sec which is more than ok .
When I restore the "PROV" i got approx 20 sec.
When I restore the MIS i got 1:43 .

The role creation thake place on another database (not MIS and not PROV)

The MIS db is approx 1.8G, has around 10 cubes, and 16 dims and around 250
roles. The odd thing is that a lot of the dimensions are parent-child (AS
2000 db maanually ported to AS2005).

The PROV db has 3 cubes and 5 dimensions and is arround 800M with arounf 150
roles. The dimensions are not parent-child.

We are in the process of completlly rebuilding the MIS db but not the PROV.

Any suggestions/ideeas?
Thanks,
Radu

P.S. our dev. server is a single xeon 3.8 4G ram (win x64 , sql x86) and the
prod. server is dual dualcore-xeon 2.8 G 8G Ram (win x64, sql x64). What I
have seen is that the dev server is *faster* than the prod server even if I
am the only user on both!.

so GHz > MultiCPU?





"Akshai Mirchandani [MS]" <akshaim (AT) online (DOT) microsoft.com> wrote