It's very stable. We've rarely encountered any challenges, and Microsoft is quick to address any problems that do arise.

It is very stable. I haven't had any outages or any issues.

Compared to OneDrive, SharePoint has been a more stable product. Many times, the systems crash due to accidental sign-ups. Managing these crashes involved unlinking the files, sometimes causing them to be associated with personal accounts instead of the organization's email, leading to numerous challenges.

I give SharePoint's stability an eight out of ten because of the mobile app integration issues.

The tool is very stable. I rate the stability a nine out of ten.

I haven't had any issues around that. It's all very stable once it's deployed.

We haven't had any issues with the tool’s stability.

Stability issues are usually related to poor architecture planning, or solutions developed without a knowledge of how the tool works.

Stability, even after deployment three months ago, still seems to be an issue. Tagging does not always show up in trending hashtags immediately. When tagging and @mentions work is not consistent from place to place.

SharePoint Online is stable. We are using the out-of-box options only, and it has been stable.

I am satisfied with the tool’s stability. I rate the stability a ten out of ten.

Mostly, we have not encountered any stability issues.

The product is stable.

I have never encountered stability issues.

The stability of SharePoint needs improvement, because once you start to get a large amount of data, it becomes very unwieldy, and it takes a long time to index. There are much better products for content management and knowledge management, when compared to SharePoint.

We have not encountered any stability issues.

I did not have any stability issues.

The stability of SharePoint is very good, amazing.

For a company like ours with around 25,000 users, this product is good and quite stable. We need to explore what happens when the data increases beyond 1 million or 10 million records. At that point, we may need to look again at scalability and what the product can support. They have support for vertical or horizontal scaling. They have a feature where you can increase server hardware, but that needs to be checked. We have two people assisting with maintenance. 

Again, no problems on our applications.

In some very rare cases, you might see that Windows updates can interrupt your service, but Microsoft is very quick to fix the issue. Other than that, it’s the users’ empowerment that is in play in this environment overall. You are providing a platform that empowers the users of the product to manage themselves. For example, instead of a call to the help desk, you have what are known as site collection administrators and owners. These power users manage the security of the site. So, instead of having a call to the help desk, the group’s power user can manage these calls themselves, which takes a load off of the help desk. This is one of many examples.

We did have stability issues in the old versions and there were too many hotfixes, in the 2013 version. It’s more stable now, but it can still be better.

I have not encountered stability issues with either the on-premise or cloud hosted versions of the product.

I have not encountered any stability issues.

SharePoint is a stable solution.

Some stability issues have been found with the database. From the infrastructure side, most people use dedicated databases for SharePoint so a simple reboot usually fixes the communication issues.

We did not have any stability issues.

I have not encountered any stability issues, but prior infrastructure planning is a must. When systems are well defined, all setup and integration runs smoothly.

The stability of the system is fine, so long as you have a well prepared support team for your Windows offerings.

I have encountered stability issues when connecting to TFS 2013 for reporting.

There have been no stability issues other than with user profile synchronization. The only times we have had SharePoint offline in the last 10 years were when we had a server issue in 2010 and when we have taken it offline for maintenance.

Any issues regarding stability are generally caused by a lack of governance from planning of the underlying infrastructure through ongoing operations. With best practices in rolling out any application from an infrastructure planning and operations perspective, stability is not a significant issue.

It is very stable if you know what you are doing and make some precautions. Microsoft lists these precautions, but these precautions are not automatized. It would be nice to have precautions such as: disk size, backup checks, or whatever automized that can be integrated with the SCCM team foundations server.

When used with large data, SharePoint may produce performance degradation; that requires some optimization and tweaks.

We have not encountered any stability issues.

I have not encountered any stability issues; very reliable.

Most instances of SharePoint are stable. I have rarely experienced instability. Usually, it’s the management of user names and groups that results in problems.

We had issues with stability when we implemented it at a previous company. We had issues where the system was down for a while.

Stability is always a big issue, but not from the view of SharePoint itself. It’s more of an issue from the architecture and infrastructure point of view. Many customers implement SharePoint on virtual machines with dynamic memory allocation. VMs have slow disk access speeds that are below recommended specifications.

In these situations, there are always issues with stability, especially regarding search services, etc. For example, if you installed SharePoint on a virtual machine with dynamic memory, it could destroy the farm without any possibility of repairing it. You will then have to reinstall the whole farm. This would really be a big problem in the case of a farm with 10 virtual servers.

N/A

It is VERY stable if you follow the recommended settings and read the SharePoint blogs.

