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 - 2002-11-21 : 16:22:44
|
| Leandro writes "I have a application running on Oracle and MS SQLServer 7SP2, and I have a very complex (and BIG) SQL Statement. On Oracle the SQL runs perfectly, but I have a very pour performance and it end's up generating a lot of deadlocks and rollbacks on MS SQLServer 7SP2. This is causing some problems to my NT Box. Microsoft experts told me that this is a known issue on SQLServer 7SP2 because of its problem with the TEMPDB contention.Does anybody knows if this issue with the TEMPDB has been fixed on SQLServer 2000? I can't re-write the SQL Statement because it is a standard SQL I run on Oracle, Sybase and Informix, and this my cause problems (or a lot of re-writing time) for other customers.I really would like to know if MS has fixed the contetion of the TempDB on the new version of their SQLServer?Sincerely,Leandro Meinhardt" |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2002-11-21 : 16:33:47
|
| This is a duplicate post:[url]http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=21809[/url] |
 |
|
|
|
|
|
Pour performance due to the TEMPDB contention