While I was working with the SQL Server Configuration Manager in SQL Server 2005 mentioned in yesterday’s post, the new features in SQL Server Denali came to my mind. Here is why I liked the Configuration Manager in SQL Server Denali.
The first striking change is that the number of tabs have increased from 3 in SQL Server 2008 to 6. This means that the options tightly stuffed inside the 3 tabs have been allocated their own space which results in ease of management.
The feature which a DBA would appreciate is the Startup Parameters tab. In the earlier versions of SQL Server, the values in the startup parameters had to be edited in-line and a small typo there would not allow the service to start as posted here. But in SQL Server Denali, a seperate text box has been provided to Add/Update the startup parameters. This makes the DBA’s job relatively easy and the chances of erroneous entry in startup parameters are less.
The other DBA friendly feature is the ability to change the directory where dump files are generated. SQL Server Dump files (*.dmp, *.mdmp) files are generated when SQL Server encounters an issue like Access Violation or when SQL Server crashes. These files contains information about what SQL Server was doing prior to the crash or error.
In earlier versions of SQL Server, any SQL Server Dump files were by default created in the directory where the SQL Server Error Log was located. I had faced this issue on a SQL Server 2000 instance where the dump files were continuously getting generated on the C drive and managing space on C drive was a challenge.
In SQL Server Denali, the SQL Server Configuration Manager includes the option to change the Dump directory (under Advanced tab).
I wish we had this feature in SQL Server 2000. My team members would agree to this, since they had a tough time managing the .mdmp files in late 2009.
Overall the new SQL Server Configuration Manager is DBA friendly. Since we are still at CTP1, hoping to have many more such good features by the time it reaches RTM.