Notes from SQLSaturday #227 in Charleston
My first time in Charleston! Quick notes:
Made the drive with the family in 7 hours, not bad, and easily the...
2013-10-13
563 reads
My first time in Charleston! Quick notes:
Made the drive with the family in 7 hours, not bad, and easily the...
2013-10-13
563 reads
Partitioning is a feature that has been around since SQL Server 2005. It allows for users to split a table...
2013-10-12
2,681 reads
In less than 72 hours I'll be in Charlotte with over 3,000 of my closest SQL Server friends for the...
2013-10-11
714 reads
I’ve always been a fan of the feeling when I find an old blog post that’s got just the information...
2013-10-11
609 reads
It’s Friday. Tomorrow I present two sessions at SQL Saturday #238 – Minnesota. Then I take off for PASS Summit 2013...
2013-10-11
718 reads
I’m not old, but I did turn 40 today. If you ask my kids, they are likely to say that...
2013-10-11
812 reads
For those of you that attended yesterday and are interested in the slides, you can download them here. Thanks! Topic:...
2013-10-11
744 reads
This sort of ties in to my last post on denying reality.
Managing expectations is the most important thing to success...
2013-10-11
699 reads
The SQL Crazy train continues chugging along this month. The next two whistle stops are back to back in the Carolinas. The first stop is coming up in just...
2013-10-11
10 reads
The SQL Crazy train continues chugging along this month. The next two whistle stops are back to back in the...
2013-10-11
667 reads
By Steve Jones
It’s a small change, but a handy one. Flyway Desktop (FWD) now includes the...
By Steve Jones
Software is hard. While I love our Lucid Gravity, I realize that they are...
By James Serra
Making Data AI-Ready, Part 2 (This is the second article in a three-part series...
Hi everyone, I'm hoping some of the longtime SQL Server professionals here might be...
Comments posted to this topic are about the item Checking the Error Log II
Comments posted to this topic are about the item Parameter Sniffing on SQL Server...
What is the reason I should change my old code that uses xp_readerrorlog?
See possible answers