Sharepoint recurring calender events filter

We are improving our processes using Sharepoint. On paper everything works well. In real life, its sometimes difficult.

I was trying to create a agendaview of the current week in Sharepoint. This wasn't supported default by sharepoint.

There is a workaround to fix it:
How To:
If there is a calendar, and you want to create a view where only events from today up to the next 60 days (or how many days out), here is how you do it:

• Add a column to your calendar.
• Name it “Date” and make it a calculated field.
• Add “Start date” to the formula, and select “add date only”.

What this does is it creates a column that is filterable, because Start Date is not, and automatically populates the content of this column with the start date of the event.

• Next, create a new view for the calendar, name it “Upcoming” (or whatever).
• Select whatever fields you would like to display. If you are creating a view to show on another page, like the home page, and you just want a quick list of upcoming events, you might want to just have title and date fields display.
• Under “Filter”, select: Date is less than or equal to[Today]+60andDate is greater than or equal to[Today]+60

http://designshare.wordpress.com/2007/11/02/filter-calendar-view/

This works for normal calendar events. But when using recurring events the start date defaults to the day the event was set to start. While the "Start Time" column displays the different dates as they progress, if you do the calculated field on "Start Time" it will only return the start time of the entire recurring event. So if you told the recurring event to start on 8/1/08, the Start Time may show 8/5/08 (today) but the calculated column will still show 8/1/08 regardless.

I did not find a fix yet!

http://abstractspaces.wordpress.com/2008/05/14/filter-list-view-by-current-week/

http://weblogs.asp.net/gunnarpeipman/archive/2007/10/09/filtering-sharepoint-calendar-by-start-time.aspx

Performance counter registry hive consistency check has the status FAILED

While installing MS SQL Server 2008 r2 on windows 7, i got an error on one of the systemchecks:

• Performance counter registry hive consistency check has the status FAILED

To fix it, i did the following:

Put this in any Console application:

• string.Format("{0,3}", CultureInfo.InstalledUICulture.Parent.LCID.ToString("X")).Replace(" ", "0");

The write down the result. i.e. "016".

Go to the registry at this key:

• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib

Add the found value as entry. In this example:

• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\016

Then copy the key's form the original entry to the new on.

Restart the setup, and you are ready to go!

http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/dddf0349-557b-48c7-bf82-6bd1adb5c694?prof=required

How to Install SQL Server 2008 R2 (Express Edition) – November CTP

Installing SQL Server 2008 R2, i found the following interesting blog bij Petersad:

http://blogs.msdn.com/petersad/archive/2009/11/13/how-to-install-sql-server-2008-r2-express-edition-november-ctp.aspx

Overview:

With the release of the SQL Server 2008 R2 November CTP, we have simplified the SQL Server Express (all editions and package) installation process. In this release, we have completed the following:

1. Reduced the number of clicks by 50% when performing an install.
2. All inputs are defaulted on Vista and above operating systems. (many inputs are defaults on Windows XP and Windows 2003, except for the service accounts)
3. Skip (auto advance) through the UI, meaning non-essential dialogs will still be skipped.
4. Reduced the size of the Express basic package

For more detailed information on the SQL Server Express release, see: http://www.microsoft.com/downloads/details.aspx?FamilyID=c772467d-e45b-43e1-9208-2c7b663d7ad1&displaylang=en

The primary SQL Server Express downloads:

• Express Base/Core (Includes the Database Engine without management tools)
  • SQLEXPR32_x86 Executable <== Select this option if your system is 32-bit
  • SQLEXPR_X64 Executable <== Select this option if your system is 64-bit

• Express Advanced (Includes the Database Engine, Reporting Services, and management Tools)
  • SQLEXPRADV_x86 Executable <== Select this option if your system is 32-bit
  • SQLEXPRADV_X64 Executable <== Select this option if your system is 64-bit

1. Launch the package, you will then see the contents extracted to a temporary location.

2. SQL Server Setup checks to determine pre-reqs are installed. If not, you will be prompted to install.

3. The Installation Center will then launch. Click on “New installation or add feature to an existing installation” to start the Installation Wizard.

4. Accept the license terms.

5. Review the features to installed and where SQL Server will be installed. Make any changes that are necessary for your environment.

6. Review the Instance Name and change if necessary.

7. Review the credentials that will be used for the services that will be created.

8. Review the Authentication Mode and the administrators that will be added to the Database Engine.

9. Review the Error Reporting settings. We encourage you to keep this option checked, as we review the product feedback on an ongoing basic. This helps us to continually improve SQL Server.

10. That’s it!

Support/Feedback

If you have further questions or feedback, you have a few options:

• Submit feedback through the SQL Server connect site: http://connect.microsoft.com/SQLServer (This is the preferred option, if you have an installation failure)
• Make a comment about this post below. I will answer as many questions as possible.
• MSDN: http://social.msdn.microsoft.com/Forums/en-US/category/sqlserver/

upgrading ms sql server 2008 to r2 FeatureUpgradeMatrixCheck

I was trying to upgrading ms sql server 2008 to r2, but got an error on FeatureUpgradeMatrixCheck.
The error was by design.
You can't upgrade a Real SKU to an Eval Sku. You need to look at the SKU matrix that is documented in BOL and determine which SKUs are valid to upgrade to and then provide an appropriate key. The keys are available on the download site.

https://connect.microsoft.com/SQLServer/feedback/details/349850/2008rc0-featureupgradematrixcheck-blocks-upgrade-of-ssas

Suppress Auto Update of MDX Parameter Datasets in Reporting Services 2008

With the MDX Query Designer in SSRS 2008 Report Designer and Report Builder 2.0, changing the main dataset overwrites the parameter datasets, which will kill any manual adjustments you’ve made. Bummer.
The hack to fix is to add a SuppressAutoUpdate =true to the parameter dataset. Right click the report and choose View Code. Find the dataset, and in the relevant node pertaining to your dataset, modify it. Then Save.

<Query>

<DataSourceName>DataSource1</DataSourceName>

<CommandText> …

<rd:SuppressAutoUpdate>true</rd:SuppressAutoUpdate>

<rd:Hidden>false</rd:Hidden>

</Query>

I found this solution here:
Suppress Auto Update of MDX Parameter Datasets in Reporting Services 2008

Changing all-name in dimension

When working with cubes and dimensions and you have a dimension with time for example, you have the value "All" default added. "All"means that you select all occurrences in the time dimension, selecting the measures over all time.

When you create reports using cubes, this all-value is default added to the report as well. So when you create a parameter, "All" is included in the dropdownbox:

To support your users, "all" is not the best discription that can be added. A better option would be "all time", or "last 5 year" (depending on the horizon of your dimension).

To change this default behavour, go to your cubedesgin and go to the properties of your dimension. Then change the field AttributeAllMemberName to the disired name:

Leaving it blank will default add "all". Changing the property will add your given name as all-value.

Executing jobs with SQL

When you work with a scheduling tool outside MS SQL, it can be handy to execute jobs using this external tool. If its a trigger or a scheduled time, it's always important keeping your processes together in one place to maintain overview. So if you need to execute jobs you can use the following:

CREATE PROCEDURE refresh_cubes AS

EXEC msdb.dbo.sp_start_job @job_name = 'refresh_cubes'
GO

http://www.dbforums.com/microsoft-sql-server/927352-how-start-dts-job.html