Declare @retValue int

EXEC @retValue = msdb.dbo.sp_start_job @job_name = 'packagename'

If @retValue = 1

Raiserror ('Failed to start [packagename]', 16, 1, null)

I have had issues with a re-attach...

There is no guarantee on a re-attach so I would always use the bak file.

Thanks Lowell

If it's the inserts that are slowing it down, is the table heavily indexed?

lol..I'll go ahead and make a deposit to your account.

thanks man!

thanks for answering

so if I use a high precision/scale (like DECIMAL(37,12))

Will it then stop cutting off the numbers shown below?

The numbers I'm importing look like:

1997841.98000

752000.00000

3798077

Thanks guys.

Not sure if standard/enterprise will matter to Doubletake.

So, we have disparate versions....how do we fix that?

The idea about playing back traces on a dev box is a good one.

Thanks everyone..

Awesome thanks bro!

missing index dmv is what I was looking for..

No...I realize I could (and maybe should) start a trace on the table...and then optimize it using ETA. Unless I missing something in ETZ I could use.

But I thought I...

damn ....can't upload a txt file either....

im using the part of Lowells scriipt in this post starts with declare @sql varchar(max)

Sorry Lynn but I can't post code...something wierd @ work stops me from posting code...tried everything

but if you look in this post..it's the restore part of the statement that...

When I run the restore part -

I get an error

Msg 102, Level 15, State 1, Line 1

Incorrect syntax near 'MSPHXX_ARC'.

Msg 319, Level 15, State 1, Line 4

Incorrect syntax near the...