2024-05-10
380 reads
2024-05-10
380 reads
2024-05-06
439 reads
2024-05-01
361 reads
2024-04-26
406 reads
2024-04-17
385 reads
If you haven’t migrated your workloads to a managed database platform yet, you’re probably still relying on SQL Server Agent for various maintenance and other scheduled tasks. Most of the time, these processes just work. But when it’s time to troubleshoot, it can be cumbersome to get to the root of some problems.
2024-04-17
2024-03-29
373 reads
2024-03-29
9,247 reads
2024-03-27
373 reads
This is for the folks who still have to log into remote machines and do work manually on the box. Yes, we still exist, and we will for as long as we’re still using physical servers in data centers and even IaaS. Not everyone has transitioned to server core and full-on PowerShell remoting for everything
2024-03-20
By Brian Kelley
Here is a short emotional intelligence (EI) post for today, courtesy of Seth Godin....
By Steve Jones
I was recently trying to handle a simple task with a few AI tools...
A nightly load into sales_fact fails. Ask an orchestrating agent to break down the...
I have a really stupid question... Is there an easy way to search for...
Comments posted to this topic are about the item How to Work with On-Premises...
Comments posted to this topic are about the item Escaping Strings
The STRING_ESCAPE() function requires 2 parameters in SQL Server 2025. The first is a string of text and the second is the type of escape rules being used. What are the options for the second parameter?
See possible answers