KPI design and implementation

Hi all,

I'm fairly new to analysis services and am encountering some difficulties when it comes to designing KPI's. I want these to be designed so that they may be displayed in a KPI list on Sharepoint 2007 server.

The basic premise for the simple data warehouse pilot was to present usage data for a number of customer sites split up but time etc. These sites also have a potential usage value attached to them. I'd like to implement a KPI that shows the current progress in the current month for there usage against the site's potential. A cylinder or thermometer type diagram i believe would work well to show the progress as a percentage value.

This may be to vague a description and i'm willing to elaborate further if necessary but could someone please help me understand how best to approach this?

Many thanks in advance,

Grant

Hello. First, if you have installed the SQL Server 2005 samples you will find an SSAS2005(Analysis Services) project, Adventure Works, with a lot of KPI:s in the cube editor. This is to get to know the MDX syntax for KPI:s.

To get the KPI:s to Sharepoint is not done directly. You will need a separate solution for this.

You can query and display KPI:s in Reporting Services 2005 but you will only see the values not the graphic/icons.

One option is to use Excel 2007 and construct a KPI spreadsheet report and publish it in Sharepoint. Another option is to use ProClarity Analytics platform and use their webparts for Sharepoint. Both these alternatives are not free of charge.

A third option is Microsofts Business Scorecard Server. It uses Sharepoint directly. This product and ProClarity will be included in the new Performance Point Server that will be on the market this summer.

HTH

Thomas Ivarsson

kill inactive connections

My company has a software designed in Visual Studio 6 using DAO and
ODBC, this software is opening too much connections to SQL Server and
maintaining them openned during too much time.
So, how can I kill the inactive connections using T-SQL?Hi
You should be calling the close method on the ADO connection object.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdmthclose.asp
John
"Juliano.net" wrote:
> My company has a software designed in Visual Studio 6 using DAO and
> ODBC, this software is opening too much connections to SQL Server and
> maintaining them openned during too much time.
> So, how can I kill the inactive connections using T-SQL?
>|||John, as I told you, I'm using DAO and as someone told me, connections
to ODBC are not closed when the close method of DAO classes are called.
Thanks.
Any help will be appreciated.
John Bell wrote:
> Hi
> You should be calling the close method on the ADO connection object.
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdmthclose.asp
> John
> "Juliano.net" wrote:
> > My company has a software designed in Visual Studio 6 using DAO and
> > ODBC, this software is opening too much connections to SQL Server and
> > maintaining them openned during too much time.
> >
> > So, how can I kill the inactive connections using T-SQL?
> >
> >|||Hi
I don't remember any issue with DAO connections!
Have you checked that you are actually executing the close method and
verified that the connection is not closed?
John
"Juliano.net" wrote:
> John, as I told you, I'm using DAO and as someone told me, connections
> to ODBC are not closed when the close method of DAO classes are called.
> Thanks.
> Any help will be appreciated.
>
> John Bell wrote:
> > Hi
> >
> > You should be calling the close method on the ADO connection object.
> >
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdmthclose.asp
> >
> > John
> >
> > "Juliano.net" wrote:
> >
> > > My company has a software designed in Visual Studio 6 using DAO and
> > > ODBC, this software is opening too much connections to SQL Server and
> > > maintaining them openned during too much time.
> > >
> > > So, how can I kill the inactive connections using T-SQL?
> > >
> > >
>|||John, every data access that I do on my code, I call a method to close
database connection.
John Bell wrote:
> Hi
> I don't remember any issue with DAO connections!
> Have you checked that you are actually executing the close method and
> verified that the connection is not closed?
> John
> "Juliano.net" wrote:
> > John, as I told you, I'm using DAO and as someone told me, connections
> > to ODBC are not closed when the close method of DAO classes are called.
> >
> > Thanks.
> >
> > Any help will be appreciated.
> >
> >
> > John Bell wrote:
> > > Hi
> > >
> > > You should be calling the close method on the ADO connection object.
> > >
> > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdmthclose.asp
> > >
> > > John
> > >
> > > "Juliano.net" wrote:
> > >
> > > > My company has a software designed in Visual Studio 6 using DAO and
> > > > ODBC, this software is opening too much connections to SQL Server and
> > > > maintaining them openned during too much time.
> > > >
> > > > So, how can I kill the inactive connections using T-SQL?
> > > >
> > > >
> >
> >|||Hi
If you are closing the connection after each command then you will be
creating un-necessary overhead. The session could stay open for the duration
of the users session! Also step through your code to make sure that the close
method is being executed and make sure there are traps for any exception
handling.
John
"Juliano.net" wrote:
> John, every data access that I do on my code, I call a method to close
> database connection.
>
> John Bell wrote:
> > Hi
> >
> > I don't remember any issue with DAO connections!
> >
> > Have you checked that you are actually executing the close method and
> > verified that the connection is not closed?
> >
> > John
> >
> > "Juliano.net" wrote:
> >
> > > John, as I told you, I'm using DAO and as someone told me, connections
> > > to ODBC are not closed when the close method of DAO classes are called.
> > >
> > > Thanks.
> > >
> > > Any help will be appreciated.
> > >
> > >
> > > John Bell wrote:
> > > > Hi
> > > >
> > > > You should be calling the close method on the ADO connection object.
> > > >
> > > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdmthclose.asp
> > > >
> > > > John
> > > >
> > > > "Juliano.net" wrote:
> > > >
> > > > > My company has a software designed in Visual Studio 6 using DAO and
> > > > > ODBC, this software is opening too much connections to SQL Server and
> > > > > maintaining them openned during too much time.
> > > > >
> > > > > So, how can I kill the inactive connections using T-SQL?
> > > > >
> > > > >
> > >
> > >
>