I've got a problem with trigger happy users.
I know that PEBKAC problems are common and the usual way to deal with it is user training. But some just can't get the plot.
So, i have a SQL Data Reader connected to a SQL Server 2000 databases and linked servers. The process it has to work through can take some time. Sometimes users get bored or something and think "hey this is taking too long, i'll sort it out" and end the task in Task Manager. Problem being this leaves it in the SQL Server and it screws things up big time (requires a server restart due to the MSDTC process crapping out) I can't kill the process in SQL Server as it just sits there in the Killed/Rolled Back state for like, ever.
Is there any way, when my program starts up again, that i can clear that data reader (which i'm guessing leaves the server side cursor going)?
Or is there anything i can do to clean up afterwards? I don't think there is, but i thought i'd ask anyway.