Uncategorized

The SQL Server Commodity – Feedback…


Featured Article(s)

Troubleshooting SQL Server 2005 Merge Replication (Part 2)
In this article, Alexander Chigrik explains some problems that you can have when you work with SQL Server 2005 merge replication. He also tells how you can resolve these problems.

Virtual Server Protection and Recovery
Building out your infrastructure with virtual servers brings with it the requirement that you be able to support, recovery and restore those virtual servers. Once you start to rely on the virtual servers and virtual environments, you find that you can run into challenges when it comes to picking up the pieces after a failure. This is where Sonasoft can help out – using the one-touch options, you can check the status of your systems, control failover to a backup server and even kick off the automatic recovery. SQL Server, Exchange and more – all protected. Get more information here.

The SQL Server Commodity – Feedback…
Yesterday I mentioned that I was wondering a bit if SQL Server is headed for being a "commodity" type service – one that doesn’t require specific attention and management, but rather "just works." (Read more here)

James wrote with their take on the situation: "We’re seeing precisely this (automated database management and maintenance) with the recent systems we’ve been delivering. Part of what is driving this is the complexity of a combined object/relational environment and the need to know that performance optimization and general structural maintenance are being done automatically to ensure that the overlying applications always have optimal access to the areas of the database they are supposed to see. We’ve reached the point of integrating maintenance instructions into meta-data and setting Performance Indicators on those metrics so we can allow the databases to self-determine more optimal paths (new indexes on heavily used tables based on recorded query patterns, for example) for data access.


With the solutions we have been delivering, this approach has worked well and has been viewed as being necessary by our clients. I think there’s no doubt that there will still be a need for regular DBA management of some systems based on special needs but we find it has been beneficial to develop the database environment to do as much of this work as possible and to simply report the results to us! This allows us to focus our efforts on innovative development and allows our clients to maintain a smaller number of database professionals with a higher skill level to maintain their systems. I believe this will only become more relevant as we deliver our first major SQL 2008/LINQ product early next year.
"

Send in your thoughts here.

Featured White Paper(s)
Accelerating Applications Beyond the Speed of Light
Application acceleration and offline networking for distributed enterprises…. (read more)

Finding and Fixing Bad SQL in Microsoft SQL Server 2000
This article will teach you the basic techniques used to find and fix poorly performing SQL statements (usually SELECT statem… (read more)

Data modelers – 7 Steps to Success – Building a Collaborative Team Environment
Your data models are brilliant… but only if the DBAs and developers are on the same page. Often, there is a significant dis… (read more)

Building Cost Effective High Availability Infrastructure with Microsoft SQL Server
Database traffic management is a simple, low-cost approach to ensuring persistent data availability and rapid database scalab… (read more)