In both cases, you are upgrading an individual content database. NOTE: If you try to restore the content database (normally you do this on a backup of the content database) twice to the same farm it will fail because SharePoint doesn’t allow two site collections with the same GUID. Before you upgrade the content database you will want to run the PowerShell command Test-SPContentDatabase
Now there will be two users with the same login in the UserInfo table of your content database. One of them will be marked as deleted
Your Overall SharePoint Hierarchy - Whiteboarding There is always a challenge in describing the SharePoint front-end (the Sites and Hierarchy) with the back-end Site Collections and Content Databases. The business, understandably, just wants to store their content and are typically wondering why it is such a big deal for them to describe the exact type of content (size, type, content types \ metadata, etc.) to I.T. in this initial phase. I like to use the analogy when I whiteboard an enterprise or global SharePoint solution with EPC Group’s clients that the hierarchy (sites, landing pages, templates, etc.) are the front-end visual pieces but if “we were to remove this whiteboard from the wall” behind it we would find all of these “50 gallon drums or buckets” that represent our content databases. The content databases are critical (as the technical team knows) to store the content in a governed manner for which the growth of these content databases is scaled and new content databases will be created once the other content database(s) reach a specific size limit. I like to then ask the business and technical teams to imagine strings connecting sites and site collections to these content databases which will then connect to other areas of SharePoint in the overall hierarchy which will affect areas such as search and even more importantly tie into security (Active Directory \ SharePoint Security Groups, etc.)
Those delivery guys who hoisted your content database into position on the shiny new RAID 10 server?...So how can our SharePoint 2010 migration treat that content database with the respect that our future user experience deserves?
1 Comment - no search term matches found in comments.
A broadband user, with continental latency, would experience up to 2x-4x response time (e.g. 4-8 seconds) A broadband user, with global latency, would experience up to 4x-8x response time (e.g. 8-16 seconds) Low bandwidth, and extremely high latency response times’ experience is hard to predict Global Farm Administration Considerations Provisioning Web Application Creation Site Collection Creation Content Databases Features and Solutions Local Service Applications Excel Services Access Service Vision Graphics Service Word Automation Services Word Viewing Global Help Desk and Support Considerations Operations System Administrators Site Collection Administrators Multi-Tiered Support Tier 1: Help Desk Tier 2: Subject Matter Experts Tier 3: Farm Administrators Support and Administrative Training Global Governance: Isolation Levels Examples Level Definition SharePoint Meaning (Potential) Isolation Tier 1 (I1) (Global) ·Out of the box SharePoint ·Out of the box Security ·Uptime During Business Operating Hours (7am-5pm EST M-F) ·Same SharePoint Farm Same IIS Application Pool ·Same Web Application ·Same Site Collection ·Same Content Database Isolation Tier 2 (I2) (Global) ·Custom SharePoint Features ·Unique SharePoint Permission ·Uptime During Business Operating Hours (7am-5pm EST M-F) ·Same SharePoint Farm ·Separate IIS Application Pool ·Same Web Application ·Separate Site Collection ·Separate Content Database Isolation Tier 3 (I3) (Local) ·Third Party Application ·Custom Functionality ·24 x 7 Uptime requirements. ·Unique SharePoint Permission ·Separate SharePoint Farm ·Separate IIS Application Pool ·Separate Web Application ·Separate Site Collection ·Separate Content Database Global Governance: Service Agreement Examples Service Level Agreement 1 (SLA 1) ·Recycle Bin Policy set to 30 ·Weekly Full Backups and Daily Incremental ·Uptime During Business Hours Backup Retention for 6 months ·Same SharePoint Farm ·Same IIS Application Pool ·Same Web Application ·Same Site Collection ·Same Content Database Service Level Agreement 2 (SLA 2) ·Recycle Bin Policy set to 120 ·Weekly Full Backups and Daily Incremental ·Backup Retention 6 months ·Backup Retention for Incremental Backup for 4 Weeks ·Uptime During Business Hours ·After Hours Technical Support ·Separate Farm ·Separate Database Server EPC Group Lessons Learned Intranet and Internet Deployments Identify Global Governance Board early Roadmap features and solutions for at least 12 months Get buy-in not only from global stakeholders but from local support groups as well Create a unified governance model for ALL farms as though they are one Project and Team Collaboration Deployments Identify the Global Governance Board early Set limits on what is globally governed and what is locally governed Create a high-level global governance which focuses on overall policies, architecture and processes Create local governance extensions which cover people, local policies, local processes and operating procedures and needs
Well, anything that falls below that line is referred to in this high-level IT-centric roadmap as "content database." Even worse, any tweaking done in a prior version -- even with the out-of-the-box toolset is relegated to the gray area of customization
For that there’s an entire gift shop of gold certified vendors who write code designed to backfill SharePoint’s inability to present or instigate an enterprise level view of your Content Database. Ironically, it wasn't the migration story that wowed us but the more stable and established content management tools that provide a rich inroad into the user experience that are lost in the log files of our current MOSS deployment
We can now add millions of documents and create content databases in the terabyte range...Separate mission critical documents from other documents into different content databases. This will greatly increase disaster recovery time
I thought I could get by with building test sites under my department’s site, or, if I really wanted to get serious, I could create a separate content database for testing
One of the ways I illustrate this point in my day job as a SharePoint MVP is to share a couple simple pictures of the data structure of the native social features within SharePoint 2013, with a snapshot of the content databases that these features generate. My point is to show the volume and complexity of what is created around these standard features, but also how these content databases can be accessed by third-party solution providers and customers themselves, enabling us to build rich reporting and dashboard solutions
8403 Colesville Rd #1100Silver Spring, MD 20910USA
Phone: (301) 587-8202Toll free: (800) 477-2446Fax: (301) 587-2711Email: hello@aiim.org
JoinBenefitsLearn More
About UsTerms of Use