Yesterday I covered what’s strecthing a database to cloud. Today I’m going to cover how to identify the tables which can stretch to Cloud. In most of the cases you knew which table we can move however if you are not sure when one then you can make use of this tool. I’m going to use one of the famous tool used in assessment before SQL Server upgrade to new version. Yes you are right, it’s SQL Server upgrade advisor!!
One of the new feature that’s going to accompany in SQL Server 2016. There is a significant improvement in the hardware sector moving into SSD, flash disk etc which increases the cost of hardware. Holding all the historical or archieve data in to this high performing disks is going to cost you more, assuming you got larger volume of data. As a DBA we don’t want to include this historical data into our backup plan to avoid the backup size. We can choose partial backup but again the tradeoff is in the recovery plan. Continue reading SQL Server 2016 – What’s Stretch Database
One of the new feature that’s being developed with SQL Server 2016. If you are a DBA then you will like this feature very much. In the real world when you move the data from production to development or uat server we are supposed to obfuscate the data so that the developer wont see the actual live data. Till SQL Server 2016 we are achieving this with dynamic DML scripts which will mask the data. Based on the volume of records in the database we will end up long wait hours to obfuscate it. Continue reading SQL Server 2016 – Dynamic Data Masking
After couple of years I’m started playing around the pre release packages. Today I installed Windows Server 2016 Technical preview release 3 and SQL Server 2016 CTP 2.4 in my machine to play around the upcoming release. Continue reading SQL Server 2016 – Tempdb Configuration During Installation