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 |
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2002-04-03 : 20:12:24
|
| This post is in reference to http://www.sqlteam.com/Forums/topic.asp?TOPIC_ID=14562I'm running a INSERT INTO ... SELECT statement that will move about 2.5 million rows (4GB's of data) from one database to another. When I ran this on my production box, it seemed like any other query against that box (even on other databases) would not run. The CPU's were at about 8-10% and RAM was holding steady at about 1GB's used.On the other hand, I do something similar on my local pc, it seems to run both queries just fine, even while playing MP3's and surfing SqlTeam.com.Is there some setting I have messed up on my production box? It's SQL 2000, with 3GB's of RAM and Dual Xeon 700'sMichael |
|
|
Jay99
468 Posts |
Posted - 2002-04-04 : 09:13:30
|
quote: would not run
as in error msg or just no response . . .Jay<O> |
 |
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2002-04-04 : 09:30:41
|
| I don't think it's a performance problem for the pc....more a timeout/lockout problem on running multiple queries...when one of the is a INSERT INFO .... SELECT FROM....i believe it's something do do with either logging, or locks on temp tables....I think i read here, that BCP for one, locks 'system' tables....maybe something similiar is happening here....i think this topic (or something similiar) came up before...search???...keywords...."insert into", "locks", "timeout"??? |
 |
|
|
|
|
|