Hi,

We are currently planning for a new Structure to be implemented... But I am stock on what the best approach may be.

Having spent some time on Miscrosoft documents looking for answer, I am having to hope for a solution on this forum...

If you have time to spare, I would appreciate your help.

Our current set up, 4 Site collections (one per jurisdictions)...

First problem, sharing and collaborate between these site collections.... It can't happen...??

Second problem... 2 of our 4 collections are maxed out at just under 200Gb. I undertstand that it is not recommended to go beyond... in Fact when we did, the whole Site ran very slow...

So we are contemplating Re-creating our Sharepoint environment, and create a Site Collection per CLient, to allow for growth, per client, But this seems a little extreme, especially when we have way more than say... a few clients....

So whats best practice here....

We have various teams working in different Jurisdictions, sharing, collaborating on each clients...

The ideal scenario would be a single Team Site Collection, but a Sub Site per Client, but we would go way above the 200Gb Limit...

Where do we go from here?

Anyone experienced this ? Any suggestions?

Apologies if this topic has been covered...

Steph

If you have plenty of disk space but are worried about the 200GB database limit then you could either add additional content databases to your site collection or use RBS (Remote Blob Storage) to store large files directly on disk as opposed to inside the database.

I have written about my experience enabling RBS here: http://www.adventuresinsharepoint.co.uk/index.php/2013/10/05/enable-filestream-and-provision-a-remote-blob-store/

And there is information on adding content databases here: http://technet.microsoft.com/en-us/library/cc825317(v=office.14).aspx