The Myth Of Tomorrow
“We’ll fix it in the mix.”
“It’s good enough for right now.”
“We’ll worry about that later.”
“Your check is in the mail.”
Of...
2017-12-04
736 reads
“We’ll fix it in the mix.”
“It’s good enough for right now.”
“We’ll worry about that later.”
“Your check is in the mail.”
Of...
2017-12-04
736 reads
I came across this in a code review not long ago:
Three things pop into my head when I see this...
2017-11-27 (first published: 2017-11-13)
2,597 reads
I never had cause to give much consideration to storage when I was a SQL developer. The companies I worked...
2017-11-19
451 reads
In my experience, there are few database objects more poorly understood, misunderstood, misused, and outright abused, than the humble view....
2017-11-16 (first published: 2017-11-05)
1,993 reads
One of the most common mistakes I see made when creating tables (and I’ve been guilty of this myself too...
2017-10-29
536 reads
I started my IT career twenty years ago as a VB and C developer, wandered into C++ for a bit,...
2017-09-30
356 reads
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...
hi , our business partner is asking s4 sap api's for receivable info and...
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...
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