Whatever order the optimiser feels is best, based on it's knowledge of the data distribution statistics and the indexes that are available on the tables.

Whatever order the optimiser feels is best.

That said, it is considered beter to join in the from clause, rather than the where clause. for readability, if nothing else.

SELECT * FROM...

What you're asking doesn't make sense. Do youi want to add new records to tb1, or do you want to update fields of existing records in tb1 to a value...

This is one case where cursors are pretty much required.

There's no automatic syntax for executing a stored proc and taking params from a query result.

My pleasure. I'm glad it's fixed.

Weird. That's a little slow, but not close to causing a timeout. Even the default value is 5 min.

How long does it take from the web page?

No idea. The .net docs should tell you.

That's already a pretty high value. how long does that query take in QA?

Not the timeout in the config. Is something like cmd.Timeout in the code, after you create the  command, but before you execute it. Not a C# expert.

For blocking, run sp_who2...

Different databases, or different tables? Looks like the latter, assuming that it is.

This isn't tested, but it should be mostly right.

SELECT HH_ID, StudentID, MAX(Parent_ID) As ParentID

FROM ParentDatabase P INNER JOIN...

select

suser_sname()

Returns <Domain>\<Loginname>

Many ways, but it depends greatly on what the root problem is.

Have a look in the performance forum, iirc there are a few posts on getting started with monitoring...

However, if you're still using SQL 2000, then the max datatypes are not available (New feature in 2005) and you're stuck with TEXT for large text strings.

The error has more to do with the wierd way text fields behave than anything wrong with your parameters. You might have some success using READTEXT, but I don't really...

What you're trying to do can't be done in SQL 2000 (function in FROM with parameter been a field from the query). It's a new feature in SQL 2005 (CROSS...

In theory

CREATE PROCEDURE TestOutput (

 @InputParameter INT

 @OutputParameter INT OUTPUT

)

AS

.....

DECLARE @Result INT

EXEC TestOutput @InputParameter = 1, @OutputParameter = @Result OUTPUT

Note the OUTPUT keyword, both when creating the stored proc and wne...