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 |
|
jimsurf
Starting Member
18 Posts |
 Posted - 2006-10-27 : 18:00:53
|
| I just started with a new company that is using sql server with service pack 2. I am having a difficult time identifying what service pack 3 is supposed to fix. Does anybody have any specific information about why it would be important to upgrade from sp 2 to either sp3 or sp4?It appears that sp4 could cause some problems with existing asp applications if the connection strings are not set up correctly?? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-10-27 : 18:34:52
|
| Service pack 2 isn't supported by Microsoft anymore, so that's a huge negative to be using that sp. You can get the bug fixes and features added to the service packs from http://www.microsoft.com/sql.And no sp4 would not cause problems with existing asp applications if the connection strings were not setup properly. I'm not sure what you are referring to there, so please enlighten us if I'm mistaken. Connection strings don't have any knowledge of the service pack that SQL Server is using. Connection strings are related to the application only. They just reference the SQL Server.Tara Kizer |
 |
|
|
jimsurf
Starting Member
18 Posts |
Posted - 2006-10-27 : 18:57:01
|
| According to: [url]http://sqlserver2000.databases.aspfaq.com/what-do-i-need-to-know-about-sql-server-2000-sp4.html[/url]under the heading of Issues after install:connection strings may no longer be valid. Somewhere between the MDAC and SP4 updates, connection strings are a bit more strict. There are two styles for OLEDB: Conn.Open "provider=SQLOLEDB.1; server=?; database=?; uid=?; pwd=?;" Conn.Open "provider=SQLOLEDB.1; data source=?; initial catalog=?; user id=?; password=?;" While it requires more typing, I strongly suggest the latter. And I highly recommend you do not mix these methods, e.g. do not use server with initial catalog or data source with uid. It may work in most scenarios, but I have seen it fail. (You may also try dropping the .1 from the first parameter, if the rest of this doesn't help.) I am not sure if this is true, but if it is, a site may need to be retrofitted it the connection string were written poorly. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-10-27 : 19:18:59
|
| It's not sp4 that does this though. It would be MDAC. This would only impact you if the application was on the same server as the database server. sp4 does touch MDAC, but only on the database server.Tara Kizer |
|
|
|
jezemine
Master Smack Fu Yak Hacker
2886 Posts |
Posted - 2006-10-28 : 01:44:48
|
Maybe my memory is wrong, but wasn't the slammer worm fixed by sp3?This page seems to confirm my recollection:http://www.microsoft.com/technet/prodtechnol/sql/2000/downloads/default.mspxCertainly you want to protect yourself from that one. It was nasty.
SqlSpec - a fast, cheap, and comprehensive data dictionary generator forSQL Server 2000/2005 and Analysis Server 2005 - http://www.elsasoft.org |
|
|
|
|
|
|
|
|
SQL Server service packs