You can use the DTSRun Utility with xp_cmdshell in an SP.

-JG

Look into your Client Network Utility and see if you are using Name Pipes -vs- TCP/IP.

And Check your odbc configuration to ensure you have a valid ID hitting against SQL...

I beleive SQL Server manages it's own thread processing, even to a smaller level called fibers.

-JG

This is what I am doing:

I create s imple queyr in an outlook msg body.

Select * from <atable>

I send it to the Sql Account.

I go to QA and execute sp_processmail...

I agree with Antares, I would capture the queries through SQL Profiler and look for missing stats. In addition run a small (few minutes) trace through the Index tuning wizard....

You should be able to capture enough info to show you where the timeout is occuring, if the transaction process and it is not timeing out in on the SQL...

I downloaded the SQL Dev pack as a trial. I am in the justification mode.

-JG

Have you tried tracing the transaction through SQL Profiler?

-JG

I could be wrong... but I beleive the ignore dupe key is best used with T-SQL's Insert. Not BCP. I am not sure if it will work with Builk Insert.

-JG

I looked in the script library, but came up empty handed. Was there a scecific script you were refering to that show how to process incoming mail queries?

-JG

You will need to sign on as the user with the mail profile, and create the profile on the server.

-JG

Edited by - jgee on 04/17/2002 1:31:22 PM

I recommend using a seperate table for the import. Create an index made of all the columns on the table with "Ignore Dupes" checked then populate the rest of your...

There are several ways to eliminate dupes.

Is this a one time thing? Or do you continually have to scrub do to an import?

-JG

SQL-DMO would do the trick. See Script Method under Index on BOL.

-JG

One quick way is to use Enterprise Manager and selecting / right clicking on the table, choose Task and then Generate SQL Scripts.

There are options on what you want to...