Is Unit Testing Important?
Testing our applications is important, but at what level do we need to test? Steve Jones talks about unit testing today, and wonders if this is prevalent for SQL Server developers.
2009-11-10
696 reads
Articles
Is Unit Testing Important?
Testing our applications is important, but at what level do we need to test? Steve Jones talks about unit testing today, and wonders if this is prevalent for SQL Server developers.
2009-11-10
702 reads
Is Unit Testing Important?
Testing our applications is important, but at what level do we need to test? Steve Jones talks about unit testing today, and wonders if this is prevalent for SQL Server developers.
2009-11-10
667 reads
Writing Custom Rules for FxCop
FxCop is a useful tool for analyzing code to highlight potential issues and deviations from best practise. To fully utilize to power of FxCop, custom rules can be added to the inbuilt rules that ship with FxCop.
2009-11-10
1,639 reads
An Un-indexed Foreign Key Gotcha
Indexing is important for improving performance, but do you know that a lack of indexes might actually cause things to stop working? Alok Dwivedi brings us a very interesting scenario where the lack of an index causes a problem with concurrency.
2009-11-09
11,552 reads
A Bad Litmus Test
A litmus test is a way of determining your answer to a question based on a single issue or response. Steve Jones sees this as a bad idea, especially when looking to hire technical people.
2009-11-09
646 reads
A Bad Litmus Test
A litmus test is a way of determining your answer to a question based on a single issue or response. Steve Jones sees this as a bad idea, especially when looking to hire technical people.
2009-11-09
588 reads
A Bad Litmus Test
A litmus test is a way of determining your answer to a question based on a single issue or response. Steve Jones sees this as a bad idea, especially when looking to hire technical people.
2009-11-09
854 reads
What a Data Warehouse is Not
Recently, I was at a conference, and I heard the following discussion about what a data warehouse was. One person suggested that a data warehouse was really all the old legacy systems connected by software that could access the data. By calling such a contraption a data warehouse, the organization could avoid having to do the hard and complex work of integration. There are so many problems with this federated approach to a data warehouse that they are almost not worth repeating here. But (once again!) here goes.
2009-11-09
6,637 reads
Introduction to the Transaction Log
The transaction log is a fairly complex construct in SQL Server and present in every database installation. New author James Rea brings us a great introduction to how the log works and how to maintain it.
2009-11-06 (first published: 2008-07-02)
40,656 reads
Blogs
SQL Server Security: Always Encryption
By Vinay Thakur
As discussed introduction of Always Encryption blog and initial Encryption at rest as TDE...
SQL Server Security – TDE Encryption
By Vinay Thakur
Transparent Data Encryption(TDE): TDE was initially introduced in SQL Server 2008 Enterprise Edition; this...
A Las Vegas Break
By Steve Jones
Only a little break for me. I’m actually heading to Las Vegas today for ...
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