Because you're grouping on everything, you'll get the max date for a distict select. You might want to look at something like:

SELECT c.consultantid

...

Yes.

Oh, a little more? Fine.

You can do either. The preferred approach when building applications is to create...

Another question far too dense to answer in a forum like this.

However, a few pointers (and, as with everything in SQL Server, there are exceptions to every one of these...

Another variation on what everyone else has done would be this:

SELECT a.OH_DOC_TYPE,

a.OH_DOC_NUM,

a.OH_PO_NUM,

...

I doubt it's going to help, but you can call this in a cross database query. I used the example from BOL:

SELECT 'Index Name' = i.name, 'Statistics Date' = STATS_DATE(i.object_id,...

Darn it. Late to the game.

Everything Matt said.

😀

Nope. Not through anything available in the system for your basic queries. There is a way to output status on restores & backups & such.

You can do this:

INSERT INTO MyTable1

DEFAULT VALUES

Then, with that, you can capture the values you inserted like this:

CREATE TABLE #Id ( id INT )

INSERT INTO onecolumn

OUTPUT inserted.id

...

It means your joins are probably returning more than one row from one of the tables. That's a pretty normal occurrence when using left joins. I'd first investigate the data...

Bloody hard and tedious work awaits.

You have to update all the data and find the different variances for the company names. Worst possible problem to have. Follow the steps outlined...

I think Sarvash hit the issue with the single quotes.

Instead of "3/3/2008" in your SQL code. It should be '3/3/2008'

Single quotes define a string, not double quotes, in TSQL.

That's a huge collection of really fundamental questions that just aren't going to be answered easily in a little post in a discussion group.

In terms of database design, you should...

Yeah, Brandie is right, kick your monitor "accidently" across the room. Keep Mr. Murphy happy!

I am definately going to try the "Fear is the mind-killer" chant next time we're deep...

Ah, well, that makes sense then. Still, I think you'd be able to avoid the scan. Look at the execution plan and see what criteria are being used by the...

TheSQLGuru (3/7/2008)

---

I guess someone has to play devil's advocate here, so here goes:

Brandie, you are totally off the mark. Do whatever you can to make the most money so...