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 |
|
Gopher
Yak Posting Veteran
83 Posts |
 Posted - 2007-01-12 : 03:30:14
|
| Hi AllI am currently having an issue with a SQL2000 server, the problem is that when I try to run a refresh program (which basically inserts about 1 million rows to various tables) it is taking about 14 hrs to run. This is obviously not good!I have worked out that the transaction throughput is about 20 rows a second. I have tried the same test on a SQL 2005 Express DB and the refresh only takes about 2hrs.Is there any way I can change the throughput, via SQL settings or is it worth attempting an upgrade to 2005?Thanks in advance!Gopher |
|
|
MuadDBA
628 Posts |
Posted - 2007-01-12 : 09:52:36
|
| Are both DBs on the same server using the same disk hardware and the same level of fault-tolerance. The difference could be as simple as one being in full recovery mode and one being in simple recovery mode. Also you need to make sure that the tables are identical, including indexes, table size, triggers, constraints, etc.If all of this is exactly the same, you can try adjusting the max async i/o settings on the sql 2000 server to see if that will help. |
 |
|
|
MohammedU
Posting Yak Master
145 Posts |
Posted - 2007-01-13 : 02:15:33
|
| From where you are loading these tables?Did you try using BCP?MohammedU |
|
|
|
|
|
|
Changing SQL 2000 transaction throughput?