Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
mikebird
Aged Yak Warrior
529 Posts |
 Posted - 2010-02-18 : 04:29:31
|
| When using the simple import tool from Excel / Flat File into SQL Server, and choosing to save the package automatically generated, this has in the past saved it in MSDB as a job I can then edit / improve / expand on.... Recently, the usual import process doesn't create the job at all. Is there a different option I need to set?. Always checking the 'save SSIS package' box, running it now, or not.... Does it save anywhere other that MSDB? It's not my database. Could it be a permissions problem? No warning to say it can't save it... |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
|
|
mikebird
Aged Yak Warrior
529 Posts |
Posted - 2010-03-01 : 05:24:29
|
| Problem was that I didn't have access to that with no SS service instance on my machine - just the interface software |
 |
|
|
|
|
|
Package Saving