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

Stupid Things I Did With AI: ASCII Art

By

I ran across this article recently (https://www.gatesnotes.com/meet-bill/source-code/reader/microsoft-original-source-code) and it has a great opening piece...

Simple Talks Podcasting in 2026

By

I’m in the UK today, having arrived this morning in London. Hopefully, by this...

SSMS 22 still inserting tabs instead of spaces

By

I’m not trying to start up a debate whether you should use tabs or...

Read the latest Blogs

Forums

Script Task execution error with HTTP request

By Bhagat

I have a script task that tries to execute a HTTP request, which seems...

SQL Server 2025 Standard Developer Edition

By Johan Bijnens

Comments posted to this topic are about the item SQL Server 2025 Standard Developer...

URL Safe or Not?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item URL Safe or Not?

Visit the forum

Question of the Day

URL Safe or Not?

If I use BASE4_ENCODE() in SQL Server 2025, is the output URL Safe by default?

See possible answers