Performance implications of the placement of an aggregate function in SQL

Just happened across this last week in some old documentation I’d kept. I ran into this years ago and it is a good example of the care you should take in using aggregate functions. I believe this was in an Oracle 10g database. I also believe when it was in PostgreSQL this didn’t cause an issue.

Performance implications of the placement an aggregrate function

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s