i think the problem is the developes are using DELETE statement instead of TRUNCATE. Thats why the log file is so big.

you can't truncate the log in simple recovery model.

how can i truncate it in simple recovery model?

any ideas how to restore the statistics? or transfer from one table to another?

ken,

sqlserver 2000. thanks for the no_infomsgs tips

Yes. Sometimes just hitting certain size/rowcount threshhold can case this. Another potential reason is a large volume of insert/update/delete activity on tables as well.

This SP hasnt been changed...

Did my own testing.

1-select * into table1 from table2 is the best

2-insert table1 select * from table2

ASked the person in charged of AS400 Side. He told me AS400 is fine and nothing major has been changed.

Could not doing "Update statistics" decreate the performance?

1-what the job does.

It pulls data from a AS400, insert, delete, update.

2-Are there any other job(s) executing at that time ?

No, i run sql profiler, and i saw...

can someone move my post? to sql server 2000

sql server 2000?

running slow barely occacionally in the last 3 weeeks.

steve,

the result shows none for the phrase "Capturing the history after the fact"

Developers are executing queries which never finish. Thus causing blocking. They have told me, they executed the code before without problems.

The server is fine now. This started to happened...

killed the blocking.

Server is still very slow after 6 hours. Even rebooted it. Any other ideas please?

it works after I checked on the DROP DESTINATION OBJECTS FIRST and USE COLLATION boxes.