Querying SQL Server Agent Job Information
Is there an easy/automated way to get information on SQL Server Agent jobs instead of connecting to each server and manually getting the information through the SSMS GUI?
Is there an easy/automated way to get information on SQL Server Agent jobs instead of connecting to each server and manually getting the information through the SSMS GUI?
Deploying changes to your environments can be challenging, especially when you have multiple script files. Sadequl Hussain brings us a technique that works well and handles mutliple files.
Start your 2012 off right with a free day of training in Colorado Springs. Bring the kids as well, as the venue is very family friendly.
The last Friday poll of 2011 has Steve Jones asking about what you want out of 2012.
Check out this tip to learn about the SELECT @@VERSION command in SQL Server.
SSIS features log-providers that can write to five different types of logging destinations; three of them are files, one is the 'dbo.sysssislog' table, and the last is the Windows Event Log.
There has been much debate over the need for the Lock Pages in Memory privilege, on 64-bit versions of SQL Server. Jonathan Kehayias presents a "warts and all" account of its history, the confusions surrounding its use, and why he believes it's still a good default configuration for 64-bit SQL Server instances, even when running Windows Server 2008 and Windows Server 2008R2.
Users often have a certain expectation of privacy about their data in applications, and as software engineers, Steve Jones thinks we need to respect that.
By Arun Sirpal
Fourth in a series on Ai and databases. What Read-Only Advisory Actually Means A...
By DataOnWheels
This is a blog that I am writing for future me and hopefully it’ll...
By Steve Jones
While wandering around the documentation looking for some Question of the Day topics, I...
Please I am hoping for some feedback Specifications: Windows Server 2022 SQL Server 2022...
Comments posted to this topic are about the item How Do the Experts Become...
Comments posted to this topic are about the item Stairway to Reliable Database Deployments...
I run this command to start SQLCMD:
sqlcmd -S localhost -E -c "proceed"At the prompt, I type this (the 1> and 2> are prompts):
1> select @@version 2> goWhat happens? See possible answers