concept storage in category sql server

appears as: storage, storage
Learn Windows SQL Server Administration in a Month of Lunches

This is an excerpt from Manning's book Learn Windows SQL Server Administration in a Month of Lunches.

4.4. Identifying potential performance concerns in storage

Storage is the absolute single biggest bottleneck for SQL Server performance. As such, one of your biggest concerns should be whether or not the storage layout is optimized for performance. Storage is also one of the biggest potential failure points, since disk drives do indeed fail every now and then. That means reliability and recoverability will be another concern. Your final concern relates to whether or not you’re able to efficiently back up and restore the database, should the need for restoration arise. How your database storage is laid out can affect that significantly.

SQL Server MVP Deep Dives Vol. 2

This is an excerpt from Manning's book SQL Server MVP Deep Dives Vol. 2.

After reviewing the requirements, you can see there’s an issue with the table’s design. The limit for the numbers of rows that can be inserted in the table is 2,147,483,647. This restriction creates a table that has an upper limit and additional data will trigger an arithmetic overflow error. The same remains true with the use of tiny int as well; I recommend that you go one size larger than you think you’ll need, unless storage is the primary concern.

The issue of disk alignment is extremely important from a performance standpoint. The issue comes down to the way that the master boot record (MBR) was defined when the first partition was created. The first 32k of space on the physical hard drive was originally used for the MBR, when storage was expensive. Today, disk space is fairly inexpensive.