July 26, 2005 at 6:56 am
Has anyone experienced any issues/problems in upgrading sql 2000 from SP3a to SP4? I'm thinking about the service pack upgrade, but I want to know of any issues, besides the AWE issue that Microsoft mentions, that could cause me to re-think my intensions.
Also, I still need to adminster a couple of sql 7.0 servers. Will the upgrade to sp4 affect the Enterprise Manager client tools?
Any feedback is appreciated!
July 26, 2005 at 8:44 am
Most important thing to do before installing SP4....
Was your SQL Server instance/db created by a third-party application? If so, check with them first before installing SP4. SP4 changes the way the version is reported. Some applications might not be able to 'read' the new versioning and might think it's not upgraded properly. (the new version numbering is in the 2000's.)
-SQLBill
July 26, 2005 at 12:33 pm
We verified with our software vendors that they didn't have any issues, and have installed it on 2 servers so far. No problems to report .... very easy.
July 27, 2005 at 12:30 am
Also, I still need to adminster a couple of sql 7.0 servers. Will the upgrade to sp4 affect the Enterprise Manager client tools?
There should not be any problems with that.
July 27, 2005 at 5:27 am
There is a problem for sure gentlemen. If you install a named instance in the same computer (after you have installed the SP4 for your default server) it corrupts the SQLpath registry key which is located under "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup" and who nows what else.
Regards
July 27, 2005 at 7:37 am
I have went from SP3 to SP4 on one Prod server. No problems reported. I now have two new installs running SP4, no problems yet either.
July 27, 2005 at 8:42 am
What do you mean it 'corrupts the SQLpath registry key"?
-SQLBill
July 27, 2005 at 9:09 am
Hello Bill,
I mean that every time you install a named instance (MSDE) a letter is erased from the end of path contained in SQLPath.
for example
one install -> SQLPath becomes "C:\Program Files\Microsoft SQL Server\80\Tool"
second install -> SQLPath becomes "C:\Program Files\Microsoft SQL Server\80\Too"
and so on!
The value of course must be "C:\Program Files\Microsoft SQL Server\80\Tools"
This reg. key is needed for opening Quey Analyzer or Profiler through Enterprise Manager and Uninstalling your default instance (developer edition, personal...)
Cool ha!?!
Regards!
----------------------------------------------------
Greece will take cup again in Germany!!!!
July 27, 2005 at 9:35 am
Check out http://www.microsoft.com/sql/downloads/2000/sp4.mspx They posted a hotfix for the AWE problem.
Terry
August 31, 2005 at 4:00 pm
I just spent 4 hours on the phone with Microsoft on this one ... damn, I knew I had read about it in the recent past but could not remember where ... While working with the MS PSS tech executing 'stuff', filemon/regmon turned up a bad path error ... 'bingo' ... once I found the discussion page here again I then told the tech at MS of the issue ... the MS PSS tech replied after searching of internal information that this issue (path truncation) is a documented (internally only) but not published 'bug' ... I wonder why ??? Well, being one to share information I sent them the URL to this discussion !
My hats off to all who contribute to this site !!!
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply