Websites versus WebsiteCollections
-
Well, it's for planing Sharepoint solutions. I made up my mind about this topic. But I like to know what do you think about. First point: In a workshop I was told by a guy who set up sharepoint solutions for some big companies (for the guys in US: small companies, just about 3000 to 5000 workstations) that I should set up more collections. Sharepoint was designed for having thousands of websitecollections for each application, he said. Second point: In a book written by a so called guru I read that everything should go into websites and only if there is a strong separation there should be a new websitecollection. I tried to figure out who's right. Well, as I know only websitecollections can be backedup on their own but there is more administrative effort. Websitecollections can be placed on different databases and - as the SQL Server isn't able to handle one database on multiple servers - the only way to seperate them on different servers. Big databases get really slow (in case of the SQL Server) and because of multimedia documents the propagandizes maximum of 200 GB is a problem anyway. So, what do you think? Should I set up collections for every department and for special applications? I think so, but I don't know if I'm right. Hope you can tell your sentiments to this questions. :rolleyes:
------------------------------ Author of Primary ROleplaying SysTem How do I take my coffee? Black as midnight on a moonless night. War doesn't determine who's right. War determines who's left.