Yash said:Yes, we'll look at more effective ways to warn customers about high usage problems before it comes to a point where we have to disable that site. This is all planned for the new cluster we'll have up shortly.
Win5 is going to be pulled down after all sites are transferred off it.
What is the timing of the cluster?
So, you're saying that if I put my site back up with the Access database, disable most of it until I can convert to SQL so as not to cause the problem again, it will be re-activated? If I then convert to SQL, I will be given notice (before being pulled) if the site, in the new configuration, starts to consume too many resources? The notice would have to be about a week to allow sufficient time to switch to a new host...is that workable?