Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
cjp
Yak Posting Veteran
69 Posts |
 Posted - 2010-04-08 : 02:45:59
|
| I am using SQLS 2005 SP 3.A few days ago, I had a blue screen of death. The error message referred to a process called battc.sys (I haven't been able to find out what this is). My computer supplier said that there is a Microsoft hotfix for this, rolled up in XP SP 3 (I use XP Pro 64-bit as my OS, currently at SP 2).I have been warned that some people report problems with Sequel Server after loading XP SP 3 on top of SQLS 2005 SP 3, but I have no detail about this - just rumours.Can anyone clarify this? I find Microsoft's technical literature fairly baffling, so I thought I should ask here.Is it safe to load XP SP 3 or might I need to remove SQLS, load the OS patch and then re-install SQLS?By the way, I use XP instead of Windows Server because the latter is so poor as a desktop OS - and I need a desktop OS.Thanks.Chris |
|
|
torob417
Starting Member
1 Post |
|
|
cjp
Yak Posting Veteran
69 Posts |
Posted - 2010-04-20 : 05:23:43
|
| Thanks for this link - sorry for the delay in acknowledging the reply but I have been away.It seems to me that the safest (and most painful) route is to uninstall SQL Server, load up XP SP3 and then re-install SQLS with its service releases.Chris |
 |
|
|
cjp
Yak Posting Veteran
69 Posts |
Posted - 2010-05-13 : 05:11:58
|
| Just to update users of this forum.The hotfix referred to in the link posted previously has both good news and bad news. In our experience, the good news is that the hotfix appears to work if it installed over a pre-existing installation of SQL Server 2005 at SP 2 (ie before loading SP 3).The bad news is this: we had a new computer built for us, and the manufacturer installed the hotfix before supplying the computer. When a colleague tried to install SQL Server 2005, problems arose: the installation never requested disk 2 and, at the end, the required system files (eg master db) were present but there was no way to address them - all that was available was the configuration manager.We removed the hotfix and the installation of SQL Server then proceeded normally.It seems, therefore, that advice to use this hotfix should be nuanced: it is OK to install it over SQL Server 2005 (at SP 2) but not OK to install it before installing SQL Server.I think that an alternative approach is to say that SQLS 2005 SP 3 may not be required for everybody. I am not certain of this but I think that users of SQLS 2005 loaded within an affected OS (XP and Windows Server...) would be safe if they stuck to SP 2 for SQLS. People not using a laptop or a UPS would, I think, not be affected since the issue seems to relate to a device driver for a battery supply - but it would be unusual not to be on a UPS: I am sticking to SP 2 rather than loading the hotfix and then loading SP 3.Chris |
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2010-05-13 : 07:55:47
|
quote:
Originally posted by cjp
I think that users of SQLS 2005 loaded within an affected OS (XP and Windows Server...) would be safe if they stuck to SP 2 for SQLS.
No way. There are a number of bugs in SQL 2005 SP2 that were fixed in SP3. Plus, SP2 is not supported any longer. Call MS support and they will require that you're running SP3 before they'll help you.--Gail ShawSQL Server MVP |
|
|
|
|
|
|
|
|
Fix for blue screen of death