Application-Aware Data Management
I don’t know how I missed this article from InfoStor a bit ago, but it had me thinking… It sort of answers the call about the whole "how do I split up my databases for recovery, for performance, for reporting… and should I?" It doesn’t really ask that question, but if you think about what they’re saying in the article, it applies.
What they’re saying, in essence, is that applications (both the end-user variety and the server-type) are getting to the point where information can be stored and managed differently depending on how that information will be used. You can approach this from a fancy application-centric ideology, or you can read a little more layperson-style thought into it. As we work to figure out where to put all of the information we’re collectively managing, think too about how it can be split up. You can start with filegroups, but there is more work than that that can be done to make your system more maintainable.
Split off that read-only or infrequently updated information. Optimize the frequently accessed information based on your fastest drives.
There are a number of things you can do to really optimize performance, storage and recoverability, just by thinking about the best place and means of storing specific data sets for your applications.
Featured White Paper(s)
Choosing a Remote DBA Instead of a Full-time Consultant
Relational databases like SQL Server and Oracle grow 3x to 5x in size every three years and present organizations with signif… (read more)
Meeting Sarbanes-Oxley Requirements with DB Audit
… (read more)