SQL Server Security Audit (Part 2) - Database Level Audit
The second in the Security Audit series looks at securing an individual database.
You Shouldn't Have Done That
We sometimes find ourselves in situations that we didn't count on. Or that aren't necessarily a mistake we made in the installation. Steve Jones reminds us that we should keep that in mind when someone is asking for our help.
You Shouldn't Have Done That
We sometimes find ourselves in situations that we didn't count on. Or that aren't necessarily a mistake we made in the installation. Steve Jones reminds us that we should keep that in mind when someone is asking for our help.
You Shouldn't Have Done That
We sometimes find ourselves in situations that we didn't count on. Or that aren't necessarily a mistake we made in the installation. Steve Jones reminds us that we should keep that in mind when someone is asking for our help.
Go Get an iPhone
This week Mobile BI is on the radar at Microsoft. Steve Jones comments on what this might mean for the database people in the future.
SQL Server 2008 T-SQL Enhancements Part - V
The fifth installment of Arshad Ali's series examines the spatial data types in SQL Server 2008. These new types allow the use of geospatial data in SQL Server applications.
What Data Should You Protect?
Perhaps we need to protect more data, according to Steve Jones. With the ability to identify most people with 10 digits of information, Steve Jones asks you to really think about what you need to store.
Building Code that Promotes Plan Re-usage
This article, the third in the T-SQL Best Practices series, discusses how to write your code to promote cached plan re-usage. Understanding how white space and comments impact whether a plan is cached or an existing plan is re-used can help you minimize the number of plans your application is caching.
How to find, compare and use the exact same session settings as another user in SQL Server
When diagnosing issues in SQL Server I've found that sometimes I need to be able to mimic a user's session state when attempting to repeat an error they may be receiving. The smallest differences can completely change the outcome, so I need to ensure all the session settings (QUOTED_IDENTIFIER, ANSI_NULLS, and so forth) are identical between the production session and my test session. Is there an easy way to determine these settings with a single query?
What Data Should You Protect?
Perhaps we need to protect more data, according to Steve Jones. With the ability to identify most people with 10 digits of information, Steve Jones asks you to really think about what you need to store.
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