Hello everyone! Summer is all around us… The sun is shining bright. The sky’s clear. The birds are chirping. Let’s talk about some fun things such as: “SharePointing” SQL Server!
You’re thinking: Wow! That sounds like fun, but what is it? Well, this edition of The Next Byte has all the answers…
- What is “Sharepointing SQL Server”?
- What steps are in included?
- What are the benefits?
SharePointing SQL Server
It’s my name for the process of installing and configuring SQL Server to best meet the needs of most SharePoint Farms.
SQL Server has many options when it’s installed. It has even more configuration settings. It has these various options and settings because it’s used by so many different applications in so many different environments. It can be the data repository for large on-line-transaction-processing (OLTP) applications for a massive insurance company (like Progressive), supporting tens of thousands of users at once. (NOTE: I have no idea which databases any of the companies mentioned here have. I suspect they use many different ones, including SS. I’m just indicating the range of missions SS can be fitted to.) It can be the data warehouse for tens of terabytes of data–think a large, multi-national retailer such as McDonalds. It could be the repository and synchronizer for thousands of hand-held, geographically wide-spread, wirelessly linked data input devices. FedEx truck drivers come to mind.
It can even support the content databases for Fpweb.net’s internet site.
But it’s also obvious while the same database type can support all the above, that each instance has significantly different demands placed on the SQL Server, and the SQL Server must be set to work differently in each category.
The large insurance company will probably have a few very large databases processing thousands of transactions per second. The database will need to ensure all data is successfully entered, that no one overwrites someone else’s data. In the event of loss, all data must be recoverable to a given point in time. Users must be able to almost simultaneously access any of the data as soon as it’s entered. The system must ensure that no user blocks another user or process for more than a fraction of a second.
The large retailer also has thousands of users, but probably has hundreds, if not thousands of databases scattered world-wide. This data has to be quickly and accurately merged and accumulated so that the high-level managers can identify current trends within hours of the trends occurring.
The trucking company must be able to accumulate small amounts of data showing movement in small legs, storage, and further movement coming from throughout the world, sort and validate this data, and immediately send out messages to inform senders and recipients of the current status of the shipments without regards to where either is located. The database has to keep this data accurate and updated in real-time.
The same type of database also keeps this very blog safe and accessible at all times.
SQL Server Enterprise Edition can do all the above quite effectively. However, the installation and configuration its needs differs for each of the above types of environment. The major benefits are in the response time and in the administrative effort required to maintain the functionality.
In my next post we’ll discuss:
- Drives/partitions: How many and what are the impacts.
- File locations: Data files and transaction logs.
- Autogrowth: What is it? How should it typically be set up?
- Memory Caps: What are some considerations?
- Backup Modes/Transaction Logs: I’m sure I’ll receive many comments on my practices.
As each of these topic can easily take an entire edition of The Next Byte, and I don’t want to get partially through one and finish it next time, I’ll sign off now while all of you are eagerly waiting for and in great anticipation of my pearls of wisdom.
So in summary:
- We’ve explained what Sharepointing SQL Server is
- We discussed the reasons SharePointing becomes important
- We listed the major areas to be covered as drives, files, autogrowth, memory caps and backup modes
Watch this spot to see what’s next!
Until The Next Byte.