Believe in Your Data - Database Weekly (Aug 25, 2008)
As DBAs we must secure and protect data, but what can we do when there are fundamental issues with the way the systems are designed. Steve Jones comments on problems with voting machines.
If You Ain't Cheatin'
Gaining recognition or an award without earning it is something Steve Jones thinks is a problem in society in general, and it's filtered into the IT industry.
If You Ain't Cheatin'
Gaining recognition or an award without earning it is something Steve Jones thinks is a problem in society in general, and it's filtered into the IT industry.
If You Ain't Cheatin'
Gaining recognition or an award without earning it is something Steve Jones thinks is a problem in society in general, and it's filtered into the IT industry.
Managing Security
This Friday Steve Jones comments on the practice of using Active Directory to help manage your SQL Server and what the best practice should be.
Believe in Your Data - Database Weekly (Aug 25, 2008)
As DBAs we must secure and protect data, but what can we do when there are fundamental issues with the way the systems are designed. Steve Jones comments on problems with voting machines.
Believe in Your Data - Database Weekly (Aug 25, 2008)
As DBAs we must secure and protect data, but what can we do when there are fundamental issues with the way the systems are designed. Steve Jones comments on problems with voting machines.
Concatenating Row Values in Transact-SQL
It is an interesting problem in Transact SQL, for which there are a number of solutions and considerable debate. How do you go about producing a summary result in which a distinguishing column from each row in each particular category is listed in a 'aggregate' column? A simple, and intuitive way of displaying data is surprisingly difficult to achieve. Anith Sen gives a summary of different ways, and offers words of caution over the one you choose.
Recover from a SQL Injection Attack on SQL Server
Lately it seems like SQL Injection attacks have been increasing. Recently our team has worked through resolving a few different SQL Injection attacks across a variety of web sites. Each of these attacks had a number of similarities which proved to point back to the same source. With this information in hand, the resolution should be much quicker. As such, if your web site is attacked with SQL Injection, how should you address it? How can the identification, analysis, recovery and resolution be streamlined? What are some lessons learned?
Creating Lift Charts - SQL School Video
This video covers lift charts, an advanced data mining feature in SQL Server 2008. MVP Brian Knight walks through a data mining example that tests a model with a lift chart.
Blogs
Did You Really Name That Default?
By alevyinroc
Ten years (and a couple jobs) ago, I wrote about naming default constraints to...
Monday Monitor Tips: A New Analysis Page
By Steve Jones
We have multiple teams (8) working on Redgate Monitor. Some work on the Standard...
Case Studies: Real-World Success Stories of FinOps Implementation
By HeyMo0sh
Learning any kind of theory is easy, but adapting FinOps and watching it rescue...
Forums
The day-to-day pressures of a DBA team, and how we can work smarter with automation and AI
Comments posted to this topic are about the item The day-to-day pressures of a...
The Problem Isn't Always Your Query or Schema... Sometimes It's Hidden Assumptions
Comments posted to this topic are about the item The Problem Isn't Always Your...
Identity Defaults
Comments posted to this topic are about the item Identity Defaults
Question of the Day
Identity Defaults
What happens when I run this code?
CREATE TABLE dbo.IdentityTest
(
id int IDENTITY(10) PRIMARY KEY,
somevalue VARCHAR(20)
)
GO
See possible answers