Post reply

Service pack 4 for SQL server 2000

  • June 6, 2006 at 7:38 pm

    #61780

    Hi All,

    I've been checking the Microsoft website for Service pack 4 for SQL 2000, but too much information is just confusing me too much.

    Could you tell me if I need to set up a new SQL server 2000, then do I install the following:

    1. Install SQL server enterprise ed. 2000
    2. Install service pack 4.

    Does the new SQL server 2000 enterprise edition come with the service pack 4? If not, should I install service pack 4? One of my friends was saying that since service pack 4 is quite new, it might have some issues with the release. So, wait for some time and then install the service pack later. Is this correct? Will installing the service pack later be easier or doing it now easier?

    Is there a website that explains the above in simple terms?

    Please help.

    Thanks heaps in advance.

  • June 7, 2006 at 1:17 am

    #642195

    If you are installing new instance its better to install with sp4 as there won't be any other patches from MS as sql 2005 is already in market.

    sp4 is more then 1 years old so I don't see any problem in installing it, I have sp4 running in my prod db since long till now no problem.

     

    ------------
    Prakash Sawant

    http://psawant.blogspot.com

  • June 7, 2006 at 6:40 am

    #642245

    Cannot blame you.I dragged my feet too.But was bitten by joining a couple of views .After a week of calling microsoft and the hardware vendors I installed SP4 as  a last resort and guess what ?

    If my opinion is anything to go by then go right ahead .The service packs and hotfixes mostly take care of identified problems and may even add  features

    Mike

  • June 7, 2006 at 4:52 pm

    #642404

    Thanks Guys, it was very helpful, and cleared my mind for any doubts I had.

  • June 8, 2006 at 3:07 am

    #642455

    There are a few issues with SP4, listed below.  All of them have fixes or workarounds except d) which you have to live with.  I would recommend applying the latest SP4 hotfix rollup if you are building a new environment.  The rollup is hard to find on the MS site, but Google gives you a good link.

    a) SP4 rtm does not allow full use of AWE memory.  A hotfix is available for this that is included in the hotfix rollup package.
     
    b) SP4 introduces restrictions on what registry keys can be accessed by xp_regread and some other routines.  KB article 887165 describes a number of ways you can persuade xp_regread, etc, to access the keys we want to use.
     
    c) Some people have reported more blocking issues with SP4 than SP3.  The documented reason for this is that SP4 is better at reporting short-term blocking than SP3 was, and all that is being seen is what really happened in SP3 but was not shown.
     
    d) SP4 is more restrictive in performing implicit data type conversions for predicates than SP3.  SP3 would do its best to convert data types, even if this resulted in truncation of data and unexpected results from the query.  SP4 tries to only get good results from the query, and this can result in some SQL statements being rejected in SP4 that 'worked' in SP3, or some queries performing slower.  There is still some discussion in the forums about if some of the restrictions should be seen as bugs or good design, but the only sure fix is to re-code offending queries to avoid implicit conversions.  However there is a new trace flag 9059 which will cause SP4 to perform data type conversions in the same way as SP3, including the risk of truncation and unexpected results.
     

    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 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply