ProClarity - active vs static presentation

Hi,

When I export the reports in my book to powerpoint, the presentation become actice. How do I change this to a static one?

Hello! The export wizard is designed for interactivity with the cube. I do not think that this is a feature that will be supported in ProClarity's last release(6.3)

Copy/Paste or Screendumps from ProClarity Professional to Powerpoint can work.

You can export from ProClarity's thin web client to Excel and Outlook but I am not sure about the export to PowerPoint.

HTH

Thomas Ivarsson

Processor Upgrade on a sql cluster

In our environment we have a cluster active standby with a shared storage
iscsi
The two machines are Windows 2000 Advanced Server with Intel Xeon
Single-Core 3.4Ghz with SQL Server 2000
Enterprise Edition.
Now we want to sustitute these two with another two machines with
Dual Intel Xeon Dual-Core 3.6Ghz
We want to clone the actual machines in the new environment cause we want a
current machine for disaster recovery and cause we want also to test the
disaster recovery plan...
1) the two new dual core processors are view from operating system as a four
processor is this configuration supported with the environment Windows 2000
Advanced Server and SQL 2000 Server Enterprise Edition ?
2)when we have transferred the disk and the configuration and the boot is ok
and sql services are started what tuning and best practice we have to apply
for the new environment for tuning performance with new dual vs single cpu
node
Hi Davide,
1) Yes, you can manage 4 processors with these licenses.
2) We need more information about your environment to answer this. Generally
speaking, you should take care of CPU affinity and IO affinity, and take a
look at your files and filegroups configurations, especially on tempdb
database
Regards
Antonio Soto
Solid Quality Leaning
http://www.solidqualitylearning.com
DISCLAIMER:
Anything written in this message represents solely the point of view of the
sender. This message does not imply endorsement from Solid Quality Learning,
and it does not represent the point of view of Solid Quality Learning or any
other person, company or institution mentioned in this message
"Dr Davide BOmbarda" <DrDavideBOmbarda@.discussions.microsoft.com> escribi
en el mensaje news:CC20F619-9ED5-4CBB-BA62-B23AF4B2C75B@.microsoft.com...
> In our environment we have a cluster active standby with a shared storage
> iscsi
> The two machines are Windows 2000 Advanced Server with Intel Xeon
> Single-Core 3.4Ghz with SQL Server 2000
> Enterprise Edition.
> Now we want to sustitute these two with another two machines with
> Dual Intel Xeon Dual-Core 3.6Ghz
> We want to clone the actual machines in the new environment cause we want
> a
> current machine for disaster recovery and cause we want also to test the
> disaster recovery plan...
> 1) the two new dual core processors are view from operating system as a
> four
> processor is this configuration supported with the environment Windows
> 2000
> Advanced Server and SQL 2000 Server Enterprise Edition ?
> 2)when we have transferred the disk and the configuration and the boot is
> ok
> and sql services are started what tuning and best practice we have to
> apply
> for the new environment for tuning performance with new dual vs single cpu
> node
>
>
|||I/O affinity only comes into play with the Datacenter Edition when working
with specific SAN configurations. Even then, you need to be pushing the I/O
channel pretty hard to even see any effect.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Antonio Soto" <antoniosotorodriguez@.gmail.com> wrote in message
news:umQqsqpKGHA.3896@.TK2MSFTNGP15.phx.gbl...
> Hi Davide,
> 1) Yes, you can manage 4 processors with these licenses.
> 2) We need more information about your environment to answer this.
> Generally speaking, you should take care of CPU affinity and IO affinity,
> and take a look at your files and filegroups configurations, especially on
> tempdb database
> Regards
> Antonio Soto
> Solid Quality Leaning
> http://www.solidqualitylearning.com
> DISCLAIMER:
> Anything written in this message represents solely the point of view of
> the sender. This message does not imply endorsement from Solid Quality
> Learning, and it does not represent the point of view of Solid Quality
> Learning or any other person, company or institution mentioned in this
> message
>
>
> "Dr Davide BOmbarda" <DrDavideBOmbarda@.discussions.microsoft.com> escribi
> en el mensaje news:CC20F619-9ED5-4CBB-BA62-B23AF4B2C75B@.microsoft.com...
>

Processing OLAP Cube causes OLAP and SQL to shut down

