It doesn't work for me... I only get 483 messages back on google. I remember having 1-2 more than that!

If you look at the 2nd query if see a key lookup. That happens when the server uses an index to find the correct data to match the where...

That's what anaylisis services and cubes where built for.

Sharepoint might also be a solution if they need to share a lot of their work and input "changes" in the reports...

Nothing we can do about point 1 and I can't confirm without going there myself...

For point #2

http://www.codeproject.com/KB/database/DiagnoseProblemsSQLServer.aspx

Some ERPs I've worked with are installed client side. That's mostly where I'm coming from.

AS For HDs and format queries, I wouldn't worry too much about this. The...

It's not that expensive... once the data is in ram it's pretty fast.

Also if you want your program to always display exactly the data that the view/query/sp returns it's a...

That gets a list of columns that the query will return (format only).

The where 1<2 makes sure the sql returns the columns without having to run the query at all...

The code compiles fine with me on 2008.

The error I'm getting in 2005 is that substring requires an int for its input parameters. If you change those 2 variables...

Ya that's what I meant in my first message... but how do you do error handling in this method?

I mean once you start reenabling all the constraints, it must fail...

Don't worry Jeff, that concept took about 2 hours to sink in my thick skull. ...

1 - What is slow? 2 secs per run times 1000 run is obviously a long time to wait after something. However what would be a fast run...

also one last thing to note... a covering index could make this query fly without hurting inserts too much...

create index whatever on dbo.TblName (part_number, workstation) INCLUDE (date_entered).

But again...

Are those times in seconds or is it another figure?

If it's seconds and assuming that query won't run 100 times a second, then there's no real need to tune it...

This is a simple one...

select workstation, date_entered from inventory where part_number='ABC' and workstation>=5 order by workstation, date_entered;

if @@rowcount = 0

--make this call another sp to get the best execution...

More to the point... this is really an ETL task...

Download data, validate it first, then reinsert the valid data and warn about problems.

No real need to flush out the fks...