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,803 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,803 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,178 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,422 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,220 reads
2009-11-30
3,417 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,712 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,031 reads
Running AI and data pipelines on the edge instead of the cloud has gone...
By Steve Jones
While writing another post I realized my UNION query didn’t work as one might...
It’s time for T-SQL Tuesday again! And we’re almost to number 200! T-SQL Tuesday...
Comments posted to this topic are about the item Secure Cached Plans
Comments posted to this topic are about the item Complex Data Processing with dbt...
Comments posted to this topic are about the item Over or Under Provisioned
The DMV, sys.dm_exec_cached_plans, contains rows for each cached plan on an instance. In Azure SQL Database, not every used has rights to every database, as there does exist an instance behind each database. How is security handled for this DMV in Azure?
See possible answers