This doesn't help right now, but the recursive Common Table Expressions in Sql Server 2005 handle variable depth hierarchies really well. I guess deploying on a Beta platform isn't an...

"DELETE * FROM" is MS-Access syntax.

In SQL Server, it is simply "DELETE FROM TableName" (or "DELETE TableName") - I suspect the presence of the '*' implies columns and a resultset...

>>The table they are copied to needs to have a RecID though.

Right, but since it's unrelated to the intial trace table, why not just make it an IDENTITY type and...

How about:

Select * From YourTable Where 0 = 1

You'll either get a zero size resultset in very fast time, or an error if there's a problem accessing the table.

Ensure your C: and D: drives have the same NTFS security settings at the root level for the SQL Server account.

In Windows Explorer, when you right-click on the D: drive and select 'Properties', what does it tell you ? Is it of type 'Local Disk' ?

The problem with your subquery is that it is not correlated to the main select. try this:

select s1.*

from sample_table as s1

Inner Join

(

  select location_id, min(sample_depth)as sample_depth

  FROM  sample_table...

Depends on requirements.

Is there a requirement to preserve the original IDENTITY value from each hourly trace ?

If Yes, then you need a 2 column composite key in the history...

No, this was confusion based on the column names. "add1 and "add2" are not 2 separate addresses, but are 2 lines of the same address (eg apartment number, street number).

You...

You can't do this in Sql Server.

You need to either use Dynamic SQL, or create 1 stored procedure per table.

Couple of alternatives in this thread:

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=8&messageid=159332#bm159359

Can't answer the licensing question, but there are other tools.

Check out TOAD for Sql Server (Freeware):

http://www.toadsoft.com/toadsqlserver/toad_sqlserver.htm

You'll need to provide more info on what conditions(s) join the 2. It is not immediately obvious how row #1 in table1 (with a month of 1) would join to...

You would populate the address table from the DISTINCT addresses of you current sponsor table:

INSERT INTO tblAddress

  (add1, add2, city, state, zip)

SELECT DISTINCT

  add1, add2, city, state, zip

FROM tblSponsor

Then add...

Are there different connection parameters in effect for the debugger connection ?

Maybe some of the SET options ? (Longshot, but maybe some SET option would cause 'Oc' to be correctly...