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,798 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,798 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,172 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,370 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,211 reads
2009-11-30
3,413 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,707 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,029 reads
By HeyMo0sh
In my experience, FinOps success has never been just about tools or dashboards. It...
By HeyMo0sh
As a DevOps person, I know that to make FinOps successful, you need more...
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers