Have you ever had the problem where a user ran a query against your SQL Serer and crashed it or made the server unusable since the CPU was spiked at 100%? A SQL Server black box is the equivalent of a flight data record. The black box records all queries being passed to your SQL Server and other useful information like errors.
We've all seen the numbers published about how well very db vendors do on the TPC tests - have you ever visited the site that sponsors the tests? Or looked to see what hardware and software configuration was used to achieve the score? Lots of good information on this site!
This week we have another article from Andy that discusses some changes he made at work in conjunction with clustering all his database servers. Not a how-to, just comments about what was changed and why. Worth reading just for the reminder about the potential gotcha that @@ServerName can represent.
Nothing super new here that has been rumored, this article outlines some of the changes we'll get to see in the next SQL release!
This article expands Steve Jones' look at ways to audit changes by examing how you can deal with the large amounts of data generated.
This is a product we haven't reviewed yet, but looks interesting. A SQL editor type app, features listed include integration with Visual SourceSafe, 'intellisense' statement completion, and keyboard macro's.
We've had a good run of jobs about job management lately, Randy sent us another one that looks at the job of job management and shows us how he tackled the problem.
Join SQLServerCentral.com co-founder Brian Knight for this free webcast on SQL Server security best practices. In this session on Technet, we will look at how to protect your system from internal and external security factors. We will look at the types of permissions in your database objects, implementing column and row-level security, and protecting yourself from SQL Injection attacks. We'll also cover best practices for basic and advanced protection for your SQL Server system.
It is always better to be proactive than reactive, when it comes to identifying and eliminating SQL Server performance issues. This article shows you how to analyze the data gathered by Profiler, to identify the performance issues. This article also provides four generic stored procedures for analyzing Profiler output.
Not even worth talking about, right? Probably, but they still exist. Read about this worst practice and pass it along.
Welcome back, my fellow sleuths, to my mystery-inspired blog series! I’m having a ton...
By Steve Jones
This was one of the original values: The facing page has this text: No...
By Chris Yates
For decades, enterprises have thought about data like plumbers think about water: you build...
Comments posted to this topic are about the item Create an HTML Report on...
Comments posted to this topic are about the item I Love Editorials
Hi everyone I have a 1000 plus line query and I am getting an...
What happens when I run this code:
DECLARE @s VARCHAR(1000) = 'apple, pear, peach' SELECT * FROM STRING_SPLIT(@s, ', ')See possible answers