Is the PTS cache per-thread or shared between threads?

Does it make a difference if the threads are in STA?

If a VB6 component uses ADOMD to access an OLAP source from a multi-threaded
(STA) environment (e.g. IIS, or an ActiveX EXE), each of the threads will
have their own OLAP connection. Does this mean that the cache is independent
for each thread, and that memory usage is therefore not optimal?

If the connection string specifies a "Client Cache Size" setting, it that
honoured per-thread or per-process?

Tony Proctor

Just in case anyone falls across this in the archives...

PTS caches appear to be connection-specific.

In an IIS environment, where each thread is likely to have its own
connection, then this means that there is a multiplicity of caches for the
same data, and an ASP application (for instance) becomes starved of useful
memory.

Furthermore, MS acknowledge that PTS is designed for two-tier architectures,
not three-tier. In fact, there's some debate about whether it's even
supported in a middle tier. Since both ADOMD and XML/A access to OLAP data
utilise PTS then this has severe repercussions for any application trying to
provide analytical capabilities in a middle tier.

.....this is what OLAP is all about, not just showing grids on a client!

"Tony Proctor" wrote: