could it be the user was denied access to the table, but has execute permissions on a stored proc that actually does the insert of the data?

i'm sure you already read the help that is available for osql; as you identified, there is no way to remove the line dashes separator directly with osql ; you...

this is part of the query analyzer: QA automatically puts the column names and a lineof dashes  to separate the data from column names.

you will not get dashes if you...

how about this:

set nocount on

select @@version

select replace(replace(@@version,char(13),''),char(10),'')

results:

Microsoft SQL Server  2000 - 8.00.760 (Intel X86)  Dec 17 2002 14:22:05  Copyright (c) 1988-2003 Microsoft Corporation Personal Edition on Windows NT 5.0...

"cleanup" is such a broad directive; i think we could help better if you could identify specific subsections of the cleanup;

what does cleanup mean in your situation? normalization? standardizing address...

can you post the udfs here so we can see what they are trying to do?

in some cases, you might be able to replace them, but in other situations, you...

there are also a few contributions in the scripts section that do a decent job for the price(free).

search for "Compare" in the "Scripts" section;

in a nutshell, yes you can, but by disabling constraints, you can insert data that does not adhere to the constraint definitions:

create table test

(testid int identity not null primary...

Thanks Tim;

it's wierd, when i run the the statement in question i get an error stating that SECUSER (which is a table in the database i called the proc from)...

i don't know if this will help you;

i create my scripts in hierarchy order, so that items that depend on other items are created AFTER they are added to the...

aonther alternative: Narayana Vyas Kondreddi wrote a stored proc that you pass the table name and it creates all the INSERT INTO TABLENAME statements: note you cannot use this to...

does the new table have a lot of constraints on it? are the number of rows being moved in the millions?

could tempdb be expanding in size in 10mb increments...

that is not an error raised by SQL Server i think(the exclaimation point is the giveaway for me..no errors microsoft finds are worthy of exclaimation points

could it be that your procedures are doing SELECT * FROM SOMETABLE without a WHERE clause to limit your results? so you end up getting the whole table instead of...

i think the best encryption tools are the ones you own the source code for; as a result, i would lean towards using the tools available below before i would...