EVERYTHING in SP is in the SQL server. Configuration, web content, and files.
Furthermore, while you can have multiple sites (= separate SQL DB's), there are some gotchas, such as that content indexing is limited to site boundaries. Thus if you maintain multiple sites, you would need to run a search across each site for which you wanted to find a single doc, for instance. We are going to run an N+1 cluster, starting with 3 nodes, for the SQL backend. Quite frankly, the sheer size implications for the SQL server when SP is going to be used as a file-store replacement scare the daylights out of me. Especially with versioning allowing for the possibility of multiple copies of a single doc to be retained in the SQL store. Make sure you understand SQL backups, Sharepoint backups, metadata issues, your backup software, and TEST, TEST, TEST YOUR RESTORE AND DR SCENARIOS! And make sure your DBA's are up to speed. No. Really. A two terabytes database requires some significant care and feeding. -sc From: Bob Fronk [mailto:[email protected]] Sent: Thursday, August 27, 2009 1:39 PM To: NT System Admin Issues Subject: RE: OT: SharePoint design I am fine with public discussion, so here is where I am starting from. Currently we have multiple sites, each with at least one file server. Each file server is home for user profiles and a large number of shares. Users share documents across sites and across VPN from these shares. Obviously it is a nightmare with locked files, deleted files, permissions, and bandwidth. Bandwidth is 45mpbs Internet (VPN) and sites range from 12mpbs to 6mpbs (MPLS). My Exchange store is nearing 300GB. My goal as stated before it to eliminate Outlook as file transport and also make it easier for users to share files from their pages. What I need to understand better is where the files will be stored in SP and if it would make sense to have only one main SP server (probably a cluster). At this point, it seems one would be the best option with a large storage array. I would like to hear about implementations some of you have running now and how you might do it differently, or if you are happy with how it is working as you designed. Thanks to all! From: paul chinnery [mailto:[email protected]] Sent: Thursday, August 27, 2009 1:30 PM To: NT System Admin Issues Subject: RE: OT: SharePoint design +1 ________________________________ Subject: RE: OT: SharePoint design Date: Thu, 27 Aug 2009 13:20:27 -0400 From: [email protected] To: [email protected] I'd like to see the discussion here, rather than by offline phone call... we are wading in to SharePoint as well and would like to hear any tips and/or war stories. -sc From: Jon Harris [mailto:[email protected]] Sent: Thursday, August 27, 2009 12:36 PM To: NT System Admin Issues Subject: Re: OT: SharePoint design Before you get started make a decision on which one you will use, Sharepoint Services or Sharepoint server. It will make a difference with the design and what you can do later. Jon On Thu, Aug 27, 2009 at 12:15 PM, Bob Fronk <[email protected]> wrote: I am heading into a SharePoint rollout to help with our file share nightmare and "Outlook as a file transport" problems. Data is at multiple sites. If any SharePoint experts out there would be able to discuss this with me via email or phone call, please contact me off list at: [email protected] Thanks. Bob ________________________________ Hotmail(r) is up to 70% faster. Now good news travels really fast. Try it now. <http://windowslive.com/online/hotmail?ocid=PID23391::T:WLMTAGL:ON:WL:en -US:WM_HYGN_faster:082009> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
