DBCC FREEPROCCACHE – What is the impact.
Here is a question that I received from a friend today and I thought it would be a good post explaining the details: Steve, I… Read More »DBCC FREEPROCCACHE – What is the impact.
Here is a question that I received from a friend today and I thought it would be a good post explaining the details: Steve, I… Read More »DBCC FREEPROCCACHE – What is the impact.
I am excited to announce that I will be speaking at (and helping organize) the SQL Conference called Companero Conference in Norfolk VA on October 4th… Read More »I’m Presenting at the Compañero Conference In October
Today Episode 91 released and it is our pleasure to present this episode on DBA Tools. DBA Tools is an open source project (http://DBATools.io) that provides a number of powershell scripts to better help the DBA perform common SQL Server tasks. This was a fun episode with the panel of Chrissy, Rob, Constantine, and Aaron who were super excited to talk with us and we loved their energy.
We all want an easy button. It is human nature. We heard quite a bit about how easy PowerShell will make everything, but for those of us who aren’t programmers, it can be a bit intimidating to get started. The PowerSHell tools from dbatools.io are shaping up to be the closest thing to an easy button for DBAs. On this episode we invited some of the team to chat with us about their tool, how they got started and the types of problems they are looking to solve.
“The features that are now inside of DBA tools, honestly, I would describe them as really awesome.” – Constantine
“I promised you this is the best code ever used and that you will ever have.” – Aaron
“It is important to us that people do feel welcomed and that their codes gets merged in.” – Chrissy
Read More »Podcast Episode 91: DBA Tools – Listen and find out what you are missing.
From time to time I get asked about checkDB, and there are many solutions out there, but I have one that I generally use that is very simple and does the job.
The script below created a stored procedure in the DBHealthHistory database that can be used to check as many databases as you can get through in a specific time interval. Here it is set to 5 minutes, but that usually gets extended for large databases. If you set the job to daily, and the job doesn’t get through checking all the databases today, it will pick up where it left off and check the rest tomorrow.
Depending on the number and size of your databases you may want to run this more than once a day, or for a longer period than the 5 minutes.
Note: the 5 minute limitation is checked before starting the next check, so if you have a database that takes hours to check, that will kick off in the 5 minute interval and run until completion.
This weeks episode of the is Episode 90 released today. Episode Quote “I would say that the bigger issue is probably going to be something… Read More »Podcast Episode 90: DBCC CheckDB
One of the common problems with when diagnosing what appears to be a slow scenario where there may be blocking involved is determining what is… Read More »Finding Blocking Queries
Today I had the opportunity to complete and launch the February 2017 version of Database Health Monitor.
I hope you like the latest version. Here are the Release Notes:
Version 2.5 is the February 2017 release of Database Health Monitor, released on February 19, 2017.
On March 18th I will be attending SQL Saturday 610 in Richmond Virginia and the day before I will be presenting a pre conference session… Read More »Pre-con at SQL Saturday Richmond in March – Emergency Preparation for Database Disasters
For a couple of months we have had requests on the SQL Data Partners Podcast to do an episode on indexing. It is my pleasure… Read More »Podcast Episode – The Long Awaited Index Episode
Lately I have had the opportunity to work with performance tuning of queries running on the Azure Parallel Data Warehouse (Azure PDW). This has been interesting in that everything you thought you knew about SQL Server DMV’s, writing queries and overall performance tuning is just a little bit different.
My goal was to write a query to show me what is currently active and running on the Azure PDW database.
To start with, I discovered the view called SYS.DM_PDW_EXEC_REQUESTS which contains all kinds of great information to get us started. Specifically it hold information on queries that are currently running or have recently been run or attempted to be run on the Azure PDW database.
SELECT * FROM SYS.DM_PDW_EXEC_REQUESTS;
Which returned hundreds of rows, and didn’t really get me to where I wanted to go.
Next I added a WHERE statement to filter out those queries that were “done”. In this case done means that were ‘Completed’, ‘Failed’ or ‘Cancelled’.