PowerShell I Heart You
PowerShell = Giggity Giggity Goo
Ok so in the last 48 hours I think I’ve fallen madly in love with PowerShell. My...
2010-06-10
915 reads
PowerShell = Giggity Giggity Goo
Ok so in the last 48 hours I think I’ve fallen madly in love with PowerShell. My...
2010-06-10
915 reads
Or maybe I’m misreading that I’m supposed to be helping to alleviate pain. Either way, next Thursday, June 17, I’ll be...
2010-06-10
555 reads
My final day at TechEd. Packed up and checked my bag at the hotel, off to the bus. Noticed that...
2010-06-10
340 reads
Another quarter gone, and unfortunately I’m still looking about the same on goal progress. Still looking good on Blog posts...
2010-06-10
1,023 reads
Every day for the next couple of weeks, I aim to highlight one of SQL Server 2008’s new features, simply...
2010-06-10
404 reads
I’ve done a good amount to raise my profile over the years. Not with that intention, but as I’ve tried...
2010-06-10
403 reads
Interesting Case of SSIS Failures
We had an interesting case of SSIS failures recently where the cause ended up being improved...
2010-06-10
1,068 reads
Here’s a big statement
WHEN WRITING DATABASE QUERIES, 95% OF THE TIME THE BOTTLENECK IS IN THE I/O, not the CPU,...
2010-06-10
971 reads
I saw this link posted by Buck Woody (blog | Twitter) and I was a little stunned. This is a profile...
2010-06-10
467 reads
This editorial for the SSC newsletter ran last week and talks about the conundrum for software vendors – how do you...
2010-06-10
599 reads
A nightly load into sales_fact fails. Ask an orchestrating agent to break down the...
By Steve Jones
It’s been some time since I provided a car update, so I decided to...
By James Serra
An architecture scenario Imagine separate Sales, Finance, Shared Data, and Executive Analytics workspaces. Sales...
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