Skip To Main Content
Dave Ballantyne on Muck Rack

Dave Ballantyne

As seen in: SQL Server Central
Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work. Claim your profile
Back to Dave Ballantyne’s profile

Articles by Dave Ballantyne

Club News: Erdington Court Winter Indoor Membership Up Since Open Day

|
By Dave Ballantyne
| suttoncoldfieldlocal.co.uk
Erdington Court ended the year with four evening and afternoon indoor leagues in full swing – with over 70 members in total taking part. Leading the Thursday night mixed triples League at present is the team led by Chris Hall – and including Dean Mortiboys and Denise Szostek. However this could all be about to change with the imposition of handicaps on the leading teams – based on their first half performance.
Open in Who Shared Issue with article?

Returning the Top X row for each group (SQL Spackle) – SQLServerCentral

|
By Dave Ballantyne, with cteRunners
| SQL Server Central
In our table we have a list of runners, the time the course was completed in and the runner's age. Our task is to retrieve the fastest X runners in each age range.
Open in Who Shared Issue with article?

Optimizing a cursor based routine – Part 2 – SQLServerCentral

|
By Dave Ballantyne, Select customerid, Purchase OrderNumber, MinTotal Due.Total Due
| SQL Server Central
In the first article of this series, we started to deconstruct a stored procedure with the aim of improving the efficiency of it. Hopefully, you will have been able to absorb that information and are now eager to see more. The number one reason I hear for creating a cursor routine is to allow for the conditional processing on a limited number of rows.
Open in Who Shared Issue with article?

Optimizing a cursor based routine – Part 1 – SQLServerCentral

|
By Dave Ballantyne, Select customerid
| SQL Server Central
When presented with a poorly performing stored procedure, there can be a one single statement that is to be optimized. However, more often than not this is not the case. There will be many statements each of which may perform well in isolation; the issue is the amount of times that they are executed. It’s a “Death by a thousand cuts scenario”. SQL is a language designed to work with large datasets and SQL Server works best when given instructions that exploit that.
Open in Who Shared Issue with article?
Show More