Home Forums SQL Server 2005 Backups Does trace flag 3226 suppress success messages on SQL2K? RE: Does trace flag 3226 suppress success messages on SQL2K?

  • Just an FYI I found out while testing that the startup parameters are sometimes a little fussy. I was changing the startup params by going to

    Start->Programs->MS SQL SERVER 2k5->Config Tools->SqlServerConfigMgr

    Right click the sql server service->properties->Advanced Tab

    The Startup Parameters field is the one we're concerned with... I noticed that you can give yourself a big headache if you just think that you can drop -t3226 or /t3226 in there anywhere. The service would not start back up if I didn't remember to put a semicolon on the line before adding the switch (it considered the tag /T3226 to be part of the path for the previous switch). After repeated tests I found out that a blank space between the newly added semicolon and /T3226 caused it to ignore the flag. So be careful when you're crafting your parameters cause even though it would start back up with the extra space there all the downtime would have been for nothing.

    The Working Value for my instance is this: (for illustrative purposes only. the values for -d -e and -l flags are instance dependant.)

    -dC:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf;-eC:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG;-lC:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf;/T3226