Database Engine Service Startup Options in SQL Server 2012

Before SQL Server 2012, it was a difficult work to add a trace flag or a startup parameter other than the default startup parameters that SQL Server uses. And, by the way, how the paramater is added from SSCM - the registry keys may not be created correctly - resulting in SQL Server startup code skipping these parameters!!!

In those days, I copy my defaults to Notepad++, than I add paramaters in this way:

Add any new parameters after the first 3 default parameters –d, -e, -l. IMPORTANT never change sorting of these parameters!
Specify the ";" delimiter between each parameter! SSCM uses ";" as the delimiter between parameters.
Do NOT use a space after the delimiter and the parameter identifier (which is the "-" character).

Copy it back to startup paramaters - save - RESTART the service!
Check the current SQL Server error log and verify that each parameter shows up in a new line and starts at the same indentation.

But now in SQL Server 2012 we have a "Startup Parameters" Tab!

Add any new parameters in the Textfield (NEVER REMOVE the first 3 default pramaters!!!)
After restarting check the current SQL Server error log and verify that each parameter shows up in a new line and starts at the same indentation.

Where to find out about trace flags

In Books Online
SQLServerPedia
And a great article by Yusuf Anis at SQLServerCentral - enjoy it!

Checking the status of trace flags

You can check the status of your trace flags by using the following command:
DBCC TRACESTATUS

If you want to know something about Trace Flag 3226, please read Christoph Muthmann's (aka cmu) post:
Trace Flag 3226

I wish you a nice day,
tosc

Qui tacet, consentire videtur

dbcc, sql server 2012, startup parameter, t1118, t3226, t834, trace flag

SQL Server

Print article

This entry was posted by Torsten Schuessler on 2012-06-28 at 15:01:00 . Follow any responses to this post through RSS 2.0.

Related Posts
Trackbacks (1)
Comments (2)

Comment from: Christoph Muthmann
2012-05-14 @ 10:29:14

Great article, but the first three parameters cannot be removed:
The following parameters are required. They can be changed but not removed.
-d is the path of the master.mdf file (the master database data file).
-l is the path of the master.ldf file (the master database log file).
-e is the path of the SQL Server error log files.

Caution
If the file path parameters are incorrect SQL Server might not start.

CU
Christoph
Comment from: Torsten Schuessler
2012-05-14 @ 12:15:37

Hi Christoph,

indeed, you are right - you can't remove it by SSCM, but by deleting the registry paramaters / key :-(

THX,
tosc