I missed the min statement last time - but look closer - this does return percentages of total.  The only thing it doesn't do is make the number coming out...

First thought would be: don't use the new PIVOT notation for that - go back to the "old" SQL2000 notation, using the CASE statement instead.

something like:

select molag,

sum(case when causecd='hc' then...

Also - since they are related terms, you might care to get REALLy familiar with the additional concepts below:

For data tuning, you might care to look up "database performance tuning"...

I forgot one:

• you REALLY need to think through the failover behavior at the windows cluster level.  The default behavior (fail immediately to the other node, and if the service doesn't...

I've had some exposure to clustered installs, but I hardly qualify as an "expert" in them.  that being said, a few things I've learned:

• Active/passive scenarios are fine for improving uptime, but...

Jaime -

are you trying to return the count next to EACH ID, or are you looking for any one of the ID?

If door #1 you'd want something like:

...

Subu -

What are you looking for?  Kenneth's definitions are fine, just very succinct.  It's just that without knowing what you're looking for, you've got the 1-line definition level, and...

You probably want to go into the Surface Area configuration, and turn on "remote connections".  I'm pretty sure that ODBC is considered a remote connection (even if the connection is...

I'm not sure what specific differences you're seeing, but here's one or two you MIGHT be seeing: your version would allow for "ties", whereas Peter's does not.

I don't know what these...

"Your lightbulb has performed an illegal operation and will be shut down"....

You're going to need to create this as a stored procedure and invoke it - that will change your OpenRecordset syntax somewhat.

--build your scratch table to...

MSAccess was where I ran into First() as an aggregate function.  It was at first glance a bit useless, but it was actually used to help make your queries run a...

Don't post any specifics you aren't ready to back up in a legal proceeding.  Remember Google - this site is regularly indexed - so any name posted will link back...

You CAN build indexes on temp tables.  You just have to build them each time you build the table.  You'd also want to tear them down when you're done.

This also...

Dynamic SQL is the key.  If you're hell-bent on issuing a USE statement then use something like this:

declare

@sql varchar(200)