This script outputs sql server service, start type, status, Service Account, installation location, start up time, uptime of sql server related services along with startup trace flags.
2015-12-17 (first published: 2015-12-09)
1,131 reads
2015-11-10
1,617 reads
As a production Database Administrator, I do not want to give Developers direct access to the SQL Server Agent job log especially for servers in the DMZ. Another problem we have is that when there is a lot of log data for a job, the default job log doesn't contain the full log detail and that makes it harder to troubleshoot. Most of all, we are trying not to use a different code set for deployment based on the environment. Basically we want to use the same methods to deploy our jobs to Development, Test and Production.
2013-01-29
1,816 reads
2012-05-15
2,312 reads
2012-02-28
2,269 reads
The following script can be used to determine the list of enabled SQL Agent Jobs, their start time, average run duration and next run date.
2011-12-29 (first published: 2011-11-30)
2,164 reads
SQL Server Agent is at the heart of any live database system. The Agent has a number of uses which aren't always obvious, and so a knowledge of the system is always useful, to developers as well as DBAs. Richard Waymire provides a simple explanation of its many uses.
2019-03-26 (first published: 2011-02-04)
5,154 reads
In a previous tip, the tip reviewed several steps for a better and improved environment for scheduled jobs. I am totally convinced with the recommendations and want to implement these for my scheduled jobs. To make this easier, I want to create a template so I can produce a suitable and reliable way of updates for my production server. In this tip I provide a step by step exercise to perform on a test server to prepare the customized and tested scripts to run on the production server.
2010-11-18
4,353 reads
Proxy accounts are a useful tool to enable teams to work independently allow users who do not have administrative access to SQL Server to run jobs.
2010-05-31
2,735 reads
2009-11-26
3,040 reads
Hello everyone! Just a quick note. I’ve removed all my slide decks from SlideShare....
Following on from my previous post about hitting the Kubernetes API from SQL Server...
By Rohit Garg
Introduction Migrating databases can be a complex task, especially when dealing with large-scale systems...
Comments posted to this topic are about the item Connect Cloud Power BI to...
Good afternoon, I had a 7.8 TB database that needed some work. I removed...
You're tasked with planning capacity for a new SQL Server database workload. Which of the following is the most accurate way to determine how much CPU, memory, and I/O throughput your workload requires? What single or multiple tools would you use to answer the questions around resource needs?
See possible answers