Monday, January 25, 2010

Michael's Triples

  • Make it work, make it work better, make it work right (first 3 versions of a software product/solution)
  • Awareness, Education and Training, Experience (3 types of education)
  • Knowledge, Understanding, and Wisdom (3 stages on the way to becoming a subject matter expert)
  • Awareness and Education, Evaluation leading Pilot, Purchase leading Standarization (sales cycle)

Michael Herman
Software Solutions Architect

Tuesday, January 12, 2010

SharePoint Joel on 10 Key Questions Determining SharePoint SQL Server Count

Checkout Joel's article here: 10 Key Questions Determining SharePoint SQL Server Count

The short list of criteria from Joel's article includes:

1. Organizations and Organizational Politics
2. Pre-production - Development/Test/Stage
3. High Availability
4. Disaster Recovery
5. Dedicated Application or Isolation
6. Performance
7. Locations
8. Service Definition Branching
9. TB Storage footprint
10. Database Count

Michael Herman
SharePoint Architect

SharePoint 2010 Business Intelligence: Which client technology should you use?

When considering a client-side technology for a business intelligence solution based on Microsoft's SQL Server, Office 2010 and SharePoint 2010 platforms, there are many choices including:
- Excel
- Excel uploaded into Excel services
- SharePoint 2010 BI web parts (e.g. charting web part)
- SharePoint 2010 BI list templates (e.g. KPI list templates)
- PerformancePoint/SharePoint 2010 (Dashboard designer with support for KPIs, reports, charts, dashboards, etc)
- Custom ASP.NET web applications
- Custom WinForm applications
- Custom Silverlight applications

What's the right choice? The right choice should be primarily driven by who the different types of users are and how they will use the BI solution for in their day-to-day jobs. That is, you need to think most about what is the right technology that helps a particular group of users successfully complete their tasks.

Other considerations include criteria like desktop requirements for client technology, licensing costs, development, deployment and maintenance costs and governance (e.g. how much of the solution needs to be centrally managed/controlled, how much latitude does the user have in terms in interacting/changing/customizing the solution).

Michael Herman
Solution Architect

Installing Office 2007 and 2010 side-by-side

Office 2010 supports side-by-side installation with Office 2007. The one caveat is that if you have 32-bit Office 2007, Office 2010 will not allow you to install the 64-bit version of 2010 side-by-side.

If you want Office 2010 64-bit, you have to uninstall the 32-bit version of Office 2007.