I've often thought the default number of site collections allowed in a content database is just silly. While you can put 5000+ site collections in a single database, in most environments, that's unrealistic. When I teach this part of the SharePoint 2013 course, I relate several elements in the product that work together to help the ITPro SharePoint Farm administrator manage their databases.
When I was learning basic networking back in the late 90's, I was introduced to a fun, yet insightful RFC that contained the 12 Fundamental Truths of Networking (RFC 1925). In this post, I'd like to correlate those truths with SharePoint. The truths were meant to be a bit tongue-in-cheek, but they are useful when thinking about a SharePoint deployment.
Cloud computing is such a valuable solution that some organizations may be so eager to start using the service that they overlook the long-term planning process. The technology is not going anywhere, so there is no need to rush any deployment. Corporate decision-makers should find an affordable and functional product that supports the unique needs of their employers, not just select the least expensive suite on the market.
This week, I found out a very interesting fact: there is a limit to the number of Web Parts a page can have in SharePoint 2013. I know what you are thinking: How on Earth did someone find out there was a limit to Web Parts on a page in SharePoint. Or if you were me, it was, "Holy smokes that is crazy, but interesting!"
SharePoint Online presents quite a compelling business case for most organizations. It offers a tremendous amount of features for a low cost and fewer headaches. However, many companies still need to keep an on-premises SharePoint farm for a variety of reasons, requiring them to deploy a hybrid topology.
Many times we want to give someone a quick status by stopping by their office and saying a quick sentence. I'm the recipient of this type of drive-by status quite often. Usually it happens by people standing in my doorway and starting to talk.