Service Pack 2a

  • Andy Warren

    SSC Guru

    Points: 119676

  • MrAkki

    SSCrazy

    Points: 2574

    Hi Andy,

    I can not find the KB entree in English. The only KB I get is in German, and it is badly translated... It seems Microsoft doesn't have a good translation software... , and there is no link to the English version of the KB....

    Would it be possible for you to post the link to the English KB?

    Thanks,

     

    Thorsten

     

  • colin.Leversuch-Roberts

    SSC Guru

    Points: 52551

    this may help  http://support.microsoft.com/kb/933508

     

    [font="Comic Sans MS"]The GrumpyOldDBA[/font]
    www.grumpyolddba.co.uk
    http://sqlblogcasts.com/blogs/grumpyolddba/

  • MrAkki

    SSCrazy

    Points: 2574

    Thanks,

    but I still get the badly translated german version of the KB????

    Any idea???

    Thanks.

  • Steve Jones - SSC Editor

    SSC Guru

    Points: 715889

    Must be something switching you on the MS site because of your browser. Are you in Germany?

  • colin.Leversuch-Roberts

    SSC Guru

    Points: 52551

    SUMMARY

    <script type=text/javascript>loadTOCNode(1, 'summary');</script>

    If you apply the initial release version of Microsoft SQL Server 2005 Service Pack 2 (SP2), existing SQL Server 2005 maintenance plans and Integration Services packages that contain cleanup tasks run those tasks at shorter intervals. The issue occurs only if all the following conditions are true:

    You downloaded SQL Server 2005 SP2 before March 05, 2007, and installed that download package.
    You use SQL Server 2005 maintenance plans or Integration Services packages.
    Those plans or packages include History Cleanup tasks or Maintenance Cleanup tasks.

    The resolution for this issue is described in the "Resolution" section.

    Users of SQL Server 2000 legacy maintenance plans and users who downloaded SP2 after March 05, 2007 are not affected. On this date, SQL Server 2005 SP2 was refreshed to include an update that avoids this issue.

    Note This problem only affects the main SQL Server 2005 SP2 packages. These packages use the following naming convention:

    SQLServer2005SP2-KB921896-ProccessorType-Language.exe

    This problem does not affect SQL Server 2005 Express Edition or SQL Server 2005 Feature Pack packages.

    The following table lists the file version of the affected version of the SQL Server 2005 SP2 package together with the refreshed version of this package.

    Package type File version
    Affected self-extracting executable file 9.0.3042.0
    Refreshed self-extracting executable file 9.0.3042.1

    Important The fix that is included in the refreshed version of the SQL Server 2005 SP2 package is included in all later SQL Server 2005 hotfix packages.

    Back to the top

    BACKGROUND

    <script type=text/javascript>loadTOCNode(1, 'summary');</script>

    When SQL Server 2005 was released, cleanup intervals were measured in days, in weeks, in months, or in years. In response to customer feedback, SQL Server 2005 SP2 includes significant enhancements to maintenance plans. These include an enhancement that lets users specify the cleanup interval in hours.

    The change in intervals caused the initial release version of SQL Server 2005 SP2 to interpret cleanup task intervals differently than the original settings. This behavior can cause cleanup tasks to delete information earlier than intended.

    The change in intervals also caused different interpretations of cleanup task intervals if you mixed versions of the tools and of the servers. Although the original release version of SQL Server 2005 (the RTM version), SQL Server 2005 Service Pack 1 (SP1), and the SQL Server 2005 SP2 refresh are compatible, mixing these versions with the initial release version of SQL Server 2005 SP2 could lead to task intervals being interpreted incorrectly in new and modified tasks:

    If you create or modify plans or packages by using the original release version of SQL Server 2005, SQL Server 2005 SP1, or the refreshed SQL Server 2005 SP2 tools, and then you run them on the initial release version of SQL Server 2005 SP2, most cleanup task intervals are shorter than intended. This behavior could delete information earlier than intended.
    If you create or modify plans or packages by using the initial release version of SQL Server 2005 SP2 tools and then run them on the original release version of SQL Server 2005, SQL Server 2005 SP1, or the SQL Server 2005 SP2 refresh, cleanup task intervals are longer than intended. This behavior could retain information longer than intended.
    If you create or modify plans or packages by using the initial release version of SQL Server 2005 SP2 tools, select the year interval, and then open the task in the original release version of SQL Server 2005 or in SQL Server 2005 SP1, the following error can occur:

    InvalidArgument=Value of '4' is not valid for 'SelectedIndex'.

    Parameter name: SelectedIndex (System.Windows.Forms)

    If you ignore the message and save the package, the original release version of SQL Server 2005 and SQL Server 2005 SP1 misinterpret the cleanup interval as days, and information is deleted earlier than intended.

    Back to the top

    RESOLUTION

    <script type=text/javascript>loadTOCNode(1, 'resolution');</script>

    If you have not installed SQL Server 2005 SP2

    <script type=text/javascript>loadTOCNode(2, 'resolution');</script>The original release version of SQL Server 2005 and SQL Server 2005 SP1 do not have this issue, and the current SQL Server 2005 SP2 download is updated to resolve this issue. If you have not installed the initial release version of SP2, you can download the current release and install it.

    Note If you try to apply the SP2 refresh over a previous SP2 installation, no files are updated. Instead, use the general distribution release (GDR) update below.

    Back to the top

    If you downloaded SQL Server 2005 SP2 before March 05, 2007

    <script type=text/javascript>loadTOCNode(2, 'resolution');</script>If you downloaded SQL Server 2005 SP2 before March 05, 2007, apply the general distribution release (GDR) update for those SQL Server 2005 SP2 installations. The GDR update is available at the Microsoft Download Center:

    After you apply this GDR update, you might have to restart the computer.

    The GDR update corrects the interpretation of cleanup tasks that were created by using the original release version of SQL Server 2005 and by using SQL Server 2005 SP1. If you created or edited maintenance plans or Integration Services packages by using the initial release version of SQL Server 2005 SP2, you must verify and update the cleanup task intervals after you apply the GDR update. If you do not do this, cleanup tasks will retain data longer than intended.

    To verify and update cleanup task intervals, follow these steps:

    1. Open the maintenance plan or the Integration Services package.
    2. Open each cleanup task.
    3. Adjust the cleanup interval to the correct value.
    4. Save the plan or the package.

    Files that are updated by the GDR update and by the SP2 refresh

    <script type=text/javascript>loadTOCNode(3, 'resolution');</script>

    Updated file Initial SP2 release version Post-GDR update and SP2 refresh version Location
    Microsoft.SqlServer.MaintenancePlanTasks.dll 9.00.3042.00 9.00.3043.00 %ProgramFiles%\Microsoft SQL Server\90\DTS\Tasks and the global assembly cache (GAC)
    Microsoft.SqlServer.MaintenancePlanTasksUI.dll 9.00.3042.00 9.00.3043.00 GAC

    Tests to determine which version of SQL Server 2005 SP2 is installed should inspect the file in %ProgramFiles%\Microsoft SQL Server\90\DTS\Tasks. If the SP2 file version is greater than or equal to 9.00.3017.00 and less than 9.00.3042.00, the SP2 version is pre-release and you should install the SP2 refresh. If the file version equals 9.00.3042.00, the version is the initial SP2 release, and you should apply the GDR update.

    The GDR update detects file versions and updates the files as necessary. However, if you need to verify file versions, you can use Microsoft Windows Explorer or the Filever command-line utility:

    To check the file version on individual computers, open Windows Explorer, right-click the file, select Properties, and then click the Version tab.
    To help with checking file versions on many computers, the Filever command-line utility is available. For more information about the Filever command-line utility, click the following article number to view the article in the Microsoft Knowledge Base:

    913111 (http://support.microsoft.com/kb/913111/) How to use the Filever.exe tool to obtain specific information about a file in Windows

    Back to the top

    WORKAROUND

    <script type=text/javascript>loadTOCNode(1, 'workaround');</script>

    If you do not apply the GDR update, you can manually update your cleanup task intervals by using matching server and tool versions. If you later apply this or any subsequent SQL Server 2005 update, you must verify and update cleanup task intervals. For this reason, we recommend that you apply the GDR update.

    [font="Comic Sans MS"]The GrumpyOldDBA[/font]
    www.grumpyolddba.co.uk
    http://sqlblogcasts.com/blogs/grumpyolddba/

  • Steve Jones - SSC Editor

    SSC Guru

    Points: 715889

    Here's some of it.

    SUMMARY

    If you apply the initial release version of Microsoft SQL Server 2005 Service Pack 2 (SP2), existing SQL Server 2005 maintenance plans and Integration Services packages that contain cleanup tasks run those tasks at shorter intervals. The issue occurs only if all the following conditions are true:

    • You downloaded SQL Server 2005 SP2 before March 05, 2007, and installed that download package.

    • You use SQL Server 2005 maintenance plans or Integration Services packages.

    • Those plans or packages include History Cleanup tasks or Maintenance Cleanup tasks.

    The resolution for this issue is described in the "Resolution" section.

    Users of SQL Server 2000 legacy maintenance plans and users who downloaded SP2 after March 05, 2007 are not affected. On this date, SQL Server 2005 SP2 was refreshed to include an update that avoids this issue.

    Note This problem only affects the main SQL Server 2005 SP2 packages. These packages use the following naming convention:

    SQLServer2005SP2-KB921896-ProccessorType-Language.exe

    This problem does not affect SQL Server 2005 Express Edition or SQL Server 2005 Feature Pack packages.

    The following table lists the file version of the affected version of the SQL Server 2005 SP2 package together with the refreshed version of this package.

    Package type File version

    Affected self-extracting executable file 9.0.3042.0

    Refreshed self-extracting executable file 9.0.3042.1

    Important The fix that is included in the refreshed version of the SQL Server 2005 SP2 package is included in all later SQL Server 2005 hotfix packages.

    If you have not installed SQL Server 2005 SP2

    The original release version of SQL Server 2005 and SQL Server 2005 SP1 do not have this issue, and the current SQL Server 2005 SP2 download is updated to resolve this issue. If you have not installed the initial release version of SP2, you can download the current release and install it.

    Note If you try to apply the SP2 refresh over a previous SP2 installation, no files are updated. Instead, use the general distribution release (GDR) update below.

    Back to the top

    If you downloaded SQL Server 2005 SP2 before March 05, 2007

    If you downloaded SQL Server 2005 SP2 before March 05, 2007, apply the general distribution release (GDR) update for those SQL Server 2005 SP2 installations. The GDR update is available at the Microsoft Download Center:

    Critical Update for SQL Server 2005 Service Pack 2 (http://go.microsoft.com/fwlink/?LinkId=85124)

    After you apply this GDR update, you might have to restart the computer.

    The GDR update corrects the interpretation of cleanup tasks that were created by using the original release version of SQL Server 2005 and by using SQL Server 2005 SP1. If you created or edited maintenance plans or Integration Services packages by using the initial release version of SQL Server 2005 SP2, you must verify and update the cleanup task intervals after you apply the GDR update. If you do not do this, cleanup tasks will retain data longer than intended.

    To verify and update cleanup task intervals, follow these steps:

    1. Open the maintenance plan or the Integration Services package.

    2. Open each cleanup task.

    3. Adjust the cleanup interval to the correct value.

    4. Save the plan or the package.

    Files that are updated by the GDR update and by the SP2 refresh

    Updated file Initial SP2 release version Post-GDR update and SP2 refresh version Location

    Microsoft.SqlServer.MaintenancePlanTasks.dll 9.00.3042.00 9.00.3043.00 %ProgramFiles%\Microsoft SQL Server\90\DTS\Tasks and the global assembly cache (GAC)

    Microsoft.SqlServer.MaintenancePlanTasksUI.dll 9.00.3042.00 9.00.3043.00 GAC

    Tests to determine which version of SQL Server 2005 SP2 is installed should inspect the file in %ProgramFiles%\Microsoft SQL Server\90\DTS\Tasks. If the SP2 file version is greater than or equal to 9.00.3017.00 and less than 9.00.3042.00, the SP2 version is pre-release and you should install the SP2 refresh. If the file version equals 9.00.3042.00, the version is the initial SP2 release, and you should apply the GDR update.

    The GDR update detects file versions and updates the files as necessary. However, if you need to verify file versions, you can use Microsoft Windows Explorer or the Filever command-line utility:

    • To check the file version on individual computers, open Windows Explorer, right-click the file, select Properties, and then click the Version tab.

    • To help with checking file versions on many computers, the Filever command-line utility is available. For more information about the Filever command-line utility, click the following article number to view the article in the Microsoft Knowledge Base:

    913111 (http://support.microsoft.com/kb/913111/) How to use the Filever.exe tool to obtain specific information about a file in Windows

  • MrAkki

    SSCrazy

    Points: 2574

    Thanks a lot....

    Now, I understand what Microsoft tried to say...

     

    Yes I'm in Germany, that's probably why Mircrosoft assumes that I want to read the KB in German...

    Usually they give you the chance to switch to the English version, but somehow they forgot it...

    Thanks to all of you, this helps a lot...

    Thorsten

     

  • MrAkki

    SSCrazy

    Points: 2574

    Hi,

    I just figured out the right link to the english KB:

    http://support.microsoft.com/kb/933508/en-us

    I have to put an "/en-us" at the end of the link...

    That works....

  • cpyne

    SSC-Addicted

    Points: 462

    The Microsoft site is still calling it "SP2". Does anyone know if "SP2a" will be the official name for the service pack or was this just the author's guess?

    Thanks

  • Zubeyir

    SSCrazy

    Points: 2559

    They just updated the release date (date published) of the pack to 3/6/2007 and I guess the executable pack file properties will show file version 9.0.3042.1 instead of 9.0.3042.0

  • Steve Jones - SSC Editor

    SSC Guru

    Points: 715889

    As the author, it was a complete guess. I caught this late last night and in an hour of frantic searching (in between pausing the newsletter and getting it rebuilt), I couldn't find any "official" MS info other than the one KB article.

    I'm hoping they'll designate "a", but so far I haven't seen anything.

  • cpyne

    SSC-Addicted

    Points: 462

    Hi,

    I installed "SP2a" and ran select @@version, but I'm still seeing this...

    Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)

    Feb 9 2007 22:47:07

    Copyright (c) 1988-2005 Microsoft Corporation

    Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

    The DLLs listed in the article list the correct versions though... Could someone run select @@version and confirm if 9.00.3042.00 or 9.00.3042.01 is listed?

    Thanks

    Could someone

  • herman maes-268348

    SSC Journeyman

    Points: 98

    everything (reg-keys, exe-files, @@version...) is listing 9.00.3042.00 after upgrade with the new sp2.

     

     

  • colin.Leversuch-Roberts

    SSC Guru

    Points: 52551

    seems the new fix broke something else !! Personally I never use maint plans , I roll my own, now I know this was a good decision all those years ago < grin >

    [font="Comic Sans MS"]The GrumpyOldDBA[/font]
    www.grumpyolddba.co.uk
    http://sqlblogcasts.com/blogs/grumpyolddba/

Viewing 15 posts - 1 through 15 (of 17 total)

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