Assertion: blob's data | /r/HasProperty | accessed
Facets:
value: rarely
type: DEGREE
value: frequently
type: TEMPORAL
value: if ever
type: TEMPORAL
value: early in its lifetime
type: TEMPORAL
value: actively
type: MANNER
Source sentences:
text: Data stored in Azure Blob storage can be accessed by making RESTful API calls or by connecting to the storage using Azure PowerShell or CLI.
text: For example, backup and archival data stored in Azure Blobs could stay in the cloud for long durations without being accessed, whereas the data in blob storage used by a production application will be accessed and modified on a daily basis.
text: This tier, as the name indicates, is suitable for data that will be frequently accessed.
text: Hot - Optimized for storing data that is accessed frequently.
text: - Optimized for storing data that is accessed frequently.
text: Cool - Optimized for storing data that is infrequently accessed and stored for at least 30 days.
text: - Optimized for storing data that is infrequently accessed and stored for at least 30 days.
text: Archive - Optimized for storing data that is rarely accessed and stored for at least 180 days with flexible latency requirements (on the order of hours).
text: Some data is actively accessed and modified throughout its lifetime.
text: Some data is accessed frequently early in its lifetime, with access dropping drastically as the data ages.
text: Some data remains idle in the cloud and is rarely, if ever, accessed after it's stored.
text: Some data stays idle in the cloud and is rarely accessed once stored.
text: Some data stays idle in the cloud and is rarely, if ever, accessed once stored.
text: In general, any data that is seldom accessed is a perfect candidate for cool storage.
text: This data can be accessed from anywhere in the world.
text: The hot tier is optimized for storing data that is accessed frequently.
text: The cool storage tier is optimized for storing data that is infrequently accessed and stored for at least a month.
text: The archive tier is optimized for storing data that is rarely accessed and stored for at least six months with flexible latency requirements.
text: The hot tier is optimized for storing data that is accessed frequently.
text: The cool storage tier is optimized for storing data that is infrequently accessed and stored for at least a month.
text: The archive tier is optimized for storing data that is rarely accessed and stored for at least six months with flexible latency requirements.