Why yes? Keep transactional data for a long time Query historical data Keep old apps/legacy systems to operate Save money on storage/size Rarely access old data!
Limitations: Historical data – no update/delete alter tables or views ! No FK Uniqueness is not enforced PK or Unique keys Enable or reenabling recreate it again
Size is determined by SQL Azure $$ ? Pay for your query
Introduced in 2015 and enhanced in 2016 Save DB files as Blob storage in Azure
Why? Fast Migration Cost and limitless storage benefits High availability and disaster recovery Security: separate computing instance from the storage instance. Snapshot backup advancement!
Why? Quickly find and fix a plan performance regression by forcing the previous query plan. Fix queries that have recently regressed in performance due to execution plan changes. Determine the number of times a query was executed in a given time window, assisting a DBA in troubleshooting performance resource problems. Identify top n queries (by execution time, memory consumption, etc.) in the past x hours. Audit the history of query plans for a given query. Analyze the resource (CPU, I/O, and Memory) usage patterns for a particular database.
FULL ACID but operate in memory Operate in memory and IO write if committed Both durable and non-durable
Why ? Multi tenants/departments How ? Silently, explicit
Why? Customer service and Credit card How? Simple attribute on column
Diving into sql server 2016
Mohamed Zaatar, M.Sc.