SQL Server 2012 Codenamed “Denali” Will Block Unsupported OSes and Upgrades

  SQL Server
Microsoft plans to limit the installation and upgrade options of the next generation of its data platform to supported technologies only.

Microsoft plans to limit the installation and upgrade options of the next generation of its data platform to supported technologies only.

According to Peter Saddow, Program Manager at Microsoft, customers won’t be able to install SQL Server 2012 codenamed “Denali” on an unsupported operating system.

Similarly, users won’t have the option of upgrading to SQL Server 2012 codenamed “Denali” from a version of the data platform that’s not covered by the supported official paths.

“The installer is going to block installation on unsupported OSes and it will block unsupported upgrade paths,” Saddow said.

Windows Vista SP2 or later; Windows Server 2008 SP2 or later; Windows Server 2008 R2 SP1 or later; and Windows 7 SP1 or later are the only platforms included in the current version of the support matrix for OSes.

According to Saddow, only the following SQL Server versions SQL Server 2005 SP4 or later; SQL Server 2008 SP2 or later and SQL Server 2008 R2 SP1 or later will allow customers to make the jump to Denali.

SQL Server 2012 codenamed “Denali” is very much still a work in progress, so the lists of supported platforms and upgrade paths could change. Microsoft is looking for input from SQL Server customers on the matter at hand.

“We are looking for feedback on three items for SQL Server Code Name “Denali”. First, are the supported OSes. Second, are the supported upgrade paths. Third, is the way the installer handles unsupported OSes and upgrade paths. Specifically we want to know if these will slow down your adoption of SQL Server Code Name “Denali”,” Saddow added.

“If the current support matrix for OSes, the current support matrix for upgrade, or the installation blocks will delay your adoption of of SQL Server called “Denali”, please provide this feedback to us! You can provide us this feedback by adding a comment below or submitting the feedback through the SQL Server Connect.”

1 Comment