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,834 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,834 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,214 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,492 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,298 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,760 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,051 reads
By James Serra
Microsoft shared a broad set of Fabric, Power BI, and SQL updates at FabCon...
By Steve Jones
No, I’m not quitting or retiring. Just going on vacation, but I leave tonight...
Comments posted to this topic are about the item Let's Talk Certifications, which is...
Comments posted to this topic are about the item The Hidden Security Risks of...
Comments posted to this topic are about the item The Empty Aggregate
I have this table in a SQL Server 2025 database:
CREATE TABLE [dbo].[CustomerOrder] ( [OrderID] [int] NULL, [CustomerID] [int] NULL, [total] [money] NULL ) ON [PRIMARY] GOWhat is returned from this code? (answers are for the sum and then the count)
SELECT SUM(total) AS sum,
COUNT(total) AS count
FROM dbo.CustomerOrder;
See possible answers