The cold-to-warm state change sounds like it's something you would only ever want to do in batch jobs.

But I can see many situations where you have a DB that only needs to actually be awake for short periods of time throughout the day for batch jobs. And even more that only need the barest minimum capacity available 24/7 with large spikes for batch-based processing.

Not sure what you're talking about. It's warm for as long as you want it to be. That's configurable. Read the post.