Torsten Schuessler
Sapere aude! (aka tosc)
Sapere aude! (aka tosc)
Aaron Bertrand describes in his Blog some very interesting inaccessibilities which belongs to SP3 and CU#10 / CU#11 (CUs after SP2).
Take a look at his post:
http://sqlblog.com/blogs/aaron_bertrand/archive/2008/12/17/more-information-on-sql-server-2005-sp3-cumulative-updates.aspx
A small keynote from him :-) :
So, if you want to be up to date, my suggestion is to wait on SP3 until CU#1 is available. If you have CU#10 or CU#11 and you apply SP3, you will LOSE YOUR CHANGES from those CUs. There will be no warning; it will just happen. Do NOT say I didn't warn you!
So let us take a small time out of applying SP3 and wait until SP3 + CU is available :-)
CU
tosc
| Print article | This entry was posted by Torsten Schuessler on 2008-12-17 at 21:16:32 . Follow any responses to this post through RSS 2.0. |
backup «best practices» books bug ctp «cumulative update» datetime dmv ebook humor index indexoptimize integrity kbfix links loginproperty maintenance «ms sql server 2008» performance php profiler «reporting services» reviews «ross mistry» rtm «service pack» «service pack 3» «service packs» sharepoint sp_msforeachdb «sql 2012» «sql pass» «sql server» «sql server 2005» «sql server 2008 r2» «sql server 2012» «sql server builds» sqlcat sqlpass «sqlpass franken» ssms ssmstoolspack t-sql technet «technical note» tempdb tools troubleshooting upgrade whitepapers