We have not encountered any stability issues. The version 10.2 we use is very stable.

Occasionally, the SQL database backend would have issues to address regarding maintenance.

We did not encounter any stability issues. In most cases, instability is caused by client or vendor implementation errors.

Occasional Office365 SharePoint outages have been noted.

For the most part, SharePoint was stable based upon the set up that we have. When installing the R2 update, it did end up creating issues with the .NET code and eliminated some of the extensions. For example, the Excel extension that is used to view Excel spreadsheets within SharePoint was either damaged or deleted. This has caused issues with exporting to and from SharePoint and hasn't been corrected.

It is stable after the hotfixes, or service pack has been applied. This has been the case for each release since 2003. If you take the release directly to the customer then it is almost always a big mess for them during implementation.

When the number of documents in a library grows too high, there will be performance issues. There is no easy way to archive files uploaded to SharePoint unless you have extra budget to get 3rd party solutions like AvePoint.

The only issue that we have is when we are creating a new site from templates. During such a situation, many of the sub-components do not work or have to be completely reconfigured once created. This makes the creation of a new project based on our project site template very painful.

There is a limitation on the number of files that can be uploaded.

I encountered no stability issues.

There were very few stability issues. The issues are usually related to problems with the related Microsoft stack such as Windows Server/ SQL/ IIS.

For the enterprise environment, I did not encounter any stability issues.

We did not have any stability issues.

I definitely encounter stability issues, like all other Microsoft-related solutions.

We did not have any stability problems.

I did not encounter any issues with stability.

The fact that it relies on the Internet and runs in a browser means it is bound to have performance issues.

We never had any stability issues. In fact, our system is quite simple. We only experienced downtime three times in six years. This was only due to a VM management problem with human resources.

I have not encountered any stability issues. SharePoint is a very stable platform, provided that it's installed on an equally stable server environment.

Occasionally, we come across strange server-level errors, but they are few and far between. Normal users almost never have problems, except for permission-based incidents.

I have run into problems with Microsoft updates killing my test machine for two months...

It's going to last until Microsoft revokes the license on which it is built.

My personal observation is that if the implementations are done in the right way by following the recommended best practices and guidelines, the product works just fine.

To be clear, I am referring to all the underlying products (IIS, SQL Server) as well as to the O/S.

There have been genuine issues. However, we have used SharePoint and CU to address them.

I did not encounter any issues with stability.

At first, we encountered stability issues, but they have been ironed out and – knock on wood – we have been stable for a while. I believe our issue might have been related to sizing the resources properly, as we started small with the intention of growing as we developed more uses for the product.

The current version is very stable compared to versions 2007 and 2010.

We have had no issues with stability.

I have not encountered any stability issues, as such.

The early RTP versions can be buggy. There are always challenges with patches, but the product has improved over time.

We have not really had stability issues, particularly in the 2013 version.

I have not encountered any stability issues. It is an excellent product if you don’t have to customize it too much.

Stability is OK.

Stability issues have been found with the database. From the infrastructure side, most people use dedicated databases for SharePoint so a simple reboot usually fixes the communication issues.

We have not encountered any stability issues.

With an on-premise, or even a hybrid model, local operations and platform teams are responsible for the uptime of the system. Most common issues are service halt, drive space management, and database corruption. All of this can be resolved easily with an Office 365 infrastructure migration.

I find SharePoint to be stable. No complaints there.

It is stable.

We have had difficulty with stability. The configuration and administration of SharePoint is complex. This resulted in incidents when changes to other products were made, like Active Directory or Exchange. Time consuming maintenance tasks are necessary, otherwise your SharePoint instance will become unstable.

I did not encounter any stability issues.

There were no major stability issues as such, but the user profile service stopped unexpectedly on a few occasions.

It is very stable. But, I think it depends on the infrastructure. 

It is very stability. I don't foresee any issues.

We have not experienced any serious issues regarding stability, except for the minor glitches with workflows. As previously mentioned, we are still on the Foundation version. However, I believe if SharePoint has been properly set up on a stable server, using proper governance and a strong infrastructure, we should not experience major issues with stability.

There were issues with a cumulative update for SharePoint.

No issues have been encountered in terms of stability.

We have not had any stability issues.

The product is quite stable.

I did not encounter any issues with stability.

We did not have any stability problems.

Stability was usually good.

We had stability issues regarding the TFS integration.

We have spent some time reconfiguring the farm in order to overcome performance degradation.

Stability is okay. The performance is great.

We have had no stability issues that I am aware of.

We did not have stability issues.

I have not encountered that many stability issues.