2018-12-14
809 reads
2018-12-14
809 reads
2016-09-21
1,198 reads
Indirect checkpoint is the recommended configuration, especially on systems with large memory footprints and default for databases created in SQL Server 2016.
2016-07-21
10,996 reads
This script will detect and display a quick summary of your SQL Server installation.
2016-08-03 (first published: 2015-01-29)
9,497 reads
Check 96 server and database settings to make sure they match your expectations in your databases with this script.
2014-05-06
4,727 reads
There are around seventy SQL Server instance settings, and a DBA needs to be aware of the effect that many of them have. Brad McGehee explains them in enough detail to help with most common configuration problems, and suggests some best practices.
2012-02-13
4,300 reads
Windows Firewall is an OS level software firewall. It can be a crucial part of OS level security if you are not using other firewall hardware or software. Since I do not have another firewall I have a need to enable Windows Firewall for my SQL Server database server. In this article I go through the process of configuring Windows Firewall for different scenarios along with the associated considerations.
2010-02-11
4,068 reads
The importance of correct configuration. Which default configuration options to change. Common mistakes.
2009-10-22
4,609 reads
I want to move my database on my SQL Server 2005 system to a new drive, but I have database options, like cross-database ownership chaining, that I don't want to lose or have to remember to re-apply. How can I do this?
2009-02-26
2,969 reads
2008-12-03
3,703 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
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