October 21, 2011 at 6:50 am
Volume wise we have about 40% of everything still in SQL2000, 20% in SQL 2005, and 40% in either SQL2008 or SQL2008R2.
Two of our most critical systems are active/passive Clusters on SQL 2000. One of them is planned to be upgraded 1st quarter next year to SQL2008R2. The other one will be app by app next year. The rest of the SQL2000 stuff will either stay there or slowly migrate to SQL2008 or be replaced by a new package. Some stuff will have to stay on SQL2000 because the vendor has gone out of business or we simply don't have support for it anymore.
I am finding it more and more that vendors do not support the latest version of SQL Server for 1-2 year after it is out. THEN you have to move to the latest version of the app which can take another 1-2 years... by then the next version of SQL Server is out.
The three year cycle is too quick as we all are going to get stuck supporting 3-5 versions of SQL Server.
PRODUCTION:
12 SQL2000
13 SQL2005
3 SQL2008
7 SQL2008R2
October 21, 2011 at 6:51 am
Oh by the way.... our 1,500 stores are running Win2000/MSDE2000. We just started replacing them with Win2008\SQL2008R2 Express.
October 21, 2011 at 6:52 am
Fortunately I have been able to convince everyone to go with SQL 2008 for all our systems, including getting it approved for compartmented classified systems that are still running Windows Server 2003 and XP on the clients. They're usually not speedy on approving new software, but it worked out for SQL 2008 and makes life so much simpler.
October 21, 2011 at 6:57 am
2000 - 7 (includes 2 SSRS only servers)
2005 - 11 (includes 1 SSRS only server)
2008 - 8 (includes 2 SSAS only servers)
2008 R2 - 6
October 21, 2011 at 7:02 am
We still support several 2000 and 2005 versions while installing 2008 R2 on all new servers, which we have several of. Of course that count several MSDE versions that are installed by applications and cross an number of versions also.
October 21, 2011 at 7:08 am
All of our servers from development through production are 2008. We went from 2000 directly to 2008 skipping 2005. We plan on skipping 2008 R2 and have not made a decision yet about 2012. Since we made it from 2000 to 2008 with no problem, I anticipate that we will probably skip 2012 and wait for the next one... As long as it's not 2012 R2 😉
October 21, 2011 at 7:08 am
The DTS packages are the biggest reason, we haven't migrated off of SQL 2000 sooner.
October 21, 2011 at 7:13 am
Last spring we got rid of our last SQL2000.
Majority of current apps are on sql2005 (and probably will be for some time), new ones are coming in on sql 2008
...
-- FORTRAN manual for Xerox Computers --
October 21, 2011 at 7:24 am
We've got about 40 instances of MS SQL server going back to v7. 2 running 7, 20 or so running 2000, 8-12 running 2005 (depending on whether you count passive cluster nodes), and 5 running 2008 R2. We just skipped over 2008. We've also got a few mysql, sybase sql, Oracle 9 and 11, etc. floating out there supporting specific apps. The 2 v7s do also support specific vendor apps. The 2000, 2005, and 2008 R2 are a mixture of in-house development and vendor apps. Some are stand-alone instances, some are multi-node MSCS clusters, some are VMs. All in all, it's a real mess trying to support as a system admin without a 'owner' for these systems.
October 21, 2011 at 7:57 am
At our Corporate Office we have...
30 x SQL 2000
149 x SQL 2005
18 x SQL 2008
12 x SQL 2008 R2
At our Remote Locations (Stores, Distribution Centers, etc) we have.
2270 Servers at 1135 Locations of SQL 2005. By the end of next summer with mirroring, that will be 4800 at 1200 locations and will probably be SQL 2008 or SQL 2008 R2.
October 21, 2011 at 7:58 am
I own a software company that has a niche product. A couple months ago, we released an update that requires SQL2005. Until then, we were compatible to SQL2000. We currently have 200 customers, each with an average of 5 DB's.
Our problem is that many customers own various versions of SQL server and we don't want to alienate any of them, so we try to be as backward compatible as possible. I have had customers tell me that they will not upgrade to a newer version of my software if it requires the newest version of SQL Server.
George Mastros
Orbit Software, Inc.
October 21, 2011 at 8:08 am
I have just the opposite problem, Management keeps buying software that is only compatible with SQL 2000, so we get stuck supporting it. Service Packs are an issue too. We need our Security team to back us up in order to force our vendors and app teams to accept the upgrade.
October 21, 2011 at 8:09 am
gmmastros (10/21/2011)
I own a software company that has a niche product. A couple months ago, we released an update that requires SQL2005. Until then, we were compatible to SQL2000. We currently have 200 customers, each with an average of 5 DB's.Our problem is that many customers own various versions of SQL server and we don't want to alienate any of them, so we try to be as backward compatible as possible. I have had customers tell me that they will not upgrade to a newer version of my software if it requires the newest version of SQL Server.
Wow, you JUST released a SQL 2005 certified version? You do realize that mainstream support for SQL 2005 has already ended. SQL 2012 will be out before we know it!
-----------------------------------------------------------------------------------
On April 12, 2011, SQL Server 2005 will transition from Mainstream Support to Extended Support, which includes:
Paid support (charged on an hourly basis per incident). Customers will no longer receive no-charge incident support and warranty claims, and won’t be able to request design changes or features.
Security update support at no additional cost.
Non-security related hotfix support will require a separate Extended Hotfix Support Agreement to be purchased within 90 days of the end of Mainstream Support – July 11th, 2011.
October 21, 2011 at 8:13 am
Out of the 115 or so servers we have at the County, along with trying to decide if we upgrade or not to a higher version, we also are striving to get any app/database that we can off hardware and into our VM environment. For myself, I handle 15 servers, some VM, mostly hardware. They include SQL 2000 SP4, 2005 Express, 2008 Std and Enterprise, 2008 R2 Std and Oracle 10. Fortunately most run just fine and it is a matter of monitoring space and backups. We would like to drop SQL2000, but that server has
9 different databases: small inhouse developed ones or older vendor ones that will never be upgraded by the vendor. The box with 2000 also has an instance of 2005 Express and I hope to slowly migrate even the older vendor databases over to 2005...some day!:cool:
October 21, 2011 at 8:16 am
We're a small shop 3 servers all on SQL 2008.
Viewing 15 posts - 31 through 45 (of 78 total)
You must be logged in to reply to this topic. Login to reply