Wednesday, 4 February 2009

Ever dreamed of Recycle Bin Security?

What I have learned today about the Recycle Bin Security behaviour:

  • The items in the recycle bin are only visible for the user who has deleted them.  It's not accessible to all users who had access to that document.

  • The "Recycle Bin" is only visible in the quick launch bar if you have the permission level "Delete Items". But ... if you click "View all site content" you can see the link to the recycle bin (bug?)

  • Only a site collection administrator can see the recycle bin of the end users and the site collection recycle bin.  Users with "Full Control" do not have acces.

Tuesday, 27 January 2009

Microsoft add Performance Point Server 2007 to the Enterprise CAL of SharePoint for FREE !

Great news for companies who own an enterprise license of SharePoint 2007.  Microsoft added a new product to the license for FREE !  The product is MS PerformancePoint Server 2007, this is a product for more advanced Business Intelligence (BI).

Announcement from Microsoft
More info on MS PerformancePoint Server 2007

Monday, 12 January 2009

How to configure a new SharePoint admin account?

What are the steps to create a new active directory user that can do installations in the SharePoint farm without having permission problems.

  • First add the user to the SharePoint Farm administrators group.  Go to "central administration" - "Operations" - "Update farm administrator's group" and add the user to the group.


  • Give the user access to the Shared Service Provider.  Go to "Personalization services permissions" of the SSP and give the user all rights.


  • Make the AD user DBOwner on all SQL databases of the Moss installation

  • Make sure the AD user is DBOwner on the content database of the administration site.  This is needed to add and install solutions in the farm.


If you run on Windows Server 2008 run all installation and .BAT files as administrator  ("Run as administrator").


With this account you now should be able to install all SharePoint solutions.

First Blogpost of 2009 !

First of all, I wish you all the best for 2009!

2009 will be an important and busy year for me. 

First of all we are expecting our first baby!  He or she, we don't know yet, will be very welcome this summer!   This is a picture from our baby last week at 12 weeks!  He or she is already 6,59cm!


And second ... we will start buidling our (dream)house this year.  Some months ago we bought a piece of ground in 'Waarmaarde' that's nearby Avelgem in West Flanders (Belgium).  During the past holiday I've tested Google Sketchup to create some 3D drawings to visualize our new home.  I must say Google Sketchup is an easy to use 3D tool and you can watch some video's as a start.  This is one of our idea's ... the water thing is phase 3 or 4 we think :-))


Thursday, 20 November 2008

Why "ItemUpdated" fires 2 times ?

I have a document library with an "ItemUpdated" item eventreceiver. Each time I upload a document, the eventreceiver fired 2 times in two different threads, with update conflicts as a concequens.

When you use check-in/check-out on your document libraries the check-in action also fires an ItemUpdated event. If found this information here (good article!):

We need to check which "ItemUpdated" we deal with ... the one from the check-in or the 'real' one. If found this code on the MS site to check the source of the event:

if (properties.AfterProperties["vti_sourcecontrolcheckedoutby"] == null && properties.BeforeProperties["vti_sourcecontrolcheckedoutby"] != null)
//This is when the update event is triggered by
//This is triggered by events other than check-in


Wednesday, 12 November 2008

Moss 2007 Database Migration - Diskspace Usage and Upgrade time

I'm currently working on a database migration SharePoint 2003 to Moss 2007.  One of my concerns was the diskspace usage during the migration.

In a previous post i wrote that a gradual upgrade can take up to  6,19 times the original diskspace.  So i had reasons to worry ...

I can tell you, a database migration takes less space, here are my test results:


Content Database 1 (+/- 12 GB)

  Before Migration After DB Migration
DATA File 11.706.624 kb 11.706.624 kb
LOG File 20.096 kb 1.219.712 kb

Logfile growth / data file = 10,42 %

Content Database 2 (+/- 58 GB)

  Before Migration After DB Migration
DATA File 58.035.584 kb 58.035.584 kb
LOG File 20.096 kb 9.930.624 kb

Logfile growth / data file = 17,11 %

Content Database 3 (+/- 18 GB)

  Before Migration After DB Migration
DATA File 17.139.776 kb 17.139.776 kb
LOG File 26.816 kb 1.321.088 kb

Logfile growth / data file = 7,71 %


The upgrade time of the DB migration depends on the hardware AND the features you want to activate during the migration.  I did a test activating the publishing features during the upgrade.

Database 1 - without publishing features : 15 minutes
Database 1 - with publishing features : 1 hour 40 minutes

Database 2 - without publishing features : not tested
Database 2 - with publishing features : 1 hour 53 minutes

Database 3 - without publishing features : 12 minutes
Database 3 - with publishing features : 51 minutes


  • The DATA file does not grow
  • The LOG file grows between 7% and 20% of the datafile
  • The upgrade time of the migration is short but depends on the features you want to activate during the upgrade.

Visual Studio 2010 Tools for SharePoint

A summary of what we can expect:

  • Server Explorer for SharePoint viewing Lists and other artifacts in SharePoint directly inside of Visual Studio

  • Windows SharePoint Services Project (WSP file) Import to create a new solution

  • Added a new web part project item and showed the Visual web part designer which loads a user control as a web part for SharePoint

  • Showed adding an event receiver for SharePoint and using the wizard to choose the event receiver and to just create a source file with that event receiver.

  • Added an ASPX workflow initiation form to a workflow project and showed how this workflow initiation form has designer capability

  • Showed the packaging explorer and the packaging editor which lets you structure the SharePoint features and WSP file that is created