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”.
1) The current support matrix for OSes is as follows:
2) Denali will support upgrading from these SQL Server versions:
3) The installer is going to block installation on unsupported OSes and it will block unsupported upgrade paths.
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.
Stick to 64-bit+ on servers but allow 32-bit including XP and upwards as clients.
We sell 95+ % to government in several European and Asia-Pacific countries. Requiring VISTA+ on clients prohibits pretty much every single customer from upgrading to Denali.
Blocking unsupported OS or upgrade path is fine. That's how we do already.
I would like to see support for Windows 2003. We have a ton of those running SQL 2005 and even some SQL 2008.
I would love to see the MS-SQL Server run on Unix,Linux. In the finance segment most of our Oracle Server run's on Unix for a long time. The DBA's don't like to switch to Windows Server for running the SQL Database ;)
I can see if a company still has XP and Windows 2003 for 2005 or even hosting 2008. Why would you expect Denali to run on old hardware? Seriously if your going to use Denali why not just use a newer OS. That doesn't mean a connection from an old server to a new server won't connect. It's just that Denali won't install on older OSes. Maybe I'm missing something.
64-bit only -> Windows 7/Server 2008 R2 and above.
Its time to not support the products and give them a reason to upgrade (more money to you and easier lives for developers such as my self).
I think at least workstation tools and SQL Express should support Windows XP, because there are still a large amount of such OS'es in corporate segment. Vista was awful and only small amount of companies moved. A lot of still using XP. You know how hard sometimes is to migrate all software (especially third party) to Windows 7. MED-V is good variant, but we should upgrade at least RAM for it. I know it is time to move, but it would be impossible to explain BOSS that if we want SQL Denali we should move to Windows 7 too.
A lot of my customers are still running SQL 2000 on Windows 2003, so I believe we should add this to the supportability.
Make it 64-bit only too. Exchange already is.
I'm going to disagree with the crowd, I think support for XP should be put in place. I'm on Windows 7 at home, but work is still on XP slowly moving to 7. Please support Windows XP. I use virtual machines for demonstrations and I like the smaller footprint that XP provides.
I don't see why we should expect new software to run on an outdated OS that can't be properly secured from all the new exploits. To run NEW software it should require the respective OS be the same that it was created for and nothing else. If Microsoft wants to drop support for something that is using old technology so that a new product can use new technology then so be it.
Everyone on XP should not expect that all new software being produced run on thier OS this is the life of software it will never be supported on all OS'es/Versions in the wild.
Get over it and move on with the rest of the world!
Upgrade blocked from
Microsoft SQL Server 2008 R2 (SP1) - 10.50.2769.0 (X64) Jun 24 2011 13:09:43 Copyright (c) Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
Was this planned?
Some of my development tools aren't even compatible with Windows 7 or Vista and not even having the option to test drive Denali at the client level is just a disappointment.
Sorry Denali, I'll have to give you a try in about 5 years when the companies in my field decide to upgrade.
In the meantime we will still be bound to third party solutions for Reporting Services inability to export > 255 columns.
I'm fine with the server restrictions, it's the client tools that will prevent adoption in my group. We're currently still on XP and with 70,000+ desktops to upgrade Windows 7 is a long ways off. So currently I can't even get the CTP installed to play with.
We won't be able to implement Denali LocalDB because of the XP limitation. We have no control over the computer that our agents use and the majority of them still use XP. If you want to force people to use Windows 7 so you can sell more product, give people a compelling reason to upgrade to Windows 7, don't force it on them. People develop a bad impression of your company.
And by the way, corporations will probably hang on to SQL 2000, 2005 and 2008 even longer now that XP is not supported.