Error updating content descriptions record phoenix
Up to three delivery attempts will be made, excluding weekends and holidays.
The shipment has reached the local UPS facility responsible for delivery and has been dispatched to a UPS driver.
The appropriate response to a full transaction log depends partly on what condition or conditions caused the log to fill.
To discover what is preventing log truncation in a given case, use the log_reuse_wait and log_reuse_wait_desc columns of the sys.database catalog view.
For more information, see sys.databases (Transact-SQL). For descriptions of factors that can delay log truncation, see The Transaction Log (SQL Server).
These alternatives are discussed in the following sections. Under the full recovery model or bulk-logged recovery model, if the transaction log has not been backed up recently, backup might be what is preventing log truncation.
This message does not mean that your shipment is behind schedule or stopped moving; it simply means that the tracking label might not be scanned for a while.
We display the Next Expected Tracking Event so you can rest assured that your shipment is still moving even though no new tracking scans may appear for a while.
Once the shipment is moving within our network, we will provide a scheduled delivery date.This topic discusses possible responses to a full transaction log and suggests how to avoid it in the future.