Post reply

Watch Your Support

  • July 7, 2007 at 11:47 am

    #174311

    Help Key

    I hadn't seen this, but it is definitely worth knowing. On Tuesday, support for SQL Server 2000 Service Pack 3a will end. So if you have servers that haven't been updated to Service Pack 4, you better get testing to ensure that any support calls you need to make can be handled. Otherwise the first thing they'll require is you update to SP4.

    One more thing to really think about is that support for the SQL Server 2005 RTM version ends on Jul 10 as well. I've known for years that the first thing support usually wants you to do is update to the latest Service Pack, and I've had a few calls where they said that was the resolution. But this means that you won't get support on this level anymore. So test those Service Packs and get them deployed.

    High Performance Engine

    This week there were a number of interesting blog posts on performance and it's good to see people making attempts to find ways to improve performance or determine what might influence it the most. Tony Rogerson in particular has a very interesting post on the procedure cache and how you might improve performance with application design,

    Lastly: Why does an ATM PIN code have 4 digits? The guy who invented the machines asked his wife and she could only remember 4 digits. I know some banks are different, but the important thing here isn't the 4 digits.

    It's the impact a spouse can have on your career

    Steve Jones

    Steve's Pick of the Week : Tour the NCSA with its hardware MTBF of 6 hours. That's right 6 hours!

  • July 11, 2007 at 7:02 pm

    #718832

    “Tony Rogerson in particular has a very interesting post on the procedure cache and how you might improve performance with application design,”

    The SQL Server procedure cache is one of the least known part of SQL Server, in 2000 it can grow to 800megs of ram and unless you use the system stored procedure sp_procoption it can remove your stored procedure from the cache based on lack of use.  The reason is the least used algorithm that is used to manage it, if a stored procedure is not used for some time it removes it to make room for others that may need the space.

    Kind regards,
    Gift Peddie

Viewing 2 posts - 1 through 2 (of 2 total)

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