August 8, 2011 at 9:22 am
Wow, my company has finally gotten on the ball and we are going to upgrade from SQL 2000 to 2005. Finally!!!! 2008 R2?????? 2015 Mayby 🙁
So here is my situation. I have 5 servers to update. I would like to do one at a time. This is the configuration. serverA is our main server, it has over 20 databases, and many of the databases are setup with replication. We are mainly using both Transactional and Merge relication.
I am looking for some good tutorials on this subject.and any suggestions will be appreciated
One question. Should I update the Publisher first, or should I update the subscribers first. I prefer to do the subscribers first since the bulk of them are at remote locations.
Thanks for your replys.
August 8, 2011 at 9:24 am
Looks like you've been down this road by why upgrade to 2005? It's already OUT of support.
It's the same amount of work to upgrade to 2008 R2 than it is to 2005 (well maybe 10% more).
August 8, 2011 at 9:31 am
My company does not want to pay the price for the 2008 License's, and the 2005 Licenses was provided to us by our sister company who did buy new 2008 R2 licenses.
August 8, 2011 at 9:42 am
How much are they looking to save by not purchasing the licenses?
The human capital required to do the upgrade can be extremely extensive and it might be good to avoid it for the next 10 years or so.
PS 2008 R2 is really ahead of 2k5, both in admin / compression and BIDS (just trying to giv eyou mor ammo)
August 8, 2011 at 11:00 am
I don't have a good tutorial for you on doing this upgrade for replication. By & large, upgrades are better and safer when they're done as a side-by-side upgrade, meaning you have a new server and you upgrade to that server instead of an in-place upgrade where you run the upgrade on the existing server. But, in your case, that adds to the overhead because then you'll need change replication each time you do the upgrade. That's going to be tough. In your situation, I think I'd risk the in-place upgrade, but you should have very good backups in place before you do it, just in case.
You have run the upgrade advisor right? Do you have a test system where you can validate your apps still work after the upgrade. We ran into several apps that after moving to 2005/2008 stopped working because of outdated ADO calls that had to be replaced in the code.
Finally, You're moving to a "new" 6 year old piece of technology. You really need to sit down with your company and talk about the support plan and the upgrade process because they really are making a mistake to not go ahead and upgrade to the latest version now. They're choosing to say that they want to upgrade again in only a few years rather than upgrade now and then be sitting on software with a decade of life left in it. Seriously, it's a mistake.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 8, 2011 at 11:05 am
... and with insurance and extra support that life cycle can be extended even further.
Yes licenses are pricey, but it comes with a loads of benefits.
August 8, 2011 at 11:22 am
Thanks for the response.
I have set up a test bed with tow servers. I don't think the upgrade part will be too dificult, but will soon find out. What concerns me most now, and as you pointed out, how all our Apps will do up against 2005 server. Hopefully I can convince the company to at least buy 1 new server to upgrade the Publisher. That way if there are a lot of issued I can drop back to the soo server until the issues have been resolved.
August 8, 2011 at 2:24 pm
My cie has a rather complexe ERP (only 1 DB & 1 app). The total man hours required to thoroughly test the application is in the 1000 of hours.
Let's put a simple figure for this. Let's say that this costs the cie ± 50 000$ in time.
Now unless we were running on a datacenter license or multiple cpus with enterprise, we'd really be losing money doing that upgrade twice.
Now imagine that with 20 applications. The license saving really has to be huge to make any kind of sense. Unless you testing is limited to just connect the app and see if the login works... which I hope you are doing better due diligence than that. 😉
August 9, 2011 at 12:18 pm
Thanks for all your concerns and suggestions. However I cannot convince my superiors to upgrade to 2008. I tried very hard to convince them prior to starting the topic.
Moving on into my upgrade, I just ran the upgrade Advisor for 2005 on one of my Test servers. I keep getting this error. "While drillthrough exists in Microsoft SQL Server 2005 Analysis Services, drillthrough settings are not migrated from previous versions of Analysis Services".
I have Googled this, but still don't know how to fix it. Do I need to fix it, or can it be ignored?
August 9, 2011 at 12:31 pm
This is where the 1000 of man hours come in.
Install 2005 trial (or the real thing if you have the license).
Run the upgrade and test the code.
You have to do this for well EVERYTHING.
I have never seen this error so I can't help further than this.
Viewing 10 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply