Base Your SharePoint Database Architecture on Business Requirements First, Database Concerns Second

Sometimes when I’m speaking at SharePoint events, I’ll mention something about the fact that “the geeks” make decisions about Site Collections and database boundaries that are a detriment to the users. I got a question about this the other day: …you mentioned something that I wanted to follow up on: basically it was a warning…

Just Because They Are SharePoint Lists It Doesn’t Mean Good Database Rules Don’t Apply

Matt Bramer and I were helping someone out in the Stump the Panel forums at EndUserSharePoint.com the other day and in the conversation, the person posted this list structure: I created a list called “Solution Team Profiles” with the following columns affinity to market birth date Bus Phone Cell Phone Clearence Levels Deal 1 Allocation…