Wake up Win America’s Cup Take the day off
The newly released SQL Server Diagnostics (Preview) can be found here.
Below are the install screenshots
Once installed it is accessible via SSMS
Dumps are usually located in your …MSSQLSERVER\MSSQL\Log folder.
Here I also selected to send an email just to see what it’ll look like.
The email received was
The other Diagnostics options were
Looks a bit of a cover all at the moment
Takes you to the below site (which no longer exists)
It’ll be sad to see the default trace go. It’s help me out numerous times during onsite consults when monitoring has not been in place. It really is one of the good features introduced in SQL Server 2005.
The deprecated features list is a bit of an unknown as there is no fixed version/date set by Microsoft, so when it’ll finally goes is anyone’s guess. Hopefully by that stage extended events will be more palatable.
Troubleshooting performance issues can be challenging and more so when 1 user has issues and another doesn’t for the same application and they both sit in the same room.
This is where SSMS Include Client Statistics may come in handy.
Enable the option and run the query causing issues on both users machines.
Possibly you the results will help point you in the correct direction i.e. network path issues etc..
Remember to unselect the option when finished as it adds extra overhead when used.
Yes as detailed here
“There will be two primary release channels available to Windows Server customers, the Long-term Servicing Channel, and the new Semi-annual Channel.”
When installing SQL Server the key thing to remember is:
“Windows Server products in the Semi-annual Channel will have new releases available twice a year, in spring and fall. Each release in this channel will be supported for 18 months from the initial release.”
18 months = 1.5 years so not very long and given that SQL Server releases are typically every 2 years, I’m not sure how viable this the new Semi-annual Channel will be for hosting SQL Server. Time will tell.
What is really interesting is that, to me, it appears that Microsoft may have gone from a market leader to a follower, I could be wrong:
Here at AKAWN we’ve been busy working on our first application which we hope to release later this year.
Having purely been focused on SQL Server architecture, administration and consulting, it has been a real eye opener into the effort required to produce an application.
So to all those developers out there a big thanks for your efforts, you guys rock.
This post got a bit side tracked :) it was meant to advise that .NET Framework 4.7 is available on Windows Update, WSUS, and MU Catalog.
Wow, you never really grasp the meaning of plagiarism until it happens to you.
Recently a couple of AKAWN blog articles have appeared on a popular SQL Server website. The person has tweaked the wording and images but it is clearly a copy.
Copying other people’s work and passing it off as your own is NOT cool.
If this person, who I assume follows this blog, does it again, I won’t hesitate to out them. You’d think a MVP would know better.
As an absolute minimum, a reference should be made to the source of your content when using another person’s work.
When working with dates/times it can sometimes get a bit confusing when abbreviation options are introduced e.g. abbreviations may pad 0’s,use 24hr (HH) vs 12hr (hh) etc.
This post is simply a confirmation that abbreviations in datediff and datepart do return the same value.
DECLARE @starts datetime = '2017-06-12 19:00:05' , @ends datetime = '2017-06-12 19:00:07'; SELECT DATEDIFF(ss,@starts,@ends) AS diff_ss , DATEDIFF(s,@starts,@ends) AS diff_s , DATEPART(ss,@starts) AS part_ss , DATEPART(s,@starts) AS part_s;