Greg Low

SQL Down Under

Dr. Greg Low is an internationally recognized consultant, trainer and author. He is a SQL Server MVP and a Microsoft Regional Director for Australia. Greg holds a PhD in computer science and is a Microsoft Certified Master for SQL Server. He is the author of a number of Microsoft white papers and is a sought-after presenter. Based in Melbourne, Dr. Low is the CEO of SQL Down Under and is well known for his SQL Down Under podcasts on SQL Server topics. Read his blog here.

Data Tales #3: The Case of the Stubborn Log File
The transaction log continues to grow despite regular backups. Diagnosing the issue and preventing it from happening again is what this case is all about.
Data Tales #2: The Case of the Exploding Table 1

I was recently at a customer site where the developers were very concerned about the impact of adding columns to a table. They told me that when they added a new column that their deployment code was timing out and the database was massively increasing in size. It had increased from around a small size to well over 50GB during the single operation. The deployment operation involved adding the column and writing one row to a deployment history table. Because they were only writing a single new row, they were blaming SQL Server for bloating the database size when a column was added.

Data Tales #1: The Case of the Auto-Truncating Table

I have a number of clients that I spend a day or two with each month. I like this style of engagement as I get to know the staff and their systems over a period of time, can see the improvements that we make over time. The staff members also know that if they have issues that aren't desperate, they can save them up for the days that I am onsite. When I arrived at one of these customer sites recently, several of the staff members had grins on their faces, and one told me that Terry (well let's call him Terry anyway) had really broken something.

Configuring SQL Server 2008’s Resource Governor 1
Prevent database performance problems by using Resource Governor to control the CPU and memory allocated to applications.

Digital Magazine Archives

Browse back issues of SQL Server Pro, from January 2007 through the last issue published in April 2014. Find the back issues here.


From the Blogs
Sep 15, 2015

Setting Up Additional Checks to Ensure Regular Transaction Log Backups 1

There’s simply no way to overstate the importance of regular Transaction Log Backups. Not only do they help protect from disaster, but regular execution of T-Log backups on Full (and Bulk-Logged) Recovery databases helps keep thing “fit and trim”. Most of the time, setting up a Notification for when T-Log Backup Jobs fail is enough to let you know when something goes wrong....More
Sep 1, 2015

Stop Using INFORMATION_SCHEMA and SysObjects for Exists Checks 3

Code like this isn’t optimal: IF EXISTS(SELECT * FROM sys.objects WHERE name = N'TableToDrop' AND type = 'U')         DROP TABLE TableToDrop; GO Neither is this: IF EXISTS(SELECT TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = 'TableToDrop')         DROP TABLE TableToDrop; GO Yet, I see both of those used all of the time – over and over again. Even though it’s 2015.  ...More
Aug 27, 2015

A Replacement for Maintenance Plan Backups 1

This blog post is a bit of a ‘repeat’ – since I already covered much of the rationale behind this post in Part 23 of my multi-part series on AlwaysOn Availability Groups and SQL Server Agent Jobs. But, I also figured that this is enough of an important topic to merit its own blog post....More
SQL Server Pro Forums

Get answers to questions, share tips, and engage with the SQL Server community in our Forums.

Sponsored Introduction Continue on to (or wait seconds) ×