|
Tuesday, February 13, 2007
Hi All:
We've had to rework a couple of sections of core code this morning to address SQL-related issues that cropped up overnight; these have been deployed and the affected batch runs will recommence shortly. In addition we've brought another server online to accelerate delivery, with another in the process of provisioning.
Phil
Update: 2/14 12:07 am
The updated SQL and the spiffy new server are performing well - we were all caught up by about 6pm on Tuesday the 13th. Going forward, subscribers should start to see email updates appearing somewhat earlier than before. This will be especially true for those on the default US east coast time zone, where the extra server is going to make a big difference.
We've had to rework a couple of sections of core code this morning to address SQL-related issues that cropped up overnight; these have been deployed and the affected batch runs will recommence shortly. In addition we've brought another server online to accelerate delivery, with another in the process of provisioning.
Phil
Update: 2/14 12:07 am
The updated SQL and the spiffy new server are performing well - we were all caught up by about 6pm on Tuesday the 13th. Going forward, subscribers should start to see email updates appearing somewhat earlier than before. This will be especially true for those on the default US east coast time zone, where the extra server is going to make a big difference.
|
|
posted at 10:37 AM
0 Comments:
Post a Comment
Note: Only a member of this blog may post a comment.
<< Home