More Tips for New (and old) DBAs
Following up on the popular article: Tips for New DBAs, author Craig Outcalt tackles three more issues including customer support and why you should learn T-SQL.
2013-11-29 (first published: 2009-01-12)
25,804 reads
Following up on the popular article: Tips for New DBAs, author Craig Outcalt tackles three more issues including customer support and why you should learn T-SQL.
2013-11-29 (first published: 2009-01-12)
25,804 reads
Author Craig Outcalt gives advice on preparing for the worst with a look at what you should consider putting in your disaster recovery plan and why.
2012-12-10 (first published: 2011-09-26)
5,188 reads
Author Craig Outcalt takes a deep dive into the SQL Server memory allocation and how it competes with OS memory.
2011-09-20
15,435 reads
New and old DBAs alike can benefit from going back to the roots of the profession. This series of articles highlight the skills needed to move to the next level of Database Administration.
2010-02-12 (first published: 2008-11-18)
46,225 reads
2009-11-30
3,419 reads
This technical article provides an overview of how to produce specific levels of index fragmentation. Useful for creating test plans.
2008-10-29
6,715 reads
Getting the number of processor cores that SQL Server is using is not as straitforward as it could be. Enter the affinity mask, bitwise operations and good old fashioned computer science.
2008-10-17
4,034 reads
By Arun Sirpal
Until now, a CRITICAL finding did the right internal routing, but the last mile...
By Steve Jones
This is actually inspired by an article SQL Server Central, which taught me something...
By alevyinroc
T-SQL Tuesday is a monthly blog party hosted by a different community member each...
I installed a new SQL server 2025 Enterprise developer edition for our development environment....
Telp Cs:(0821)8200174 Jl. Jenderal Ahmad Yani No.1, Benua Melayu Darat, Kec. Pontianak Sel., Kota...
Telp Cs: (0821)8200174 Jl. Jend. Sudirman No.17, RT.008/RW.04, Pangkal Lalang, Kec. Tj. Pandan, Kabupaten...
How can I change the location in which the SQL Server error log is written in SQL Server 2025?
See possible answers