Microsoft SQL Server 2012 (SP1) - 11.0.3368.0 (X64)
May 22 2013 17:10:44
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
I've done a lot of work over the last year with trace flags 8015 and 8048. Recently just started to work with trace flag 2335. In various locations all three are documented as startup trace flags. Startup trace flags can only be activated/deactivated at SQL Server startup. Other trace flags can be set dynamically at the global, session, or query level.
Interestingly, trace flag 2335 was initially documented as a startup trace flag.
But, in the KB article that documented the querytraceon function, it specifically mentions support for trace flag 2335.
If a call to dbcc traceon is made in an inappropriate context for a given trace flag, (such as trying to enable a startup trace flag after startup), the following error message is returned.
Ignoring trace flag <n>. It is either an invalid trace flag or a trace flag that can only be specified during server startup.
So... of the trace flags I am most concerned with (8048, 8015, and 2335) - which ones still register the error indicating that the must be specified at startup?
Only 8015. Looks like trace flags 8048 and 2335 no longer require activation at SQL Server startup - if they ever did.