Well well well, look what’s happened, I have spent quite some time threatening to get into SharePoint Development and a few weeks ago I decided I would make some effort to get things going and with that in mind, of course, I wanted to share my thoughts and my journey.
One of the most underappreciated (in my estimation) roles in IT is the Business Analyst, and yet it should be one of the most critical functions in your organization. Within many companies, a BA is viewed as being junior to project managers, with all BA’s aspiring to the PM role. This should not be the case — the BA and PM are two very different roles, and at some companies, the BA is a much more senior function. I’ve spent a good portion of my career managing PM and BA teams, spinning up project management organizations (PMOs), and working with both as an outside consultant. The roles are distinct, the skill sets are different.
Part of being a SharePoint solutions architect means designing a solution based on technical, maintenance and governance requirements. One of the most important initial design questions is whether to recommend Sites or Site Collections for a solution.
Following on from a recent post I made about a SharePoint health analyzer rule that can be used to automatically expand a SharePoint content database outside of normal working hours, I wanted to create a solution for monitoring content databases growth over time via central admin. Here’s what I came up with:
SQL 2012 brings some great capabilities to the table for an “Always-On” environment. In this post we will configure our SQL 2012 environment to be ready for SharePoint. To begin with my environment is made up of the following:
1.2 x SQL 2012 Servers
2.1 x SharePoint Server
3.1 x AD Server
Of course in the real world I would have more servers than this, especially from the SharePoint side. Firstly you will need to install SQL 2012 which I am not going to cover here as it is just like installing any other version. Once installed you will need to access the “SQL Server Configuration Manager”.
Office 365 plans comes with support for public facing websites. No matter if you are using Small Business Plan (P Plan) or one of the Enterprise Plans (E Plans), you can create exactly one public facing website. The difference between plans is the fact that for P plan public website is created automatically at the root level immediately after you establish your account, and for the E plans it have to be created manually.
Steve Fox, Director of Developer and Platform Evangelism at Microsoft, shares his thoughts on the one thing that people need to know about SharePoint 2010. This is part of ‘The One Thing’ video series produced by Christian Buckley (@buckleyplanet) and the Axceler team.
SharePoint 2010 is coming up to its 2 year birthday, so it worth talking about Ribbons. Too often solutions concentrate on pages, Web Parts, lists, libraries and workflows. A SharePoint solution should be more than this – each of these components should be combined to provide users with a holistic solution, where the components work together and not as discrete entities.
Where do I start? The users demand support for multi lingual. First step I see is to start supporting the language packs… but which ones? You need to figure it out. You may not be best served by simply installing all of them. What would happen if MS decided to stop supporting one of them? I’ve found a few places that make me sound smart when I recommend languages to support… It doesn’t have to be a guessing game. 1)