blogs.conchango.com

So as suspected when I installed the new Security patch released by Microsoft for SQL 2005 sp2 that I mentioned this morning my build number has indeed shot up to 3233.  This places me somewhere between CU6 and CU7. Build 9.00.3228 was CU6 and 9.00.3239 is CU7. So just bear in mind that when you plop on your patch you are actually taking a ...

And so the great run comes to an end... For the full details of this incident please click here. N.B. This also affects Windows. However this is released under a different KB article. For the SQL 2005 sp2 KB article look at this link http://support.microsoft.com/kb/948108 For SQL 2000 GDR and MSDE 2000 KB article look at this one ...

Well David Litchfield thinks so. "Who he?" you ask. Well this article will explain all. Thanks to Dan Jones for the link.   -Jamie  

Over the last few years, I've been a consultant for a major IT Services company; worked for a UK-based support services company; contracted for Australia’s largest independent magazine distributor; worked in-house designing and project managing a Europe-wide infrastructure refresh for a major fashion design, marketing and retail organisation; and ...

I just stumbled across this 10-step plan to help secure SQL Server 2000 and thought it might be useful to note...