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
In my experience, FinOps success has never been just about tools or dashboards. It...
By HeyMo0sh
As a DevOps person, I know that to make FinOps successful, you need more...
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers