<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:s="http://www.techrepublic.com/search" xmlns:dc="http://purl.org/dc/elements/1.1/"  xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
    <title><![CDATA[Discussion on Are Quarterly patches a good idea on Database Servers? ]]></title>
    <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-222016]]></link>
    <atom:link rel="hub" type="application/rss+xml" href="http://pubsubhubbub.appspot.com/" />
    <atom:link rel="self" type="application/rss+xml" href="http://www.techrepublic.com/forum/discussions/102-222016/rss" />

    <description><![CDATA[]]></description>
    <language>en-us</language>
    <lastBuildDate>2013-05-22T22:30:49-07:00</lastBuildDate>
             

    <item>
        <title><![CDATA[No better way]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-222016-2230496]]></link>
        <description><![CDATA[Timing is the most important element here.  Long holiday weekends are a boon to this process and the curse to the IT people, but it has to be done.  I can't count the number of holiday weekends I've had to work on just these type  of projects.  It has become a way of life but a very important part of the customers business, keeping systems up to date without disturbing the normal flow of work or colliding with other neccesary procedures needed to keep users information up to date and not bogged down by balky systems and out of date data bases.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-222016-2230496]]></guid>
        <dc:creator><![CDATA[mjd420nova]]></dc:creator>
        <pubDate>Wed, 09 May 2007 11:38:45 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Database upgrade vs OS upgrade]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-222016-2230515]]></link>
        <description><![CDATA[The difference is scope.  Taking an individual PC down for an upgrade only affects its one user and can generally be completed in 10-15 minutes.  Not a big effect on productivity unless the patch breaks something.Taking a production database server down, on the other hand, can affect hundreds or even millions of users.  And database upgrades are _rarely_ in the 10-15 minutes category.  Most require several hours to apply the patches/upgrades and then recompile affected database objects.Is there a better way?  Should there be a better way?  Good questions.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-222016-2230515]]></guid>
        <dc:creator><![CDATA[blarman]]></dc:creator>
        <pubDate>Wed, 09 May 2007 11:18:56 -0700</pubDate>
    </item>
    </channel>
</rss>

