Sharepoint

We’ve just finished watching Jeff Teper and co. take us through a phenomenal tour of the new features coming to Office 365—specifically SharePoint. Last year, Jeff Teper, Corporate Vice President of Office, OneDrive, & SharePoint, walked the Microsoft world through the new SharePoint experience and reignited the excitement behind SharePoint.

This year (which now seems to be a general trend for the Office business group), they did it again at the SharePoint Virtual Summit event, streamed live across the web and Twitterraties to an unprecedented number of people.

SQL databases are not optimized for storing the unstructured content like documents, images and videos that dominates SharePoint. These unstructured objects, known as BLOBs, degrade performance and create SharePoint database sprawl, which is hard, time consuming and expensive to manage. StoragePoint shrinks SQL databases in SharePoint up to 98% by moving BLOBs outside those databases to storage of your choosing. This enables SharePoint content databases to remain lean, efficient and high performing.

Cloud really is changing the way that enterprises do their business. And while Amazon Web Services, Google Cloud and Microsoft Azure fight for the opportunity to help clients get to their cloud services, Microsoft is still the powerhouse brand for enterprise applications and since many enterprises already run Microsoft servers it has a traditional advantage.

Recovery Point Objective (RPO) and Recovery Time Objective (RTO) are essential cornerstones of any disaster recovery (DR) or backup plan. In fact, attempts to formulate a DR/Backup plan without RPO & RTO are little more than best-guesses. So what are these concepts and why are they important?

As a Product Manager, I often have the opportunity to talk to our customers and prospects about their SharePoint deployments.  Many of these conversations have been about the pros and cons of governance policies when using SharePoint Groups or Active Directory groups.

Governance policies are a set of rules and procedures put in place to help with the deployment, configuration, and management of SharePoint. In short, they determine how SharePoint will run, who will use it, and what equipment will be used.

As if you weren’t aware, your SharePoint environment could very well be a gigantic jumble of content. More than half of SharePoint deployments now measure well over 1 TB of content. Every year, this content grows around 65 percent. This is a lot of content – but what does it mean for you?

“How do we get the best speed from a SharePoint migration?”

It is one of the most common questions the Metalogix team is asked. I know a lot of people are looking for that magical GB/hour figure but there isn’t really a one-size-fits-all answer to this question. Let’s face it – we shouldn’t really expect that since SharePoint deployments are rarely, if ever, the same.

The long-awaited, much-anticipated SharePoint 2013 has finally arrived. At this point, many organizations are asking themselves whether they should upgrade to SharePoint 2013. For some organizations, now may be the time to considering investing in SharePoint for the first time and consolidating content.

Read Part 2Dispelling the Myths of Shredded Storage in SharePoint 2013

There is little doubt the SharePoint community is excited for SharePoint 2013. With 60% of users in a recent SharePoint survey saying they want to upgrade in the next year, the anticipation is building to a climax.

UPDATE: Moving to SharePoint 2016? Read the latest version of this blog, "Yes, You Can Move Straight From SharePoint 2010 to SharePoint 2016"

recent survey showed that a large number of SharePoint customers are still using versions of SharePoint older than 2010. So how do they move to the SharePoint 2013? This is a common question currently being asked on SharePoint forums. Worryingly, most answers are either wrong or not completely correct.

Pages

Subscribe to Sharepoint