What does the source data look like?

BTW, I was using 5409045121009 table structure. Also I didnt put in the leading zeros but that would be easy enough if you need it.

One more solution using derived table

update t1

set somethingiwant = t2.somethingiwant

from test as t1

join(SELECTid,

code+CAST((select count(*)

from test b

where a.code = b.code

and a.id >=b.id)

as varchar(10)) as somethingiwant

from test a

)as t2

on t1.id = t2.id

...

I noticed you mentioned sysfiles in your earlier post. Usually stored procedures created in master and prefixed with sp_ will run in the context of the database they are called...

Yes, if the dynamic sql is set based then you will need to put it into a temp table to be able to work with the data. If all you...

Ahhh, I didn't look at your code that closely. Now I see what you were talking about.

Antares answered the coalesce question.

Antares,

In the original query, rows with a NULL ErrorID would not have been returned if his @ErrNumStart was not null.

It would have evaluated...

Have you tried using a coalesce with a number that isn't valid for the variable like a negative number. e.g

AND(ErrorID >= COALESCE(@errNumStart,-1))

That will work just fine, but the variables scope is in the exec statment and it will go away as soon as it completes. You will not be able to...

That still does not change the database context except for during the exec statement.

The use is only for the duration of the execution.

You can see that by running this

declare @db nvarchar(50)

declare @db2 nvarchar(50)

set @db = 'use tempdb select db_name()'

set @db2 = 'select...

You can't. I'm pretty sure since I said that someone on here will figure out a way.

You really dont have to loop although you do have to build dynamic sql.

Here is an example.

CREATE TABLE Tests (name varchar(50))

GO

INSERT INTO Tests

SELECT 'Test1'

GO

INSERT INTO Tests

SELECT 'Test2'

GO

INSERT INTO Tests

SELECT...

This works... Notice how I doubled up on the single quotes. I think that may be your problem.

CREATE TABLE test (col1 char(1), col2 char(1))

go

CREATE PROC test_it @sqlVals varchar(10)

as

...

Here is a view I created similar to Antares without the huge IN clause...

It does require a numbers (sequence) table though.

CREATE VIEW dbo.PK_Columns_View

AS

selecto.nameASname,

o.idASid,

c.nameAScolumn_name,

n.idASsequence_number

FROMsysobjectsASo

JOINsysindexesASi

ONo.id =...