SQL Server 2014 Introduces Delayed Durability

When it comes to IT systems scalability is a huge buzz words. untitledEveryone wishes to create robust and scalable systems that can be dynamically upgraded, however it is hardly easy to execute in practice. In some cases you need to come up with innovative solutions to deal with tricky issues. Let’s take a corporate application that runs perfectly for most part of day except for certain hours where a higher number of people log-in and update data. During those peak hours transactions take a huge amount of time to complete and users end up waiting idly for updating the next transaction. Much of this delay is due to the fact that transactions have to be committed first via I/O mechanism before the control can given back to the end user. While scaling up can help alleviate the situation, it would involve significant costs. However SQL Server 2014 you can quickly workaround the issue by using the delayed durability feature.


  • How Does Delayed Durability Work

Delayed durability essentially uses a buffer to hold the data records you input into the database still certain amount of data from multiple transactions are available. Then it commits together in one go thus drastically reducing the I/O activities. Moreover a user gets back the control immediately as system does not hold back till the I/O operation is completed. As data is written in large chunks, it helps improve the overall capacity of the system.


  • Key Benefits

Using delayed durability can offer you significant benefits in a whole array of scenarios. To start of with, you would have the bandwidth form more concurrent users seamlessly using the application as I/O is not bogged down. In scenarios where there is a significant contention rate, use of delayed durability can facilitate quicker release of locks and increase the overall productivity.


  • When to go in for Delayed Durability

At times the idea of exercising the delayed durability option may not work out if you cannot deal with even minimum data loss. If you do have some bandwidth for data loss in case individual records then you can use this feature. Most non financial corporate applications, such as MIS, logistical applications etc can use this feature with ease. Again if your Windows Server is prone to crashes, you should avoid using the feature as certain amount of data loss would always be a part of the deal.


  • SQL Server Remains vulnerable to crashes

Even after introducing several sophisticated features, the SQL Server application still remains vulnerable to crashes. In some scenarios you would even find your SQL data files getting all messed up and sql recovery becomes the order of the day. Now if you have been looking for a proficient tool to bring back your lost data then you should undoubtedly go DataNumen SQL Recovery application owing to its stellar performance record. Not only does it give you the highest data recovery rates, it is quite capable of helping you dig out content from related NDF files.


Author Introduction:

Alan Chen is President & Chairman of DataNumen, Inc., which is the world leader in data recovery technologies, including access recovery and sql recovery software products. For more information visit https://www.datanumen.com/

Comments are closed.