Expanding on the issue of reviewing software for SQL Server, Steve Jones proposes some standards for reviews in this article. Please take a moment to read and comment on this proposal to better help SQL Server Central.com provide you with the information that you need.
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.
By HeyMo0sh
Working in DevOps, I’ve seen FinOps do amazing things for cloud cost control, but...
Every organization I talk to has the same problem dressed up in different clothes....
By DataOnWheels
I am delighted to host this month’s T-SQL Tuesday invitation. If you are new...
Comments posted to this topic are about the item The day-to-day pressures of a...
Hello all, I’m looking for advice on how to derive a daily snapshot table...
We need to replace our Windows server running SQL 2017. Any reason not to...
I have some data in a table that looks like this:
BeerID BeerName brewer beerdescription 1 Becks Interbrew Beck's is a German-style pilsner beer 2 Fat Tire New Belgium Toasty malt, gentle sweetness, flash of fresh hop bitterness. 3 Mac n Jacks Mac & Jack's Brewery This beer erupts with a floral, hoppy taste 4 Alaskan Amber Alaskan Brewing Alaskan Brewing Amber Ale is an "alt" style beer 8 Kirin Kirin Brewing Kirin Ichiban is a Lager-type beerIf I run this, what is returned?
select t1.[key]
from openjson((select t.* FROM Beer AS t for json path)) t1 See possible answers