Max Server Memory Setting Explained If you have more memory than your database and applications on the SQL Server will ever use than this is not a problem, but when you run into memory constraints this setting is much more important. SQL Server attempts to use as much memory as possible, and when there is no more memory available, SQL …
In SQL Server there is a special connection that can be used to connect to the database, the remote Dedicated Admin Connection or (DAC). This is a special connection that allows the administrator to connect to the SQL Server even if something has occurred that is preventing connections on the normal port. One quick way to check if the DAC …
SQL Server – Dedicated Admin Connection (remote DAC) Read more »
Here are the slides for my presentation at SQL Saturday, at Las Vegas today. Download the presentation here CorruptionPresentation.pdf
As part of the Database Health Monitor version 2.1 release there were many new report includes, one of those was the backup status report. A quick way to page through all of your SQL Servers and check on the status of backups. Here is an example of the backup status report showing a database that hasn’t had any recent backups, …
I have just released version 2.1 of Database Health Monitor, this release involved 2 months of development since version 2.0 was released in July. People often times ask me if this is free, or free to use in production, or free to use on more than one server. The answer is yes indeed, this is a totally free application to …
Database Health Monitor version 2.1 Just Released Read more »
This Saturday, September 12th, 2015 I will be presenting at SQL Saturday Las Vegas. My presentation is on Database Corruption, here are the details. When Database Corruption Strikes – Will you be ready? Duration: 60 minutes Track: Enterprise Database Administration & Deployment You are working along month after month with no problems in your database. Suddenly someone reports that their …
I was looking through my SQL Server error logs to confirm that CheckDB was being run as I had scheduled based on my previous post to run DBCC CheckDB on all databases. I wanted to confirm that there was no corruption, and that all of the databases had been checked, and not had been missed. Going through this I noticed …
So you are checking your database with DBCC CheckDB and of course if you are like me you use the WITH NO_INFOMSGS parameter. But it turns out that CheckDB is taking longer to run that you expected, and you want to check and see what table is currently being checked. Here is a quick SQL Script that I use to …
Its not always quick and easy in SQL Server to get a full list of the jobs that have been run, when they were run and how long they took. I created the following script to quickly check on the status and run time of SQL Server maintenance plans and jobs. Display Job History Just run the script in SQL …
If you use the SQL Server maintenance plans to run DBCC Check DB, you are not allowed to include TempDB in your DBCC CheckDB sequence. For a while I was using maintenance plans, and ending up adding a separate job step to run TSQL to just check TempDB. Rather than using two different steps, the regular maintenance plan, and a …