SQL Server 2008 users should definitely consider using MERGE. MERGE will avoid having to do multiple scans/seeks in many cases.

http://blogs.conchango.com/davidportas/archive/2007/11/14/SQL-Server-2008-MERGE.aspx

Maybe it doesn't apply to your case but be aware that there is a nasty gotcha with BINARY_CHECKSUM(*). The checksum is determined by column order rather than name. So if...

Go to

http://code.google.com/

You'll find all the information about Google APIs and how to integrate with their services.

Hi DCPeterson,

Thanks for reviving the discussion.

I'm not sure I understand your argument. I agree with you when you say that if we had a truly relational language and platform then...

Please could you post the code here.

In your Access query, FIRST just retrieves a value of the name column from some random row. Assuming you don't actually require a random result but don't mind which name...

The "set based" model really means the Relational Model, on which SQL is based to a certain extent. It separates the data model from its implementation. Independence from ordering and...

I recommend you start by reading this book:

http://www.amazon.com/Introduction-Database-Systems-Eighth/dp/0321197844

The straightforward answer to your questions is that SQL Server is designed and optimized to work well with set-based SQL logic (more...

I agree! Date and Darwen do too. They included RM Proscription 10 in The Third Manifesto: "D shall not be called SQL"!

Date's book is a must-read.

Tropashko's book is already out. I got mine here: http://www.bookpool.com/sm/0977671542. I have to admit I was a little disappointed. It does contain some interesting nuggets but there wasn't...

In a nutshell, I'd expect to see all the benefits that the relational model promised but that SQL doesn't always manage to deliver on: derivability, integrity, data independence, guaranteed access.

As...