Yes and no. When you process an dimension or partition, the system issues
SQL statements on your behalf to build the MOLAP structures. Like any SQL
statement those will place read-locks on the host database; either table or
row-level locks depending on the lock escalation process taken on the RDBMS.
When it is done, AS closes out the connection. Unfortunately since
connection pooling is used automatically, this can result in open
connections remaining to the RDBMS which means that the read locks may still
be present. Might this be what you are seeing? This is pretty easy to see
using SQL Server; just fire up SQL Profiler, restart the msmdsrv service
(which will clear out any existing connections), and start your processing.
Within Profiler you will see connections being openned; SQL statements being
issued; and then the long wait for connection pooling to ultimately timeout
and have the db connection finally go away.

--
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.

"Wendell G." <WendellG (AT) discussions (DOT) microsoft.com> wrote