The return value of a stored procedure can only be an integer. Stored procedures are not really designed to return data like this. The return value is there...

Another solution would be to simply join to the detail again.

[font="Courier New"]Select

oph.order_no

, opd.order_line_no

, opd.product

, opd.quantity

, opd2.product as OtherProduct

, opd2.quantity as OtherQuantity

From

OrderDetail opd

inner join OrderHeader oph on opd.order_no = oph.order_no

inner join...

Please don't cross-post.

http://www.sqlservercentral.com/Forums/Topic583449-148-1.aspx?Update=1

Please don't cross post.

http://www.sqlservercentral.com/Forums/Topic583444-391-1.aspx

I am not sure what you think you are gaining by installing the 32 bit version of SQL.

Have your ops guy install the 64 bit OS. Then you can...

Good idea Grant.

If it is the global temp tables, the locking behavior will still continue.

If it isn't, you will quickly find out what process is updating data - because it...

SSIS 2005 requires using VS2005. You cannot use VS2008.

On the happier side, both version of VS can reside on the same machine. Install VS2005 (or leave it installed)...

Add a variable to your package and increment the variable within the ForEach loop. If there are no files, the variable will remain zero and you can check it...

You will find lots of postings on this site about this subject, so search around a bit.

I have had good and bad experiences with it and at this point I...

If you only have shared locks, you cannot generate a deadlock. The only possibility would be if there ended up some kind of deadlock within the system tables while...

In SQL 2005, DTS (Data Transformation Services) was replaced by SSIS (SQL Server Integration Services).

Development for SSIS packages is done using the Business Intelligence Studio - which is a project...

The SCD wizard generates an OLEDB Command component that essentially updates every field regardless of it having changed. So, if any field on a record is changed, it updates...

Unless you can really ensure you will never hit the 8k limit for a record size, even SQL 2008 is not going to help you.

If you want to use SQL...

While it is running, look for tables in tempdb:

SELECT * FROM TempDB..Sysobjects WHERE Type = 'u'

A table variable usually has to get pretty big before it spills over into TempDB.

If there are no objects in the schema, drop away.

If you upgrade a database from SQL 2000 to 2005 or 2008 you can end up with some schemas that have...