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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2006-08-31 : 10:37:26
|
| Pieter writes "After installing updates on our windows 2003 server, rebooted and then we had problems with the tempdb: could not load tempdb into RAM not enough free space, but we have 4GB of RAM. We changed the tempdb to run of a device, nolonger in RAM. Do you know what causes this and if there is a workaround for this problem. It's really affecting our production servers.ThanksPieter" |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2006-08-31 : 10:42:50
|
| 1) MS removed "tempdb in RAM" with SQL 7.0 because it was a bad feature. You should consider not using it anymore.2) It's unlikely MS will support or troubleshoot SQL 6.5 in this configuration, and if they do, they'll probably recommend not using this setting.3) Might want to think about upgrading to SQL 2000 or 2005, because at some point your app will outgrow the capabilities of 6.5. At this time, you can't upgrade directly to 2005, you'll have to move to 2000 first.Whatever performance improvement tempdb in RAM might be giving you (and I say *might*) you'll get a bigger improvement by upgrading SQL Server to a new version. |
 |
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2006-08-31 : 12:28:04
|
| I think you have already posted this same question several times, and received just about the same answer each time.Several people have pointed out that SQL Server 6.5 was never supported on Windows 2003.CODO ERGO SUM |
|
|
|
|
|
|
Problem starting SQL 6.5 TempDB error