Additional caveat: although the Lazy Evaluation gives a neat way of not using concatenated strings and dynamic sql, it can only really be used on small tables - I've just...

This is the sort of thing you could use:

--drop table TblTest

--go

create table TblTest

(

SupplierId int null,

CompanyID int null

)

go

insert into TblTest (SupplierId, CompanyID) values (1,10)

insert into TblTest (SupplierId, CompanyID) values (2,20)

insert...

Here is the link:

http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=96&CategoryNm=T-SQL%20Aids&CategoryID=19

This will take a little while to write so I'd start with a small version using a couple of variables and check out the query plan -...

Nice, clear article - I think if I come across this type of system in the future I'll easily recognise it now. Not sure that I would choose to implement...

Looking at the used memory is a little misleading, because SQl will cache the compiled sps and table data until it uses up the available memory, so in your case...

Haven't reviewed Red-Gate but still might be worth trying the DTS route. I have a setup which copies objects between servers using the copy objects task - all objects, sps,...

Several posibilities come to mind.

If you're happy doing this manually, just highlight the tables, sps etc in EM and right click, All Tasks, Generate SQL Scripts. You can also script...

Might be relevant to NT:

Win 2000 Server supports a maximum of 4 processors.

Win 2000 Advanced Server supports a maximum of 8 processors.

Paul Ibison

Paul.Ibison@btinternet.com

Full-text indexing could be used for probably the subject column but be aware that wildcards are not valid at the start of the argument, so a direct replacement of %Subject%...

Have a look at Page 2 of this forum - there is a relevant thread ("Select * from @var" possible?") which will probably answer your questions.

Paul Ibison

Paul.Ibison@btinternet.com

You could run a profiler and correlate this with the increate in RAM useage from Performance Monitor and this might clarify the issue. When I discovered this site I had...

Thanks, Andy - nice to know I'm on the right track. One final question though: I intend to use log shipping between the 2 SQL 2000 boxes, and I know...

My guess is that this is not a high enough severity level to generate an error as such - more of a warning. If it's not in the error log...

I'd import the data into a staging table having two fields. Then use a cursor which iterates through the new table and inserts each company/accountno pair into the final table....

If you use a go after the alter table it should work ok - eg:

create table #dummy

(

PERSONAL_REFERENCE varchar(10)

)

insert #dummy ( PERSONAL_REFERENCE )

values(1)

alter table #dummy add STAFF_NAME varchar(60) NULL

go

update #dummy

set #dummy.STAFF_NAME...