Performance Point : Programmatically Create a new Scorecard


Working with PPS programmatically requires an understanding on the PPS Web Services

Below is the first blog entry to help other on working with PPS programatically to do some actions

void CreateScoreCard ()

    {

        Scorecard scorecard = new Scorecard();

        scorecard.Guid = Guid.NewGuid();

  /////////Even the following Lines are optional,

  ///If you didn’t enter a name for the scorecard it will be created with an empty name

        BpmPropertyText NameProperty = new BpmPropertyText();

        NameProperty.Text = "The ScoreCard";

        scorecard.Name = NameProperty;

        //To publish the scorecard on the server

        Publisher.CreateScorecard(scorecard);

    }

kick it on DotNetKicks.com

Upgrade SharePoint SQL Express to Standard or Enterprise


Source : Todd Klindt’s SharePoint Admin Blog

Microsoft so very graciously provides a free version of SQL 2005, SQL Express, with MOSS. If you install MOSS using the Basic option or Single Server under Advanced you get SQL Express automatically. So what if as a budding newbie SharePoint admin you chose the Basic option, but now as a wise aged SharePoint admin you’ve seen the error of your ways and want to use a more respectable version of SQL for your SharePoint backend? You’re in luck. In this blog post I’ll walk you through upgrading SQL Express to SQL Standard or Enterprise.

First thing you need to do is get a copy of SQL 2005 Standard or Enterprise. Which version you choose depends on the redundancy and availability you want. Either will upgrade from Express. After you have your media you can start the install. This step is important as you have to pass the setup program a parameter to let it know you’re doing an upgrade. To upgrade use the command setup.exe SKUUPGRADE=1. It should look like this:

The setup should kick off and it won’t give you any indication that you passed it a parameter. Never fear, it will come up later. When the setup gets to the instance selection make sure you don’t accept the default instance and you choose the SQL Express instance. First click Installed Instances:

Then choose the OFFICESERVERS instance from the list and hit OK:

Your next screen should confirm that it found SQL Express:

If you click the Details… button you’ll see that the setup confirms that SQL Express can be upgraded. This step is optional.

At this point you can Close the box and hit OK until the setup is finished. After the setup is finished you’ll want to apply SP2 for SQL 2005 and any post SP2 patches that are available. I don’t know if it’s required but I always do an IISRESET after this to make sure that SharePoint reconnects properly to SQL.

That’s all there is to it. Once you are using full SQL you have quite a few more options available to you like log shipping, database replication, SQL Profiler and more. If you have any questions about how to leverage those tools with SharePoint, leave me a comment and let me know.

tk

Integrating CS2007 with Moss 2007


So, if you have been wanting waiting to use Office SharePoint Server 2007 in conjunction with Commerce Server 2007, this is the whitepaper for you.

http://www.microsoft.com/downloads/details.aspx?FamilyId=2AEB1A5E-43B8-483B-8CB2-86C0E82BF0AB&displaylang=en

This document covers the topics needed to take Commerce Server data and services and make them visible in portal sites based on Office SharePoint Server 2007. Samples are provided to show how to make custom Web parts that access the Commerce Server APIs.

MOSS 2007 and WSS 3.0 Service Pack 2 has been officially announced


Microsoft preparing for the release of Microsoft SharePoint 2007 WSS 3.0 Service Pack 2.

The Expected release will be something between February and April 2009

Here are some of the expected highlights for the SharePoint Area provided by the SharePoint Technical Product Managers:

  • Improved Read-only Content Databases
    Whenever a content database is marked read-only, all of the site collections in that database are automatically marked as read-only.
  • ECM Performance and Manageability Improvements
    Improved performance and manageability in variations, including STSADM commands for repairing links between source and target pages.
  • Improved Index Rebuild Timer Jobs
    SharePoint content databases running in SQL Server 2005 will undergo an automatic index rebuild, which helps stop defragmentation, and stop the database from degrading in performance.
  • Upgrade Checker
    This will scan your SharePoint farm in advance of applying SP2 and will provide feedback on the environments readiness to upgrade.

Information for customers who have not yet applied Service Pack 1: Based on the support lifecycle page support for systems without Service Pack 1 will end on January 13th 2009.