I might be missing something, but why not do it in a single set based operation?

INSERT INTO tAppUser(x,y,z)

SELECT x,y,z

FROM [Mercury Cvt Temp].dbo.tApplicationUser AS tAppUser

WHERE ....

the registered version of Winzip accepts command line parameters...which you could call from xp_cmdshell.

PKZIP/PKUNZIP is another program which can do the same thing. there once was a free verison of...

thanks Jeff...force of habit I guess.... I like to make code different from comments, so it's obvious what to copy/paste.

I changed it to syntax highlighting as best I could...certainly more...

hate to point out the obvious, but with only the tablename, sp_help lists the name of the index, and of course the column components of the indexes as well.

I had a...

Are you having trouble doing it? for me, it just a bunch of "Next" buttons in a row....the enterprise edition dummied itself down to the developer version, because the operating...

yeah this isn't all that easy...adn you can get bitten by the varchar 8000 length issue if the data you are combining gets much over 4000 chars...varchar(8000) + varchar(8000) ends...

sweet someone found something I wrote and it helped...i'm humbled

permissions due to a service pack:

http://support.microsoft.com/kb/328151

You need to have admin rights, and this switch must be called in order to restore debug rights:

Exec sp_sdidebug 'legacy_on'

HTH; i ran into the...

also search for the Split() function in the scripts...there are several, and some return a table with multiple columns (ELEMENT,ELEMENTID), some just return a single column, etc. the split a...

could it be a permissions issue? you might have SELECT permission in the master database, but NOT dbowner (so that you can CREATE VIEW) in the other database? what user...

to use the in function on a string, you'll need to grab one of the many SPLIT functions that are in the script contributions here.

otherwise, you really would want...

here's an example I keep around for casting from nvarchar to varbinary and then back to nvarchar:

the key is to use nvarchars... i beleive this fails if you try to...

I saved this snippet for SQL2000, so i would assume it would still be valid in 2005; hope this helps:

USE master

go

EXEC sp_grantlogin 'BUILTIN\Administrators'

go

EXEC sp_defaultdb 'BUILTIN\Administrators', 'master'

go

EXEC sp_defaultlanguage 'BUILTIN\Administrators', 'us_english'

go

EXEC sp_addsrvrolemember...

here's one of many citations on it from microsoft: i just searched for sql 2005 server multi core processors and grabbed the first link

http://www.microsoft.com/technet/prodtechnol/sql/2005/msde2sqlexpress.mspx

so to be clear, if you...

it's physical processors that are counted, not cores...so you could have a 4 processor all with quad cores, as i remember it, and it would work with no problem