May 022012
 

Have you ever had to set SQL Server trace flags or startup parameters on the instance startup? It’s quite a chore. SQL Server 2012 solves this pain with a very simple and elegant solution.

On all versions before SQL Server 2012, the interface was just bad. If the syntax is not perfect, including semicolons or other delimiters, the SQL Server instance will not start.

Do you see that tiny space after the last ‘ldf’? That’s where any additional start parameters must go. For example, if you wish to enable large memory pages (trace flag 834), the string goes from this:

-dF:\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf;-eF:\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG;-lF:\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf

To this:

-dF:\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf;-eF:\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG;-lF:\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf;-T834

The syntax must be perfect or else the instance will refuse to start.

However, in SQL Server 2012, this screen was updated.

That’s much better! Thanks Microsoft!

 

This site uses Akismet to reduce spam. Learn how your comment data is processed.

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close