Hi. After about a 9 months of running without issues, I'm seeing 3 early sql engine tasks in our etl suspended hours after the entire package should have completed. Since I started watching there have been no change in the 3 i-o's but
they are at 75797,1178 (the select) and 223275 already. Earlier today, I had to cancel an engine db backup (to disk) on the same server after it seemed to be running hours longer than expected. There are two databases on the entire server.
One is an engine db, the other olap. The engine is about 97 gig. I see hundreds of gigs available on the c: drive. I see no blocking reported by sp_who2. Two of the tasks are bulk inserts. One is a select. I believe
that even if one or two tables from a separate source server are involved, that they arent preventing my tasks from running because I had no problem running adhoc and count(*) queries on them separately under ssms. But I dont have security to run sp_who2
or the dmvs there (the remote server) to be sure.
Is it possible that cancelling my backup today left sql in a funny state? I see SP1 STD 2008 when I run server properties. Is it possible sql feels that some available disk space threshhold has been hit and it has become somewhat
frozen as a result? I dont thin
View Complete Post