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.
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.
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.
#SQLPASS on Twitter
With the PASS Summit taking place last week in Seattle, Steve Jones found that there was a tremendous amount of SQL Server news and information on Twitter. It's a medium that is becoming useful for SQL DBAs.
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.
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.
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.
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.
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.
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.
Blogs
Five Ways Redshift Serverless Quietly Eats Your Budget
It is Friday, the queries are running, and nobody is watching the bill. That...
A Career of Memories
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
Rethinking Index Maintenance: Why avg_fragmentation_in_percent Is Outdated and What You Should Do Instead
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Forums
Changes, Happiness, and a Few Tears
Comments posted to this topic are about the item Changes, Happiness, and a Few...
BCP on Linux
Comments posted to this topic are about the item BCP on Linux
You Probably Don't Need a Vector Database
Comments posted to this topic are about the item You Probably Don't Need a...
Question of the Day
BCP on Linux
When running bcp on Linux, what is the field terminator?
See possible answers