A family of Microsoft relational database management systems designed for ease of use.
The main issue with SharePoint is the list size limitation (5000). If you plan on a db tables with large recordsets SharePoint just won't do.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We have an application which was working okay till last month. But after the last windows update our clients are getting issues with access database. access database got corrupted. We ran compact and repair. But it still getting corrupted again and again. This issue started right after the window update. clients are on different OS. Like server 2018, server 2012 and windows 10.
Is there anything i have check in new windows update or any other step to prevent database corruption?
A family of Microsoft relational database management systems designed for ease of use.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
The main issue with SharePoint is the list size limitation (5000). If you plan on a db tables with large recordsets SharePoint just won't do.
I see that Microsoft suggest SharePoint as a possible solution for "light workloads", although of course they do not define this. On reading more about how data is stored in SharePoint (apparently all in one SQL Server table) and its limitations, it seems to me wholly unsuitable for any moderately complex or sizable database application. Maybe someone can describe a database which is working well with a SharePoint back-end, so that readers have some idea whether its worth taking the time to test their own application?
Search online for "sharepoint 5000 records". I don't consider it a viable option for real database work.
I found this article - Thoughts ?
https://sharepointmaven.com/how-to-overcome-sharepoint-5000-item-limit-threshold/
David, I have been researching this as a possible option but am not sold on it. If it proves to be an ineffective solution, I will no longer pursue it.
I find it ironic that Microsoft views a potential solution negatively when they have done basically nothing to effectively fix this Access data corruption issue for the past 3 years.