On April 18th, Microsoft Senior VP of Server Technologies, Paul Flessner announced that Microsoft would be moving from a standard beta release cycle for SQL Server 2005 towards the more flexible Community Technology Preview (CTP) format.
<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />
This decision is significant for a number of reasons. First, it’s an indication that the much-awaited beta 3 release of <?xml:namespace prefix = st1 ns = "urn:schemas-microsoft-com:office:smarttags" />
The new April CTP is an excellent version to start your beta testing, if you haven’t already done so. In effect, it is the beta three release of SQL Server 2005. After speaking to several SQL Server program managers at Microsoft, I was impressed that a number of features (pending any major new findings, of course) are settling down to production or near-production quality.
The quality of the CTP and Microsoft’s innovative and flexible approach to supporting pre-RTM deployments is a boon to the community. You can now go forward with confidence that you’re working with a product very similar to the commercial release. Will changes occur in the bits? Undoubtedly. Will there be more CTPs before the GA release of SQL Server 2005? Certainly. (I’m beginning to sound like a Magic 8 Ball, here.) But you can also now implement production deployments of SQL Server 2005 Express Edition with the full backing of Microsoft.
The full version of SQL Server 2005 is soon to follow. Click on these hyperlinks to read case studies about how customers like Koehler Paper, MetaLife, and Summit Partners, are working with SQL Server 2005 today.
You can get the full beta of SQL Server 2005 if you have an MSDN subscription or if you participate in the Technology Adoption Program (TAP). (The TAP program, incidentally, is run by a friend of mine named