Microsoft announce SQL Server 2014
As the world is going green, Microsoft announced today that it is going “Blue”. Confused? I’ll explain all in a...
2013-06-03
1,268 reads
As the world is going green, Microsoft announced today that it is going “Blue”. Confused? I’ll explain all in a...
2013-06-03
1,268 reads
Welcome to Teched 2013
We’re starting off with some type of James Bond video. Chase scene with a really cool car....
2013-06-03
876 reads
The Techno Security & Forensics Security Conference is held in conjunction with the Mobile Forensic Conference each year in Myrtle Beach,...
2013-06-03
1,189 reads
I was asked today to take a table with a social security column and put all 0s if the column...
2013-06-03
919 reads
This probably applies more to beginners or people who have been using SQL for a while but have been wondering...
2013-06-03
510 reads
To move a database from one location to other you fist need to detach the database from server. In this...
2013-06-03
1,153 reads
Today Microsoft announced their next major version of SQLServer, SQL Server 2014 at Tech-Ed NA 2013.
This version of SQLServer is indeed a reflection...
2013-06-03
1,382 reads
Oh my god, there are so many events happening this month it is crazy. I’m going to break with tradition...
2013-06-03
697 reads
I was searching all over the place to try to find out how to move files into Azure Storage. Most...
2013-06-03
2,382 reads
I’m a little late to the celebration but on Friday some there was some exciting news regarding Power View was...
2013-06-02
951 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