The Top 10 TN Wiki ninja’s page is always great fun: http://blogs.technet.com/b/wikininjas/archive/2012/06/03/top-10-wiki-ninjas-margriet-bruggeman-s-sharepoint-2012-best-practices.aspx. Margriet’s activities of last week led to the one and only TN Wiki Ninja stick figure:
Margriet is a regular TechNet Wiki contributor. Read more about how Wikis can help you placing the right bets in SharePoint projects on Margriet’s first post as a Wiki Ninja on the Official Blog of TechNet Wiki: http://blogs.technet.com/b/wikininjas/archive/2012/05/20/wikis-just-may-be-your-best-bet.aspx
Last week, Margriet has been quite active in the TechNet Wiki community. To tell the truth it was to her own surprise (see http://social.technet.microsoft.com/wiki/contents/articles/default.aspx) that Margriet ranked quite high. Now it’s a game, lets see if Margriet can move up one or two places.
This may not appeal to everyone, but here are some interesting links regarding the writing and keeping track of Wiki pages:
There are at least three kinds of best practices. Often, when companies inform about best practices they actually mean: what does MS say is the best practice. It’s also possible that people are referring to what are in fact practices, but not necessarily the best ones. And then there are true best practices.
The following Wiki page: http://social.technet.microsoft.com/wiki/contents/articles/8666.sharepoint-2010-best-practices-en.aspx contains a considerable list of SharePoint 2010 Best Practices. They are not best practices of the first kind we’ve mentioned (as they are not officially dictated and endorsed by MS), so we’ll leave it to you to decide if they are of the 2nd or 3rd kind. Or, heck, you can even contribute if you like!
Just started a Wiki page that discusses what to do when you have a slow performing SSRS report. Everybody is more than welcome to contribute at http://social.technet.microsoft.com/wiki/contents/articles/9950.sharepoint-2010-best-practice-troubleshooting-an-ssrs-report-that-times-out.aspx
It’s an interesting question: should you keep relational data in a database or migrate it into a custom list? We’d love our readers to contribute to the discussion at the TechNet Wiki page at http://social.technet.microsoft.com/wiki/contents/articles/9638.sharepoint-2010-best-practice-keep-relational-data-in-a-database-or-migrate-it-into-a-custom-list.aspx
The discussion as it stands so far:
If you need relational database capabilities (transactionality, triggers, real constraints (not the approximation of that in SharePoint)): use the existing database (and create a BCS external list to access the data).
– Are there existing apps using the current relational database? If yes, create a BCS external list to access the data.
– If no reasons prevent it, migrate the data into a custom list as this makes the solution less complex.
You need to make sure you play nicely and keep the data within the limits of capacity planning (https://sharepointdragons.com/2011/12/05/sharepoint-capacity-planning/ ). If there is absolutely no way that you can’t, keep the data where it is.