Last week I published below blog where I talked about a trace flag. Backup Randomly Failing with Error 112 (There is not enough space on the disk.) One of the reader commented, whether he needs to enable trace flag every time SQL Server is restarted?
SQL Server 2016 – Introducing AutoGrow and Mixed_Page_Allocations Options – TraceFlags
I have been playing around with SQL Server 2016 for a while now and I have seemed to have learnt a number of interesting options when playing around with the new version. One of the readers after reading – SQL Server 2016 – Enhancements with TempDB asked me if the option of TraceFlags of 1117 and 1118 not available when working with user defined normal databases. This was a valid and appropriate question for sure. I was not sure where to start. Let us see traceflags related to AutoGrow and Mixed_Page_Allocations.
SQL SERVER – Identifying Page Types
I try to keep the understanding and concepts for learning simple. Because for a strong building one needs to have a solid foundation. The structure’s stability is a function of how well the foundation holds them. Just having a beautiful exterior will not be sufficient. So getting into complex design issues or internals sometimes is not of any use if you didn’t get the basics right. Let us learn about Identifying Page Types in SQL.
SQL SERVER – What are my Trace Flags Enabled on SQL Server?
In one of my recent interactions with a DBA friend of mine, I had to dig into one of the simplest yet a capability which is available inside SQL Server. SQL Server from time to time has an uncanny requirement to enable certain Trace Flags. Trace Flags are specifically enabled by administrators to mitigate certain behavior that SQL Server has in specific situations. We need to understand that, these trace flags are a special purpose and shouldn’t be used without understanding what the implications are on the server as a whole. So please handle these with care. LEt us learn about trace flags.Â