SQLSaturday #52 – Colorado Recap
I had the good fortune of being able to travel to Denver for SQLSaturday #52 the weekend of September 25,...
2010-10-04
671 reads
I had the good fortune of being able to travel to Denver for SQLSaturday #52 the weekend of September 25,...
2010-10-04
671 reads
Back in 2007 when we started SQLSaturday we had the good luck to leverage an existing relationship between Seminole Community...
2010-10-04
756 reads
I drove up on Friday, just under 7 hours with a couple quick stops on the trip. Listened to Team...
2010-10-04
510 reads
Another weekend, another new city, another SQL Saturday. This was my first trip to Kansas City, and it was a...
2010-10-04
1,606 reads
The CPUID website has a screenshot of CPU-Z 1.55.2, showing its support for the upcoming 32nm Sandy Bridge processor, which...
2010-10-04
590 reads
I have been working with a several clients that are leveraging Change Data Capture (CDC) as a tool for incrementally...
2010-10-03
1,350 reads
So many people have been waiting for a SQL Saturday in Houston and now it’s finally here. As a native...
2010-10-03
721 reads
It is amazing how fast time moves the older (and slower) we as humans get. Looking back on time, it...
2010-10-03
627 reads
The KC PASS chapter has successfully executed the latest SQL Saturday. Thanks to all the organizers and volunteers for a...
2010-10-03
2,008 reads
As I discussed in my first part of replication SQL Server 2008 Replication: High Availability Solution Part One, replication is...
2010-10-03
12,067 reads
By Brian Kelley
Fabiano Amorim has written an excellent article at Simple Talk on securing msdb. Here's...
By Steve Jones
This month we have a new host, which I am grateful for. So many...
I needed to do some research because there is more to #temp tables than...
I wrote a recursive CTE to determine employee levels... but what if I wanted...
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...
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