FROM BOL, CREATE TABLE

If more than one temporary table is created inside a single stored procedure or batch, they must have different names.

My main procedure and the procedure it was calling both had a temp table called #Accounts. I changed the name in the called procedure and it worked. Thanks again to...

Below is what I have tried and the errors created.

INSERT INTO #Accounts (#Accounts.Account) VALUES (@Account_Group)

Error: Invalid column name 'Account'.

INSERT INTO #Accounts SELECT @Account_Group

Insert Error: Column name or number of supplied...

I have isolated to an insert into a temp table here. This is the proc being called.

ALTER PROCEDURE [dbo].[myProc]

@Account_Group varchar(50),

@Type varchar(10),

@SessionID int

AS

CREATE TABLE dbo.#Accounts (Account varchar(50))

IF...

Thanks you for responding. There doesn't be a schema problem.

I can change the procedure to use

EXEC myproc @A, @b-2, @C

I altered the procedure and still got the same behavior....

I would make a copy of the table using the CREATE TABLE statement. Say the new table is called ItemsTest. Then you could run this

INSERT INTO dbo.ItemsTest

(

Code,

Name,

Description,

Price,

UnitOfMeasureID,

RevenueTypeID

)

SELECT

Code,

Name,

Description,

Price,

UnitOfMeasureID,

RevenueTypeID

FROM dbo.ItemsStaged

If this...

Another thing you might try is importing the data into a staging table, not your final destination table. The import wizard will create this table for you.

Then post the...

The original drives were overprovisioned. The SAN tools can migrate the LUNS but they would remain the same size. We want the new drives to be smaller. Now I am...

Thank you. Your suggestion is working for me.

Thanks to all who replied. It is a situation where the data can be either a number I need to calculate with it or a textual code, not a combination...

Hello,

You can...

See this thread. http://sqlblog.com/blogs/andrew_kelly/archive/2008/02/27/when-getdate-is-not-a-constant.aspx

You may get different results by referencing getdate() multiple times.

Putting aside ISNUMERIC and its issues I still don't understand why a CONVERT would work when selecting a field but not in the WHERE clause.

Is it possible that the comparison...

Can LIKE '%0-9%' be adapted if my data is like the following?

100.00

75.99

99.00

Yes it does. My apologies. I have overlooked the obvious....