February 3, 2008 at 10:53 pm
Hi ,
We are planning for ‘in place’ SQL Upgrade from SQL 2000(Ent. Edition with SP4) to SQL 2005 Ent.Edition with SP2 for
1)Replication Distribution Server that serves to PULL subscriptions.
2)One for the Subscriber Cluster (Active Passive)Server (its distribution server already upgraded to SQL 2005)
We have gone through the requirements from Microsoft Technical Resource Guide but looking if somebody had any issues or any advice other than Upgrade Advisor reported before we move for Upgrade for both of above cases as some people indicated they had issue with Password Policy , Appreciate your reply…
February 4, 2008 at 9:32 am
The biggest problem I had with passwords (that I had a hard time finding documentation on) is that in SQL 2000 passwords are case INsensative by default (you can make them case sensative but they don't start that way). In SQL 2005 they are case Sensative. So a number of my linked servers and DTS packages all of a sudden stoped working because the passwords hadn't been typed in correctly.
Of course to make matters even better some of these users were so old no one remembered what the orriginal password was to begin with.
In the end it was just a brute force fix. I went in and "changed" the passwords to what I showed they were supposed to be. And then changed everything else .. linked servers, DTS packages etc .. to the corrected password. It was a pain but it worked. Of course I also took the opportunity to start switching over to Windows Authentication at the same time where I could.
Kenneth
Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]
February 5, 2008 at 5:44 am
Best of luck.. you will need it.
You need to plan for an in-place upgrade failing part-way through, leaving SQL completely dead. The only way out is to uninstall SQL then re-install. This does not often happen, but I have had this when testing upgrades.
My recommendation is to uninstall SQL 2000 then do a clean install of SQL 2005. Yoyu know you will have a system that is supportable in the long term.
PS I recently published http://www.codeplex.com/SQLServerFineBuild which has a section on upgrading from SQL Server 2000 to SQL Server 2005.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
February 5, 2008 at 3:23 pm
Thanks , also after running the upgrade advisor getting below in error reports
Object reference not set to an instance of an object
FTMULTIPLEINSTANCES
any body knows what does it mean?
February 6, 2008 at 3:00 am
I think it means the is a bug in Upgrade Advisor.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply