Thanks and just to confirm, the SQL server has a build number of SP2 plus a query hot fix.

Is it possible the application of the SP2 didn't patch the SSIS...

It sounds like it...your error message cannot find a valid SQL id to become the db_owner.

In most cases unless a vendor app asks for it but the database owner is...

If that is the case why would I get this message:

Error:SSIS Error Code DTS_E_PRODUCTLEVELTOLOW. The product level is

insufficient for component "Data Conversion (cleared_amt)"(1422)

Error:SSIS Error Code DTS_E_PRODUCTLEVELTOLOW. The product level is

insufficient...

How about "I really apologize but AP cannot get checks to run and I don't know how to reset the table to get the process going again.."

I was at my...

Any resources you can recommend to do some additional research on the syntax diffs and the migration? I can only put tools on my own laptop but in return can't...

You apologize for the question being basic I hope you don't mind the answer basic as well!

Open SSIS, on the control flow select the Control Flow item 'Script Task'. ...

T tried to upload some of the tables and the queries remained in Access, but we had to bring them back to Access since performance was unbelievably slow and at...

Thanks guys I haven't had time to test but this makes sense. I build the SSIS package on my desktop and the flat file is located on my C...

No errors when run in Business Studio but if I run it in SQL job I think I don't have the correct settings as there is a myriad of tabs...

You create a package via the Business Intelligence Development Studio. Debug it..make sure all steps are green then Save As to SQL server msdb database.

In Studio Manager if you...

There is an option in the export/import to append data but if this is test, I feel it is much easier to do a backup of production, then do a...

Keith try this:

1. In the source server via Studio Management, highlight the table, right-click and choose Script Table As Create To New Query

2. Save this query as a .sql file

3....

Rob,

Try this script to find all columns of job_id within the msdb database. If this script doesn't work I have two more search scripts:

/* This command using the undocumented...

In SQL 2005 in msdb.dbo.sysjobs that field is no longer there.

It is replaced by the originating_server_id which is an INT datatype.

Haven't need to delve into this much but...

Again not sure if I follow...a 'shell' SELECT script is this

SELECT [column1]

,[column2]

,[column3]

,[column4]

...