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.

Last week I wrote an article for Creating DAC packages. Today I’m going to cover how to deploy a DAC package. It’s very easy  for the DBA’s to deploy the DAC in few clicks that means in few clicks database implementation will get completed, it’s as simple as like that. I’m going to use the DAC package which I created last week. To deploy a DAC package proceed the steps below

In previously article I’ve covered what is DAC package and how it helps during deployment. In this article I’m going we are going to see how can we create a new data tier application (DAC) package for deployment. All SQL Server related objects can be included in this package for deployment, this includes both database and server level objects. You can create DAC package through any of the following methods

Denali CTP3 is already released and we have new DMV’s accompanied with this version which will be very useful for us. I’m going to cover the DMV that are all generic and not to a specific feature of Denali, I’ll will cover those DMV’s while writing article on that feature. There are around 8 DMV’s which I’m going to discuss it now.

Activity monitor has been refreshed in SQL Server 2008 Management studio. Microsoft has recoded the activity monitor written for SQL 2005 to provide more information on SQL Server processes and how these processes affect the current instance of SQL Server. The first change which I experienced is the real time graphical view of processes, CPU time etc, this really helps us to know the status of the server immediately.