One or more of the columns in your group by has different values for one departure airport. Can't say which one without seeing a sample output from your query.

Thanks for that.

I think I have enough ammo now. Going to see if I can get a meeting on monday. The san 'experts' won't be there, since they're in London,...

If moves pages as early in the file as possble (generally causing massive fragmentation in the process), then releases unused space to the OS. This depends on the settings you...

Found a couple of SQLCAT blog posts:

Deploying SQL Server 2005 with SAN #1

SQL Server 2005 Configuration Blog #2.doc

Deploying SQL Server 2005 with SAN #3

That you need to do a log backup before the space in the log file can be reused.

Neither differential nor full backups truncate the log. Only log backups do that.

If...

Don't shrink the database. It shuffles index pages, causing fragmentation, and generally is not necessary.

Rebuilding indexes creates very large transactions. When the backup log occurs, active (uncommitted) transactions cannot be removed from the log.

You may find it's necessary to grow the log a bit...

Info on buying Standard edition:

http://www.microsoft.com/sql/editions/standard/howtobuy.mspx

For standard edition, you're looking at around $6000 per processor or $1800 for 5 CALs, depening which type of licencing you want.

What does the log_reuse_wait_desc column in sys.databases say?

Are you doing index rebuilds or other large transactions around the time of the error?

Do you have replication active on that DB? Mirroring?

Express is freely available, standard is not.

http://www.microsoft.com/sql/editions/express/default.mspx

Deny overrides grant, so you can use deny to override grants if the user in question is in more than one role.

The built-in roles don't have anything for just exec...

Not with any SQL backup tool. They allow you to backup the entre database or a file of the database.

You could export the table to CSV. You could make a...

The user on the database that your published site uses does not have select permissions on the tables. It's probably just got exec on the procs.

Inline SQL (especially if concatenated...

Seconded. Shrink = really bad idea.

It also appears you don't have an index rebuild happening anywhere. Is that the case?

To prevent SQL injection completely:

- Use only stored procedures or properly parameterised queries from your web app

- Do not concatenate SQL statements and execute them. either in the web page...