Isn't that what I just said?

Use DBCC InputBuffer(@@SPID) within the stored procedure and it will tell you the exact query used to call the sp. You have to get a little tricky to be able...

You can't use variables as db object names. You need to build a sting and then execute it.

Declare @SQL varchar(1000)

Set @SQL = 'insert into ' + @tblVar + ' (somefld)...

I agree that the data model may need to be rethought, but I don't think he is trying to keep them identical. Frankly, I'm not sure what he's trying to...

Sorry, I should have left the 'Rush - 4 Weeks' in the query instead of using TimeFrame.

You can use the alias in the Orber By but not in the Group...

This will give you the Min and Max for every column without using a cursor. The generation of the SQL statement is lightning fast, but selecting a lot of Min's...

This will give you a syntax error: [PID.PQty]

I think you may want inner joins instead of left joins, but I have no way to know that for sure.

Try this out:

SELECT...

Exactly what part do you want to override, the seed value being the next available value?

Are these fields primary keys or is there otherwise a unique constraint? If not, then...

This error can also be caused by creating a package with a client that has service pack 3 installed yet the server only has service pack 2 installed even though...

To find out if this is the case, try to open the package. If it is a version problem, the package most likely will not open. It will give you...

Those are possiblities, but I would bet the farm that the real reason is that you do not have proper permissions.

One of the oddities of SQL Server is that it...

It's definitely a memory error. I would check to see if there is stuff running that shouldn't be including a check for viruses if you're not already protected (which I...

You can pass in the parameters to a stored procedure, use the parameters to build a call to the bcp utility and then use xp_cmdshell to execute the bcp...

I do stuff like this a lot. I get data in from a multitude of outside sources. These sources aren't always reliable, so I have QA checks built into all...

> but it fails on the "Set conn = Server.CreateObject('ADODB.Connection')" statement.

Remove the "Server." and use double quotes  instead of single quotes. Both of these items will give you an error....