SQL Server 2012 AlwaysOn Availability Groups provides a unified high availability and disaster recovery (HADR) solution that improves upon legacy functionality previously found across disparate features. (more…)
Recently, I have had the need to remove all the web parts of the welcome page of a large number of sites. The number of sites was so big that the option of doing it manually was out. It is in these cases where we can always rely on Windows PowerShell, because the time invested in developing a script is profitable, plus we are learning along the way.
An important limitation that users have to face when they works with Performace Point Service’s tool, Dashboard Designer, is that it only allow users to choose those Master Pages that are physically located in the site where we want to deploy the Dashboard. It’s the reason that users cannot see those master pages that they have created and deployed in the Master Page Gallery in root site (/_catalogs/masterpage). Only can see default.master, minimal.master and v4.master, which there are phisically in each sub-site.
I’ve been working on accessing SharePoint data remotely (2007, 2010 and Online) in the last months and I found a couple of months ago a breaking point in my developments. The Events List (also known as SharePoint Calendar list).
When I tried to get list items fro this kind of list using this line of code
In this article, we will give a brief overview of Power View (code name “Crescent”) – what it is, the architecture and how it complements the Microsoft Business Intelligence tools stack. We also provide a few examples of reports. Power View is a new data visualization tool which allows users to interact with data. It is a web browser-based end user Microsoft Business Intelligence tool. (more…)
For et par uger siden var jeg sammen med en flok rimelig dygtige gutter i Redmond. Et godt bud, så var 30 af de 40 mennesker der var med MVP’ere, de resterende var blot MCM’ere og MCT’ere….og så var der lille mig
Emnet var Bare Metal, som i grundsubstansen går ud på at sætte et undervisningsmiljø op og træne ‘underviserne’ i at undervise hjemme i vore respektive lande.
Emnet for undervisningen var ‘de bedste features’ i SQL Server 2012. En dag gik med den relationelle del og den anden dag gik med BI delen.
Jeg må indrømme at der i denne version er nogle ting som får mig i godt humør, jeg kan blandt andet nævne AlwaysOn og PowerView.
AlwaysOn er en teknologi som samler de bedste ting fra Clustering, Mirroring og logshipping. Det bliver nu muligt at lave et cluster med DAS(lokale diske) og lave failover på grupper eller enkelte databaser…..endelig kan vi få noget IO performance på vore SQL Servere uden at skulle betale millioner for et SAN(som alligevel bliver misbrugt på det groveste )
Power View er en frontend til OLAP cubes. I lang tid har Excel været væktøjet, men nu er sortimentet udvidet. Power View giver en visuel og intuitiv ad-hoc-rapportering for ‘normale mennesker’. De kan nemt oprette rapporter og interagere med data fra modeller baseret på PowerPivot eller SSAS tabular baseret på SQL Server 2012 Analysis Services. Power View er et browserbaseret Silverlight applikation som startes fra SharePoint Server 2010. Måske en Targit killer
Jeg kan varmt anbefale at I begynder at lege med de nye features….jeres chef eller kunder vil elske de nye ting
In this article is going to be explained the differences between the Windows PowerShell console and the SharePoint Management Shell in SharePoint manage. SharePoint 2010 Management Shell loads a Windows PowerShell profile located in the SharePoint root. The profile’s path is: SharePointRoot CONFIG POWERSHELL Registration SharePoint.ps1.
This script configures the initial user environment for Windows PowerShell. The three things that the profile does are the followings:
I’m developing a custom desktop solution in Windows Presentation Foundation (WPF) that has to access a SharePoint Online contents and do some things with them.
The first thing I had to “fight” with was the Authentication method that is by default a bit different from the On-Premise version (programmatically too). When I started to look for the right documentation about that topic I found quite fast this great article from the MSDN library “Remote Authentication in SharePoint Online Using Claims-Based Authentication” by Robert Bogue. After read the article and download the Sample Code, I told myself “Yeah! This going to be a piece of cake!”.
First thing I have done is to open an existing 2008 SSAS solution on the new Denali BIDS, the conversion process is almost immediate, just to run a simple wizard but when you open the solution you’ll see that everything remains as before, even the SSAS environment, there is just a change on the look and feel of the menus and and background colours to accommodate to the Visual Studio 2010 IDE.
Once I have the solution open I have deployed it to the Denali instance and process it, again, no changes at all from previous version.
The first change I have found is a visual but important one: the pane where the cube is browse now looks and works as the SSRS one used for creating a SSAS dataset.Which is the impact on this change? From my point of view is big, because I don’t really like that SSRS pane.
It just allows you to explore the data as table, I mean with just dimensions on the rows axys, so no more dimensions available on the column area.
No more drillthrough actions available. The predefined actions you have defined on the cube item cannot be explore anymore from the browse tab, so you have to test them in a separate tool.
You have the option to convert the browse on a MDX query directly. That would be a good thing if the MDX query would be the best one, but so we are limited just to dimensions on the rows I do not really like it at all, (I will continue writing my own MDX I think)
There is one additional item that is not on the SSRS pane, a new icon so you can lauch Excel directly from the browse tab. So obviously they are directing you to run most of the test within Excel. That would have sense on a development environment, but the fact is that the same changes have been apply on the SQL Server Management Studio (SSMS) so is Microsoft trying to push everybody working with SSAS to have Excel setup even if you are working directly on a server?
Actually there are not many more changes on the OLAP BIDS side, the rest is related with the new features explained at the MSDN site. I’ll continue describing the new features on future posts.