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
I wrote multiple articles on heterogeneous linked server which helped user to connect to Sybase , SQL Server & MySQL RDBMS platforms. However I missed creating Oracle linked server , many users responded to write an article on this so I decided to complete it. As you know when you create a heterogeneous linked server you need proper driver of the destination RDBMS. I have split this into two sections a.) Installing Oracle Driver and configuring tnsnames.ora file b.) Creating Oracle linked server in SQL Server Continue reading Creating Oracle Linked Server in SQL Server
In one of my project I was working on SQL Server 2000 to SQL Server 2008 upgradation. It’s a side by side upgrade so I need to restore the database from SQL Server 2000 to SQL Server 2008, in which some of the databases are readonly. I know I will be able to restore readonly database however in this case when I tried to restore the database in SQL Server 2008 I got the error below
AWE (Addressing Windows Extension) is one of the know server configuration to everyone. This parameter allows SQL Server to access large amount of memory in 32 bit machines. However MS decided to depreciate this configuration in SQL Server 2012 (Denali) . I hope this is the first step towards depreciating all 32 bit SQL server editions. So if you are using this setting in your current environment then you need to be careful while upgrading it to SQL Server 2012.