External Article

Providing SQL Agent Job Log Data for Developers

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.

SQLServerCentral Editorial

Still 32

There is likely still a lot of 32-bit software out there, even as the x86 platform appears to be dying away. Steve Jones notes that you'll likely be dealing with 32/64 bit issues in your career.

Blogs

Rethinking Index Maintenance: Why avg_fragmentation_in_percent Is Outdated and What You Should Do Instead

By

As a SQL Server DBA with years of experience tuning production environments, I’ve seen...

Microsoft Build 2026 announcements

By

Once again there were a number of Microsoft Build announcements related to data and...

T-SQL Tuesday #199: Roundup

By

A good week ago I hosted the monthly T-SQL Tuesday blog party. I invited...

Read the latest Blogs

Forums

Changes, Happiness, and a Few Tears

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Changes, Happiness, and a Few...

BCP on Linux

By Steve Jones - SSC Editor

Comments posted to this topic are about the item BCP on Linux

You Probably Don't Need a Vector Database

By Kumar Abhishek

Comments posted to this topic are about the item You Probably Don't Need a...

Visit the forum

Question of the Day

BCP on Linux

When running bcp on Linux, what is the field terminator?

See possible answers