Well, once again I haven’t been very diligent in posting exercise success.
Quick recap – this week I did 10.75 miles on tuesday and 5.25 miles on thursday. Monday and wednesday were strength and conditioning.
I was toasted after the Tuesday workout. I maintained about 170HR and 7m27 per mile. Now I need to start transferring that to the roads.
Thursday workout was about 7m31 per mile. I wanted to take it easy but I have a hard time with that.
Planning to upgrade/migrate requires a fair amount of prep work. Some of that prep work involves auditing your server for any users that may still be using the instance.
Quality data is a goal we all strive to attain. Nobody wants to have bad data. Yet, despite our best efforts, the problem of bad data has its way of presenting itself over and over again.
For the most part, things work the way you might expect them to work in windows – except it is on Linux. Sure some things are different, but SQL Server itself, is largely the same.
This article demonstrates how to use Extended Events to determine if a database is being used by someone or something.
There are multiple ways of retrieving data from a table when you have a list of values. This article explores the use of the table value constructor.
I am humbled to be among so many great professionals and honored at the same time for having been chosen.
With this script, I have the ability to quick show which step is failing, what the command is for that step, what kind of process is running on that step, any passwords (in the event of an SSIS password), and of course the failure frequency. This is golden information at the fingertips. There is no need to click through the GUI to gather this information. You can get it quickly and easily in one fell swoop.
Data professionals around the globe are frequently finding themselves occupied with figuring out why and when a file (data or log) for a database has changed in size. Whether that change is a growth or shrink, or if the change was expected to happen or not.
An important part of any DBAs job is to ensure database related jobs are running prim and proper. Sometimes that just doesn’t happen. When jobs are being overlooked, it is useful to be able to gather data related to consistency of job success or failure. This script will help you in your investigation efforts.
If you are being serious in your role, then the amount of times you grant permissions to the public role should either be a) never, b) when you want to have a data breach, or c) you are testing in a sandbox to improve your skills.
