… THE NEXT BYTE
A high-level overview of what databases are, and how SQL Server fits the mold.
What is a database?
Why do we need one?
How does SQL Server fit the mold?
In my last blog, I outlined the series of discussions I want to have about SharePoint and SQL Server. I said I would start at the beginning, which is ‘what is a database?’ (To complicate life,”Database” often refers both to the management program and to the data itself. Hopefully my usage will indicate which we’re referring to.)
The best generic definition of a database I’ve found is in Wikipedia. I’ll copy it here as it is succinct and spares me the trouble of trying to say in many of my own words what is already stated in fewer words:
(Meet Don Conrad, affectionately known as Don SQL in the office. This introduction into the SQL arena paves the way for further SQL content from Don.)
Hello, I’m Don Conrad. I’m the Database/Systems Architect for Fpweb.net, a dedicated SharePoint hosting company. Hosting SharePoint sites for customers around the globe is our only business. As a leader in our industry, we host thousands of sites– everything from small Foundation environments to some SharePoint Server Enterprise multi-server farms that demand literally terabytes of disk space.
Hosting for SharePoint, a Microsoft product, also requires SQL Server, another Microsoft product. The underlying architecture for SharePoint fundamentally relies upon- and resides within- SQL Server databases. Curious, that.
I take care of those database servers and have about 20 years of experience doing so. My main job is to help plan, configure, install and administer SQL Server database servers and databases for our various SharePoint hosting customers.