|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Rolling Back from build 3159 to build 3152Hi,
We were on build 3152 after hotfix 933097. Build 3159 hotfix 934459 was applied by accident. 933097 says it can be uninstalled by using Add/Remove programs and hotfix 934459 shows up in the list in Add/Remove programs. So can we rollback 934459 using Add/Remove programs? Thanks Chris Hi Chris
"Chris Wood" wrote: Although I haven't tried it you should be able to role back the files > Hi, > > We were on build 3152 after hotfix 933097. Build 3159 hotfix 934459 was > applied by accident. 933097 says it can be uninstalled by using Add/Remove > programs and hotfix 934459 shows up in the list in Add/Remove programs. So > can we rollback 934459 using Add/Remove programs? > > Thanks > > Chris > changed by this, although I am not sure why you should want to, as there would be risks to be taken into consideration. Test it on a non-production server first. John If it appears in add/remove programs, then the only reason it would break is
if there is a bug. Which, I guess, given the history of SP2, is why I agree with John's suggestion to try it in a test environment first. Not that it couldn't still break in production after passing in test, but hey... I do agree with John though, why do you *need* to roll back to 3152? Did you find behavior in 3159 that you need to revert? FWIW, if I accidentally patched a server with the highest build available, then that's where I would do my testing and bring all environments up to that build ASAP. Perhaps your situation is different. Show quote "Chris Wood" <anonym***@discussions.microsoft.com> wrote in message news:ez%23uSqPgHHA.3960@TK2MSFTNGP02.phx.gbl... > Hi, > > We were on build 3152 after hotfix 933097. Build 3159 hotfix 934459 was > applied by accident. 933097 says it can be uninstalled by using Add/Remove > programs and hotfix 934459 shows up in the list in Add/Remove programs. So > can we rollback 934459 using Add/Remove programs? > > Thanks > > Chris > Guys,
This is a Development server I am talking about. From what I see in Add/Remove programs I believe it would rollback to SP2 either at 3042 or 3050 build (We had applied SP2 (good 3042) and then applied 3050 and then applied 3152 as this was our path on our test server). If I look in Add/Remove programs it shows entries for 3159 and no entries for 3152 on this server. If I look on another server with 3152 it shows entries for 3152 in Add/Remove programs. Why go back? We had decided on build 3152 and discounted 3159 due to the various comments about these hotfixes. We had Development at 3152 and just upgraded Acceptance to 3152. With 3159 on Development we would need to upgrade Acceptance to 3159 now with more testing to keep our levels in sync. It is nice to see SQL2005 fixes show up in Microsoft Update but this can lead to patches being applied to a server by non DBA staff. Thanks Chris Show quote "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message news:%23sXUTBRgHHA.596@TK2MSFTNGP06.phx.gbl... > If it appears in add/remove programs, then the only reason it would break > is if there is a bug. Which, I guess, given the history of SP2, is why I > agree with John's suggestion to try it in a test environment first. Not > that it couldn't still break in production after passing in test, but > hey... > > I do agree with John though, why do you *need* to roll back to 3152? Did > you find behavior in 3159 that you need to revert? FWIW, if I > accidentally patched a server with the highest build available, then > that's where I would do my testing and bring all environments up to that > build ASAP. Perhaps your situation is different. > > -- > Aaron Bertrand > SQL Server MVP > http://www.sqlblog.com/ > http://www.aspfaq.com/5006 > > > > > > > "Chris Wood" <anonym***@discussions.microsoft.com> wrote in message > news:ez%23uSqPgHHA.3960@TK2MSFTNGP02.phx.gbl... >> Hi, >> >> We were on build 3152 after hotfix 933097. Build 3159 hotfix 934459 was >> applied by accident. 933097 says it can be uninstalled by using >> Add/Remove programs and hotfix 934459 shows up in the list in Add/Remove >> programs. So can we rollback 934459 using Add/Remove programs? >> >> Thanks >> >> Chris >> > > > It is nice to see SQL2005 fixes show up in Microsoft Update but this can Agreed. I found it particularly funny that some of these updates were > lead to patches being applied to a server by non DBA staff. deemed critical and, on a lot of systems, applied without consent. A Aaron,
Not sure if you used the SQL2005 BPA CTP but it flagged one of our servers for running a build (2047 - SP1) that was lower than build 2052 that fixed a memory leak in the CLR. I don't remember seeing anything in MU about this being a problem or in any other notification. SQL2005 seems a lot more loosy-goosey than SQL2000 ever did. Chris Show quote "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message news:uC1sThRgHHA.3960@TK2MSFTNGP02.phx.gbl... >> It is nice to see SQL2005 fixes show up in Microsoft Update but this can >> lead to patches being applied to a server by non DBA staff. > > Agreed. I found it particularly funny that some of these updates were > deemed critical and, on a lot of systems, applied without consent. > > A > Hi Chris
Show quote "Chris Wood" wrote: Have you considered moving to a new instance or different server with the > Guys, > > This is a Development server I am talking about. From what I see in > Add/Remove programs I believe it would rollback to SP2 either at 3042 or > 3050 build (We had applied SP2 (good 3042) and then applied 3050 and then > applied 3152 as this was our path on our test server). If I look in > Add/Remove programs it shows entries for 3159 and no entries for 3152 on > this server. If I look on another server with 3152 it shows entries for 3152 > in Add/Remove programs. > > Why go back? We had decided on build 3152 and discounted 3159 due to the > various comments about these hotfixes. We had Development at 3152 and just > upgraded Acceptance to 3152. With 3159 on Development we would need to > upgrade Acceptance to 3159 now with more testing to keep our levels in sync. > > It is nice to see SQL2005 fixes show up in Microsoft Update but this can > lead to patches being applied to a server by non DBA staff. > > Thanks > > Chris patch level you wanted? You could then remove the original instance if necessary. John Show quote > "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message > news:%23sXUTBRgHHA.596@TK2MSFTNGP06.phx.gbl... > > If it appears in add/remove programs, then the only reason it would break > > is if there is a bug. Which, I guess, given the history of SP2, is why I > > agree with John's suggestion to try it in a test environment first. Not > > that it couldn't still break in production after passing in test, but > > hey... > > > > I do agree with John though, why do you *need* to roll back to 3152? Did > > you find behavior in 3159 that you need to revert? FWIW, if I > > accidentally patched a server with the highest build available, then > > that's where I would do my testing and bring all environments up to that > > build ASAP. Perhaps your situation is different. > > > > -- > > Aaron Bertrand > > SQL Server MVP > > http://www.sqlblog.com/ > > http://www.aspfaq.com/5006 > > > > > > > > > > > > > > "Chris Wood" <anonym***@discussions.microsoft.com> wrote in message > > news:ez%23uSqPgHHA.3960@TK2MSFTNGP02.phx.gbl... > >> Hi, > >> > >> We were on build 3152 after hotfix 933097. Build 3159 hotfix 934459 was > >> applied by accident. 933097 says it can be uninstalled by using > >> Add/Remove programs and hotfix 934459 shows up in the list in Add/Remove > >> programs. So can we rollback 934459 using Add/Remove programs? > >> > >> Thanks > >> > >> Chris > >> > > > > > > > We have decided to move to 3159 as we could not determine what we would have
rolled back to and precious time was wasting. We have applications that need SP2 to run the way they did under SQL2000. Thanks Chris Show quote "John Bell" <jbellnewspo***@hotmail.com> wrote in message news:424ACA8C-313A-4C0E-87F1-9432BAD38C89@microsoft.com... > Hi Chris > > "Chris Wood" wrote: > >> Guys, >> >> This is a Development server I am talking about. From what I see in >> Add/Remove programs I believe it would rollback to SP2 either at 3042 or >> 3050 build (We had applied SP2 (good 3042) and then applied 3050 and then >> applied 3152 as this was our path on our test server). If I look in >> Add/Remove programs it shows entries for 3159 and no entries for 3152 on >> this server. If I look on another server with 3152 it shows entries for >> 3152 >> in Add/Remove programs. >> >> Why go back? We had decided on build 3152 and discounted 3159 due to the >> various comments about these hotfixes. We had Development at 3152 and >> just >> upgraded Acceptance to 3152. With 3159 on Development we would need to >> upgrade Acceptance to 3159 now with more testing to keep our levels in >> sync. >> >> It is nice to see SQL2005 fixes show up in Microsoft Update but this can >> lead to patches being applied to a server by non DBA staff. >> >> Thanks >> >> Chris > > Have you considered moving to a new instance or different server with the > patch level you wanted? You could then remove the original instance if > necessary. > > John > >> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in >> message >> news:%23sXUTBRgHHA.596@TK2MSFTNGP06.phx.gbl... >> > If it appears in add/remove programs, then the only reason it would >> > break >> > is if there is a bug. Which, I guess, given the history of SP2, is why >> > I >> > agree with John's suggestion to try it in a test environment first. >> > Not >> > that it couldn't still break in production after passing in test, but >> > hey... >> > >> > I do agree with John though, why do you *need* to roll back to 3152? >> > Did >> > you find behavior in 3159 that you need to revert? FWIW, if I >> > accidentally patched a server with the highest build available, then >> > that's where I would do my testing and bring all environments up to >> > that >> > build ASAP. Perhaps your situation is different. >> > >> > -- >> > Aaron Bertrand >> > SQL Server MVP >> > http://www.sqlblog.com/ >> > http://www.aspfaq.com/5006 >> > >> > >> > >> > >> > >> > >> > "Chris Wood" <anonym***@discussions.microsoft.com> wrote in message >> > news:ez%23uSqPgHHA.3960@TK2MSFTNGP02.phx.gbl... >> >> Hi, >> >> >> >> We were on build 3152 after hotfix 933097. Build 3159 hotfix 934459 >> >> was >> >> applied by accident. 933097 says it can be uninstalled by using >> >> Add/Remove programs and hotfix 934459 shows up in the list in >> >> Add/Remove >> >> programs. So can we rollback 934459 using Add/Remove programs? >> >> >> >> Thanks >> >> >> >> Chris >> >> >> > >> > >> >> >>  |
|||||||||||||||||||||||
Other interesting topics