Forum Discussion
Migrating from network drive to SharePoint
stenci To get around the 300000 file limit it's an issue where you have to throw hardware at it. Balance the load across multiple machines using multiple clients.
SharePoint may not be the best place for this. As I said it sounds like this process just using SharePoint as a dumping ground.
I would say that if you're required to use SharePoint - this is incurring a lot of technical debt because of the need to use OneDrive client to sync contents as if they were in a local drive. Re-engineer the process to work for the place where you are storing the files there are plenty of different ways to automate the file upload process. I would also be mindful of how many files that are created that are like versioned by adding something to the end of the file because that could be de-duped by using versioning in SharePoint.
Whatever the outcome may be document what is going on because IMO - this isn't a process or development that I would want to come into having to figure out what is going on with it.
TimLB Smart caching / on demand file sync is a requirement, so SharePoint is not the right tool for us?
Is it possible to configure the library with the sync on demand for the last year and use the hand picked sync for the older folders?
For example we could keep available with on demand caching the last one year, or 180,000 files, and the older stuff, without on demand caching, will only be available if the user manually syncs the folder?
What you'll need is to structure of libraries/folders so that you don't have to "Sync" or access folders/files that may go over the limit. You'll need to take into consideration how many folders/files do you produce in a year, month, etc. separating them as libraries if necessary.
Also, another storage may be more suited if you think files/projects are no longer going to be accessed.
Fred
- > separating them as libraries if necessary
If I understand the documentation the limitation applies even if the files are separated in multiple libraries.- After reading your response to Timothy, I've seen files that have dependencies which relies on network path. This is also something to consider when using SharePoint as repository.
This may also involve re-thinking your process how files are accessed, in order, to go around the 300K limit as you've already identified - live and archive.