Here's a situation I ran in recently, and I'm trying to discover root cause.
I should mention this was occuring on a active/active two-node cluster w/ 6
instances of SQL running on it. The OLAP service in question was tied to th
e
SQL Server service as part of the same cluster group.
I had a cube in OLAP I was attempting to process, but each time I tried the
OLAP service and the SQL Server Service that OLAP was using as a data source
would shut down and fail over to another cluster node. This would
continually happen each time we would try to process the cube - it would fai
l
over back and forth to the two nodes on the cluster.
Finally when we manually took the cluster group down and brought it back up,
everything stabilized. Not sure why this smoothed things out as the SQL
Server instance and the OLAP service had been on the correct node before, bu
t
now that we had moved the instance manually, everything was fine.
My only guess as to root cause was contention for resources. Does anybody
else have any ideas? Again, the problem I'm trying to understand is why
processing a cube will cause a SQL Server and OLAP instance to shut down.
Thanks in advance.Yes! Resource contention. If you are trying to run 6 instances of SQL
Server and at least 1 Analysis Services server on only a two node cluster,
you most assuradely have resource contention and it is called MEMORY, which,
too, is most assuradely used during the building of the cube.
How much memory are you running on those two nodes? What is the MAX SERVER
MEMORY configuration set to on each of the instances? What is the setting
for the source of the OLAP cube? Anything short of about 512 MB to 1 GB for
each instances, plus about 1 GB for the Analysis Services, is under capacity
for any real use production system.
Do you have 6 to 12 or so GB on EACH node?
Sincerely,
Anthony Thomas
"TX_KniveS" <TX_KniveS@.discussions.microsoft.com> wrote in message
news:9C541BA2-E1B4-46C8-8F1D-3D1D145A622C@.microsoft.com...
Here's a situation I ran in recently, and I'm trying to discover root cause.
I should mention this was occuring on a active/active two-node cluster w/ 6
instances of SQL running on it. The OLAP service in question was tied to
the
SQL Server service as part of the same cluster group.
I had a cube in OLAP I was attempting to process, but each time I tried the
OLAP service and the SQL Server Service that OLAP was using as a data source
would shut down and fail over to another cluster node. This would
continually happen each time we would try to process the cube - it would
fail
over back and forth to the two nodes on the cluster.
Finally when we manually took the cluster group down and brought it back up,
everything stabilized. Not sure why this smoothed things out as the SQL
Server instance and the OLAP service had been on the correct node before,
but
now that we had moved the instance manually, everything was fine.
My only guess as to root cause was contention for resources. Does anybody
else have any ideas? Again, the problem I'm trying to understand is why
processing a cube will cause a SQL Server and OLAP instance to shut down.
Thanks in advance.

Processing OLAP Cube causes OLAP and SQL to shut down

Here's a situation I ran in recently, and I'm trying to discover root cause.
I should mention this was occuring on a active/active two-node cluster w/ 6
instances of SQL running on it. The OLAP service in question was tied to the
SQL Server service as part of the same cluster group.
I had a cube in OLAP I was attempting to process, but each time I tried the
OLAP service and the SQL Server Service that OLAP was using as a data source
would shut down and fail over to another cluster node. This would
continually happen each time we would try to process the cube - it would fail
over back and forth to the two nodes on the cluster.
Finally when we manually took the cluster group down and brought it back up,
everything stabilized. Not sure why this smoothed things out as the SQL
Server instance and the OLAP service had been on the correct node before, but
now that we had moved the instance manually, everything was fine.
My only guess as to root cause was contention for resources. Does anybody
else have any ideas? Again, the problem I'm trying to understand is why
processing a cube will cause a SQL Server and OLAP instance to shut down.
Thanks in advance.Yes! Resource contention. If you are trying to run 6 instances of SQL
Server and at least 1 Analysis Services server on only a two node cluster,
you most assuradely have resource contention and it is called MEMORY, which,
too, is most assuradely used during the building of the cube.
How much memory are you running on those two nodes? What is the MAX SERVER
MEMORY configuration set to on each of the instances? What is the setting
for the source of the OLAP cube? Anything short of about 512 MB to 1 GB for
each instances, plus about 1 GB for the Analysis Services, is under capacity
for any real use production system.
Do you have 6 to 12 or so GB on EACH node?
Sincerely,
Anthony Thomas
"TX_KniveS" <TX_KniveS@.discussions.microsoft.com> wrote in message
news:9C541BA2-E1B4-46C8-8F1D-3D1D145A622C@.microsoft.com...
Here's a situation I ran in recently, and I'm trying to discover root cause.
I should mention this was occuring on a active/active two-node cluster w/ 6
instances of SQL running on it. The OLAP service in question was tied to
the
SQL Server service as part of the same cluster group.
I had a cube in OLAP I was attempting to process, but each time I tried the
OLAP service and the SQL Server Service that OLAP was using as a data source
would shut down and fail over to another cluster node. This would
continually happen each time we would try to process the cube - it would
fail
over back and forth to the two nodes on the cluster.
Finally when we manually took the cluster group down and brought it back up,
everything stabilized. Not sure why this smoothed things out as the SQL
Server instance and the OLAP service had been on the correct node before,
but
now that we had moved the instance manually, everything was fine.
My only guess as to root cause was contention for resources. Does anybody
else have any ideas? Again, the problem I'm trying to understand is why
processing a cube will cause a SQL Server and OLAP instance to shut down.
Thanks in advance.