Showing posts with label SQL. Show all posts
Showing posts with label SQL. Show all posts

Wednesday, July 10, 2013

Performance on large tables


Data volumes are exploding in every business where a Database or BI professional might find himself. Subsequently data warehouse and decision support systems to keep up with this growth,  and are expected to perform at the same levels while offering even deeper insights into what the data is actually saying.

Monday, January 21, 2013

It Sounds Like...

Imagine a world where everyone had the spelling capability of a High School English teacher... Now snap out of it, because that's slightly delusional. Everybody makes the odd spelling mistake, especially when it comes to names, luckily there's a way in SQL to get around this...

Thursday, December 6, 2012

The tricky swamps of database versioning

If any developer have to draw a picture of most solutions, he/she usually draw the cylinder that represents the database first. Unfortunately when you start to apply version control to the solution, you start versioning the code first and more often than not completely omit the database from this process. One can ascribe this to the fact that database versioning can become relatively tricky, but also because few people understand exactly how to version a database.

Friday, September 21, 2012

SQL Index Fragmentation

SQL Indexing

Indexes are applied to tables to better performance in query execution, instead of the database engine searching through each and every row for the queried data, indexing provides an indexed subset of data that can be queried to get the required rows.

Monday, August 27, 2012

Isolation Levels


As a follow up to my NOLOCK blog I thought it would be a good idea to discuss the five different isolation levels in SQL Server. These are as follows:

Thursday, August 16, 2012

NOLOCK!

Introduction

I see many developers writing SQL code and using NOLOCK as a "performance tool". I see NOLOCK spread liberally through scripts, applied to every single table as far as the eye can see. This technique is dangerous and I would like to share why.

Thursday, July 5, 2012

Honey I Shrunk The Database


As a developer or a dba you may in your life have to shrink the log file of a database or you will have to shrink the database, because the server that the database is on is running low on space.
The syntax for a shrink statement is:

DBCC SHRINKDATABASE
( database_name | database_id | 0
     [ , target_percent ]  *
     [ , { NOTRUNCATE | TRUNCATEONLY } ]
)
[ WITH NO_INFOMSGS ]              

*For more information about how the target_percent or any of the relevant areas of the shrink database query works, reference the following link:

Friday, June 8, 2012

SQL Joins Explained

Introduction
For some reason I can’t remember the different types of joins or rather what exactly the differences are, I always confuse them (I’m hoping I’m not the only one).  I’ve noticed that a graphical ilustration usually helps, so I’ve added Venn diagrams to aid in the explanation.