January 22, 2009 at 1:51 am
Hi All,
I know many of them would have installed SP3 and SP3 with CU1 for those who have their servers in SP2 with CU10 or CU11.
Can you please share your feedbacks on the SP3on 2005. Any issues like performance or any new bugs detected on the same.
January 22, 2009 at 2:46 am
I had one bug on log shipping with SP2, that was been fixed with SP3, apart from that i have installed SP3 on my warm server, dint roll out on production until now, testing on warm servers, till now i dint face any problems with my operations on SQL 🙂
January 22, 2009 at 1:03 pm
January 22, 2009 at 2:14 pm
Hi ,
I have installed SP3 for SQL server 2005( Std Edi.) It seems to working fine. And guess what i have installed this on Vista home Premium.
Hary
Thanks a lot,
Hary
January 23, 2009 at 1:05 pm
We seem to have a major issue with BULK_INSERT after the SP3 install without any CU. We will be putting a support call in to MS.
Our bulk loads used to take from 30 minutes to 1 hour. After the SP3 install, this same exact load now takes 3 hours, or longer.
This is a 2 NODE cluster. 4 AMD 64-BIT processors and 24GB of RAM. We're running 64-BIT Windows Server2003 and 64-bit SQL2005 Enterprise Ed.
It seems as through the db engine is seeing the indices, or using the indices differenently. This started happening the day after the SP3 install.
February 3, 2009 at 8:39 pm
The one bug I found in SP2, did not make it to SP3. 😎 I was told it will be fixed in CU12, due in Feb 2009. When creating a snapshot of a mirrored database on a server, the account creating the snapshot must be sysadmin. As per BOL, the user only needs to have dbcreator permissions, but if you try it with this security level, you will get a nasty core dump in your SQL log file. So for now, the user who creates a snapshot must be a sysadmin on that server.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply