|
 |
|
Browse Blog Posts by Tags
-
Those of you who read my blog regularly may have noticed the previous post and maybe more important the comments on this post. Somehow I think we were not the only ones having this questions and remarks. As a follow-up please read the following blog posts as they are very relevant to the discussion....
-
The guys @ Microsoft have been busy improving the quality of SQL Server even more. First of all CU7 was released (Build 3239) here . As usual this means CU8 has been announced here . I know there has been a lot of requests from the customers to release Service Pack 3 for SQL Server 2005. Although I see...
-
With every release comes a new announcement of course. http://support.microsoft.com/kb/949095/
-
It is out there! The build number is 3228. http://support.microsoft.com/kb/946608/
-
Because CU5 is released here is the next announcement . The question is of course how many of you have already implemented CU5?
-
It is out there! The build number is 3215. http://support.microsoft.com/kb/943656/
-
We are in the process of gradually upgrading our servers to CU4 now (build 3200) and here is the next announcement . I know many people think they are messing about with SQL Server 2005 and that it has more bugs than other products but this is not the case. Releasing this many hotfixes is all part of...
-
It is out there! We are at the nice round build 3200. Same as with CU3 there is also no download available. http://support.microsoft.com/default.aspx/kb/941450
-
Probably a bit early since the previous package is not yet available, but knowledge is power they say. http://support.microsoft.com/kb/941450
-
Keep an eye out for KB939537 which will be the next cumulative hotfix package for SQL Server 2005 SP2. Unfortunately the fix itself is not yet available for download. Any guesses on the build number? I'm going for 3193 :-) *EDIT* It is build 3186 so I was pretty close but too pessimistic ;-)
-
Reading this and this post reminded me of our very bad experience with the USERSTORE_TOKENPERM cache. When we ran into our USERSTORE_TOKENPERM issue last year there was no real awareness of the problem yet (SQL Server 2005 x64 - Enterprise Edition Build 2153). It was so bad we had to revert to SQL Server...
-
We're at build 3175 with KB936305 , the hotfix is not publicly available though. For an overview of the hotfixes released after SP2 check out KB937137 , it contains the list of fixes per build.
|
|
|
|
|
|
|