SQL Server 2014 was released to manufacturing on March 18, and became generally available April 1, 2014.
Sorry for Microsoft's ambitious release schedule, but no one I know or work with can or will undertake the cost and risk of upgrading so frequently. We're hopping releases - we're in the midst of completing our roll onto SQL 2012 now. We'll next take a look at SQL 2016 perhaps.
Appreciate your comments! Very understandable. Good luck on your SQL Server 2012 implementation. -- Jayleen, Editor
We have just completed conversion of SQL Server 2005 to SQL Server 2008R2. We have SQL Server 2012 installed on a couple servers to test and review it. A lot of planning on server hardware and operating systems before we begin to upgrade to SQL Server 2012 or 2014...
Yesterday we just installed SQL2012 on a test server to see what it looks like. We have about 85% of everything in SQL2008 and 5 of our last 7 dbs in SQL2000 will be upgraded to 2008R2 next month. The last 30 DBs in SQL2000 has been a 2 year long upgrade project.
We just recently made it to 2008 R2 with 2005 compatibility level. The time investment for this kind of upgrade in our environment is large, though I do plan on raising the topic in our department meeting today. I think the first task will be to get off of Windows Server 2003.
Agreed, upgrades are a big investment and budgets are a big consideration. Thanks for your comments! -- Jayleen Heft, Associate Editor
We still don't have anything running on SQL Server 2012. We have 7 databases still on SQL2000 with 5 of those scheduled to be upgraded in April.
Thanks for sharing! I don't think you're alone. So, what type of SQL Server Pro content is most helpful for you? --Jayleen Heft, Associate Editor
Anything SQL Server honestly. I want exposure to everything SQL Server.
Appreciate the feedback. We can do that! Thank you. --Jayleen
Browse back issues of SQL Server Pro, from January 2007 through the last issue published in April 2014. Find the back issues here.
Get answers to questions, share tips, and engage with the SQL Server community in our Forums.
Sponsored Introduction Continue on to (or wait seconds) ×