Speeding up Data Access Part 1 - Missing Indexes
In the first part of this series, learn how to pinpoint missing indexes in your databases.
2011-07-19
18,199 reads
Articles
Database Size Survey
Help us collect some data on the sizes and counts of databases in your environment. Take a few minutes and answer this survey.
2011-07-18 (first published: 2011-07-01)
3,232 reads
JSON.SQL: A CLR-resident JSON serializer/deserializer for SQL Server
One CLR function and four CLR procedures for the import/export of JSON data to and from SQL Server are presented, with supporting performance metrics.
2011-07-18
17,884 reads
Migrating SQL Server Databases – The DBA’s Checklist (Part 1)
It is a fact of life: SQL Server databases change homes. They move from one instance to another, from one version to the next, from old servers to new ones. They move around as an organisation’s data grows, applications are enhanced or new versions of the database software are released.
2011-07-18
3,616 reads
SQL Saturday #80 - Wheeling. WV
Come get a free day of SQL Server training in Wheeling on Jul 23, 2011.
2011-07-18 (first published: 2011-06-22)
2,518 reads
SQL Overview SSIS Package III - Full Package
Continuing on with his series on reporting for your SQL Server, David Bird brings together the series with the full package used for building the report.s
2011-07-15 (first published: 2008-01-22)
21,683 reads
Yet Another SQL Strategy for Versioned Data
There is a popular design for a database that requires a built-in audit-trail of amendments and additions, where data is never deleted, but superseded by a later version. Whilst this is conceptually simple, it has always made reporting the latest version of data complicated. Alex Kuznetsov joins the debate on the best way of doing this with an example using an indexed view and the filtered index.
2011-07-15
3,274 reads
2011-07-14 (first published: 2009-06-10)
7,122 reads
Second Normal Form
In this article Tom Thomson takes a look at what second normal form means, how it is violated, and how you can fix it. This is part of our normalization series.
2011-07-14
8,139 reads
Identifying PII Data to Lock Down in SQL Server - Part 1
We're pretty confident that we have locked down and encrypted our financial data, but a lot of our customer's PII (Personally Identifiable Information) data is still held in unencrypted form. This data is able to be selected directly by read only business users on many of our downstream reporting, datawarehouse and standby servers. The rise of identity theft makes protecting this data imperative. DBAs are the custodians of this information and must protect it like we protect our own personal information. Recent publicity over the theft of Sony PSN data underscores both the economic and ethical importance of protecting personal data.
2011-07-14
2,864 reads
Blogs
Architecting Zero Downtime Deployments–Day of Data Boston
By Steve Jones
Here are the resources for my talk at Day of Data Boston. Slides –...
The Book of Redgate:A Prehistory
By Steve Jones
I’ve covered the values in a number of previous posts on the Book of...
Evidence-bound: what AgentDBA will and won’t link
By Arun Sirpal
When the evidence names the database, it says so. When it doesn’t, it stops....
Forums
Azure SQL Database Event Log Limitations
Hi, Do you know if there is a way to get more detailed logging...
Four Rules for Adding AI Without Breaking What Already Works
Comments posted to this topic are about the item Four Rules for Adding AI...
SQL Server 2025 section missing?
Hello, the title says it all. Is the SQL Server 2025 section missing?
Question of the Day
Hyperscale Replicas III
In an Azure SQL Database Hyperscale Edition, how many named replicas can be configured?
See possible answers