Index Reorganize time limit by Greg Low - Australia

This would be so beneficial in our OLTP environment where we simply can't afford Enterprise Edition for online rebuilds. I strongly urge Microsoft to reconsider this proposed feature. It can't be that difficult to implement.
Seems like a work-around would be to set the timeout value prior to issuing the reorg statement. So behind the scenes the implementation could just temporarily set that session timeout value.

This should be implemented, having the ability to stop this operation would greatly increase the benefit of index reorganize where you have small (but maybe frequent), maintenance windows.

I completely agree that this is a fantastic idea. I would also add that it would be nice to specify a transaction log consumption limit (percentage or absolute kb/mb/gb/tb). With mirroring and availability groups, and maintenance windows, very worthwhile suggestion!

Voted up as a useful enhancement to the language. Borrowing Aaron Bertrand's example syntax:

ALTER INDEX foo
ON dbo.bar
REORGANIZE WITH (TIME_LIMIT = '00:45:00');

This is much neater than the workaround (a job to kill a job).

Sorry, I didn't quite follow the comments. As far as I'm aware, Index rebuild is transactional and will be rolled back if interrupted but Index reorg isn't transactional and won't be rolled back if interrupted.
Then, it makes complete sense to have a time limit.
Many customers can benefit from index reorganization but have limited time windows for this work. It shouldn't be necessary to build a job to find and kill another job, just to be able to specify that "I'd like to do an hour's work of reorg tonight".

Greg,

Good suggestion. However, index reorganization is a transactional operation, so any work completed before a "cancel" is issued will be complete and not rolled back. Can you implement a script that automatically cancels the operation after some period of time?

Thanks,
--R