A lot of people have made a difference in my career. A LOT! I don’t think we ever thank those that make a difference as much as we should. Often, it’s not until years later when you look back on your career and reflect on how you got from where you used to be to where you are now that you really realize how much help you had along the way. Sometimes that help is incidental or accidental. Sometimes that
Thanks to everybody who attended my webcast Troubleshooting SQL Server Connection Issues yesterday. If you missed it, the recording will be available soon on the MSSQL Tips website. The slide deck and demo code will also be available with the recording, or you can download it below. Slide deck: TroubleshootingSQLServerConnectionIssues.pptx (1.1 MB) Demo code: TroubleshootingSQLServerConnectionIssues.zip (2 KB)
In case you missed, I started a new blog series several weeks ago called 5 Tips for Friday on SQL Server Best Practices. Every Friday I post a set of 5 best practices on a particular topic. The topic changes from week-to-week. This week’s topic is database configurations: 5 Tips for Friday: Database Configurations. The topics covered previously are: Security Query Tuning Transaction Log Upgrades and Migrations Availability Groups Public Speaking Be sure to check back each Friday for the
If you have worked with me or are a frequent reader of my blogs or a frequent attendee of my presentations, you know I hate doing things manually. Over my career, I have found that one of the biggest enemies of automation is being able to get someone else to do it manually. If you can get someone else to do the work, it’s not your problem, right? I have seen manual processes linger on for years when it could
I will be doing a live webcast on Thursday, November 9th 2017 at 3 PM Eastern Time (8 PM UTC time) on Troubleshooting SQL Server Connection Issues. The description for the presentation is below. Hope to you all there. Registration is required to attend. Description Whenever a connection to SQL Server fails, it’s usually blamed on SQL Server by default. There are dozens of things between the user and SQL Server that could cause the connection to fail. The problem
Recently, I joined Carlos L Chacon (site|@CarlosLChacon), Steve Stedman (blog|@SqlEmt), and the rest of the SQL Data Partners Podcast team for their podcast show and the episode went live earlier this month. We talked about best practice and the reality of patching SQL Server. Check out the podcast to get my take on keeping up with patching and see Carlos’ write-up on the podcast to see what you can expect from it. Episode 112: Keeping up with patching
If a disaster struck tomorrow, are you ready for it? Are you sure you thought of everything? I cannot count the number of times something happened, and I thought that I should have been able to anticipate that. It can be a big benefit to get another viewpoint on your disaster plan. No matter how well you think you’ve covered yourself, someone who thinks about things differently than you do can often see something you don’t. Here’s a checklist of
A few years ago, I did a blog post series dedicated to disaster recovery (backups, restores, corruption, etc). 31 blog posts dedicated to the topic (though not 31 days in a row) have been compiled into a 75 page eBook that can be downloaded from the new website SQL Server Best Practices.
If you’ve been living under a rock, you may not have noticed how frequently SSMS is getting updated. The SQL Team is really rocking over at Microsoft putting out fixes and enhancements fast and furious. When CUs (cumulative updates) and SPs (service packs) come out, it makes sense to install the latest SSMS update at the same time (if you put SSMS on your servers). If applying both an SP or CU along with an SSMS update, order does matter.
It’s T-SQL Tuesday again, and this month’s host is Kendra Little (blog|@), and the excellent topic selected by Kendra is Interviewing Patterns & Anti-Patterns. When I logged on to Twitter this morning, the first tweet I saw was for Brent Ozar’s (@BrentO) post The DBA Job I Turned Down. It was another great post from Brent, and I was inspired to write about a similar topic. For my contribution to this T-SQL Tuesday is 3 Jobs I Didn’t Take, and