How do you beta a service pack?

  • As we all know, Microsoft frequently has beta programs for service pack releases.

    My question is for those who regularly partake. What methodology do you use to uncover potential issues? How proactive are you in the discovery process? Or do you simply install the service pack on a test box, run your app and report anything out of the ordinary?

    Thanks in advance. Be great!

    Mike

    Be great!


    Be great!
    Michael

  • I like to review the readme.txt to see if they've fixed anything that might be something I've had a problem with or just is close to an area thats important. I use replication a lot so Im always checking what bugs have been fixed there, even if I have no problems..that I know about anyway. Beyond that I install and run, maybe do some testing on a specific bug if its a fix I need. Betas are supposed to be fairly solid, they are looking to test on a wide variety of hardware and software, so just installing and running is pretty good. Certainly if you have time it makes sense to really put it to the test, but not required. As far as I can tell anyway.

    Andy

    http://www.sqlservercentral.com/columnists/awarren/

  • Be sure you have test servers that you can afford to have down while you reinstall first.

    Then follow Andy's advice. Read about it, and install it. You will probably have to at some point to get support, so you may want to get a head start, but only if the issue are relevant. If not, then do it if you feel like helping others.

    Steve Jones

    sjones@sqlservercentral.com

    http://www.sqlservercentral.com/columnists/sjones

  • Installing and running is done for the most part. Not really to many issues from a Service Pack with hardware unless they change drive support in SQL. Generally they give you a list of things fixed and you try to test on many different Win OS platforms to see if any fails (I do Win 98, NT4, 2000 and XP myself). Also variations of key hardware RAM, CPU to see if any type of memory errors occurr. Then you want to do revision testing, making sure the update does not inadvertently undo a previous fix. Then you want to test issues oyu may have reported that have not been patched as of that point and you want to try to find any new issues that have never happened before. You however do not need to go to extremes in testing but do need to make sure does not potentially create issues for you.

    "Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

Viewing 4 posts - 1 through 3 (of 3 total)

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