How do you handle software upgrades like SQL Server 2008? -


I am only asking this because I think that I am old, it becomes a very disappointing part of my job.

How do you handle new versions of the software, especially the software that coders and DBA use on a regular basis? It seems that when I flushed in SQL 2005, then SQL2008 will come and run and SQL 2010 will be here. I have forgotten to walk completely and it is not spatial for coders and DBA.

I'm not just for upgrading to upgrade, unless it has compelling functionality, I want to let go of it go away. Either way though, the software is becoming more frequent with release, I can not help but I think this is a wrong approach. Edited to add:
I think I am saying that there is not enough time to become an expert in the edition before releasing new editions.

itemprop = "text">

At least these upgrades must have a lot to release. Actually, I almost debate that the amount of Reliance release The amount of time between is equal to So SQL Server was 5 years from 2000 to 2005, and a lot changed, from 2005 to 2008, there was not much change. From 2008 to 2010, I'm guessing that there will not be much to learn there, I think the move is to stay on top of things. Because if you come back to some editions, then it can be a nightmare to catch things. Even if you play with it and do not use it in live projects, then you are probably ahead of many people.


Comments