SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Syncing Releases


Syncing Releases

Author
Message
Steve Jones
Steve Jones
SSC Guru
SSC Guru (145K reputation)SSC Guru (145K reputation)SSC Guru (145K reputation)SSC Guru (145K reputation)SSC Guru (145K reputation)SSC Guru (145K reputation)SSC Guru (145K reputation)SSC Guru (145K reputation)

Group: Administrators
Points: 145537 Visits: 19425
Comments posted to this topic are about the item Syncing Releases

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Carl Federl
Carl Federl
SSCertifiable
SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)

Group: General Forum Members
Points: 6840 Visits: 4352
As there do not appear to be significant dependecies between the Database Engine, Analysis Services, Reporting Services, Integration Services and the new Master Data Management, MS would be better off breaking the release schedule dependencies between these services. Then, a delay, show stopper flaw, or significant change in any of the services could be released on a different schedule.

SQL = Scarcely Qualifies as a Language
James Stover
James Stover
Right there with Babe
Right there with Babe (735 reputation)Right there with Babe (735 reputation)Right there with Babe (735 reputation)Right there with Babe (735 reputation)Right there with Babe (735 reputation)Right there with Babe (735 reputation)Right there with Babe (735 reputation)Right there with Babe (735 reputation)

Group: General Forum Members
Points: 735 Visits: 862
Let's run that list again:

SQL 2008 R2
Windows 2008 R2
Office 2010
Visual Studio 2010
(Windows 7)
(Exchange 2010)

You have to think about it; that's a big list. I would guess that 1/2 (or more) of the company are engaged in developing and selling those products in some way (design, dev, test, PM, marketing, etc.). I'm wondering if Microsoft hasn't had enough manpower to see a synchronized release of their flagship products until now. Sure, MSFT is a big company but we must be talking tens of millions of man-hours - could even be hundreds of millions - to do a fully synchronized release cycle of this size.

It will be interesting to see if they can do it successfully. It will certainly set the bar very high for future release cycles.


James Stover, McDBA

Chris Harshman
Chris Harshman
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10835 Visits: 4657
In a way, I'd have to agree with Carl in that there are already too many things tied into a release of SQL Server. While I can understand the desire of Microsoft to bundle in all those additional features with SQL Server to add value for the customers, a full release of SQL Server should be more about changes to the RDBMS.

Remember that products like SQL Server, Oracle, DB2, and others are aimed at corporations. Most corporations tend to value stability more than the latest wiz-bang features. While the database vendors don't want their products to seem stale, corporate mentality and an "if it ain't broke don't fix it" attitude would make a new full release of a product consideration for new projects and systems. Upgrading the information infrastructure of an existing system is generally seen as a major undertaking. I know for a fact that some companies still run SQL 2000 for major systems and are only now just considering moving to SQL 2005.
Steve Jones
Steve Jones
SSC Guru
SSC Guru (145K reputation)SSC Guru (145K reputation)SSC Guru (145K reputation)SSC Guru (145K reputation)SSC Guru (145K reputation)SSC Guru (145K reputation)SSC Guru (145K reputation)SSC Guru (145K reputation)

Group: Administrators
Points: 145537 Visits: 19425
Chris,

It's a balance and I'm not sure how to address it. Microsoft doesn't expect, in my mind, everyone to upgrade to the next release. What they likely think is they will have 30-50% each time, with some people upgrading every 3 years, some every 6.

The problem is that if you wait 5-6 years between releases, it's a big upgrade. There are so many feature changes that it can be a hassle to train your people, not to mention upgrade related software. It's also harder to test and know if it makes sense.

Do any of us want to develop one big piece of software every 3 years in our company? No, we want to be more agile, releasing more often, and vendors are doing this as well. They also have to work out pricing, support, etc., but by moving to shorter cycles, they can get a certain amount of people to move each time in smaller upgrades.

Oracle, DB2, etc. do this, but they do point releases, and Microsoft has gotten away from that in a marketing move. However I believe the IBM/Oracle force maintenance on you, so you are paying for the point releases in a different way.

I'd say that MS should offer discounts for upgrades, and perhaps include R2 for free if you have the "base" version.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Dan Guzman - Not the MVP
Dan Guzman - Not the MVP
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1336 Visits: 751
Considering all the new features they add each time with each product, and the amount of overlap, it's really about time.

With office 07 we saw OpenOfficeXML, but SSMS 2005 couldn't import it. Now we have 2008 reporting services, but VS2008 was released first, and doesnt have the report viewer (yet) These disconnects are the most frustrating to me. When you work with the rest of the system/organizations, many of these applications overlap, and when the features don't connect your stuck.

If I have specific features in one application that I like, but I can't use them because the other products it would work best with don't have that feature because it won't be relesaed until next year, then I'll just wait.

If they are released together, then I might buy them all, becuase I can use them all to upgrade my system. ie use the new SSIS to import OpenOfficeXML files, crunch, combine, split, modify, then display in my SSRS report viewer in VS 2008.

It's in Microsoft's best interest.
Summer90
Summer90
SSCertifiable
SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)

Group: General Forum Members
Points: 7117 Visits: 3831
We are falling WAY behind here. Most of our SQL Server stuff is still on SQL 2000 (stable and if it ain't broke don't fix it). We have a few 2005 and have not even looked at Win2008 or SQL 2008 and now R2 will be out next year followed by SQL 2011 the year after... WOW !
Chris Harshman
Chris Harshman
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10835 Visits: 4657
Steve,

I'm not arguing with you, although the expectation of 30-50% upgrades seems rather high. I'm just trying to convey the corprate mindset that I've seen in 15 years as a database professional for several different companies. They typically end up with a mixed environment, older systems on the version that was recent at the time that system was developed or had a major overhaul, and newer systems on the more recent versions.

More releases more often = bad idea in the corporate world, because it will be more different releases that the IS/IT department has to support simultaneously.
DPhillips-731960
DPhillips-731960
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1618 Visits: 801
I applaud the release, as it will help to push the 2008 series out there. Many wait for a second release for fear of problems and bugs, and this will mainstream it. 2008 has great enhancements especially in the BI sets. I look forward to this with much optimism.
Steve Jones
Steve Jones
SSC Guru
SSC Guru (145K reputation)SSC Guru (145K reputation)SSC Guru (145K reputation)SSC Guru (145K reputation)SSC Guru (145K reputation)SSC Guru (145K reputation)SSC Guru (145K reputation)SSC Guru (145K reputation)

Group: Administrators
Points: 145537 Visits: 19425
Chris,

I tend to agree with you. Most IT groups don't want to upgrade servers often. But they will look to new versions, and I think it's a good idea to do a few here and there. It is harder to support, but if you take care of your staff and limit turnover (easier to do if you try), they can support the old versions, plus they get to learn new things.

I think the expectation for SQL Server DBAs going forward is that you'll need to support 3 or 4 versions of the platform at any time.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search