||SQL Server Tips by Robin Schumacher
What about Self-Managing
What about the whole concept of self-managing databases? Have
Microsoft and the other database vendors made the need for
Performance Lifecycle Management obsolete by embedding new automatic
functionality within the database engine? Hardly.
The recent shift in the major database vendors’ marketing messages
has been interesting. For years, it used to be that the two primary
themes of any new database release centered on performance and
scalability. This made sense because each database vendor understood
that nearly every corporation’s datastores were expanding at
exponential levels, hence the touch point for scalability.
Additionally, the need for speed with respect to application
response times continued to be severe in nearly every environment,
thus the performance concentration.
While performance and scalability are still trumpeted by the
database giants, they are now overshadowed by a focus on
manageability. This can be seen in the releases of IBM DB2 UDB
version 8 and SQL Server database 10g, both of which tout the
self-managing features of the database. Microsoft SQL Server has
ridden this same concept in a quieter fashion especially since
version 7.0, and it continues in SQL Server 2005.
It is not surprising that such messaging is being put forth right
now. Much of this recent push can be traced back to economics. The
turbulent economy has, during the early 2000’s, caused many IT
managers to shift focus from “bigger and better” to cost control.
Given the changed corporate mindset, the database vendors find
themselves in a position of needing to convince IT management that
their databases are not complex or expensive to purchase and manage.
This need has translated into a number of enhancements to the
database engine which eases the burden on the DBA in the areas of
setup, configuration, administration, and backup/recovery.
The above book excerpt is from:
High-Performance SQL Server DBA
Tuning & Optimization Secrets