| Author |
Topic |
|
mikebird
Aged Yak Warrior
529 Posts |
 Posted - 2010-03-03 : 08:12:29
|
| It's not at all clear how to get from a done & dusted, testing and working SSIS package and the deploy so users can make use of it.Can you make it work like executing a stored procedure with parameters? I like those.Reading the books and websites about this is horrifying!Can't I just simply implement this package? |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2010-03-03 : 10:02:36
|
This is not a backout.What is the meaning of "users can make use of it"?All my SSIS packages are running in a scheduled job.It is also possible to start such a job via T-SQL command but I don't know what you want.
No, you're never too old to Yak'n'Roll if you're too young to die. |
 |
|
|
mikebird
Aged Yak Warrior
529 Posts |
Posted - 2010-03-03 : 10:50:27
|
| We have a package to loop multiple nested files importing into a table. Works fine. But to use it at all, have to open BIDS and run it in debugging mode. No bugs any more. I know there is to not debug while running it.When I make an IS connection from SSMS, not much is shown in the tree, but there is MSDB - completely empty. How to I get the package(s) in there to run, external parameter to choose directory to pull files from, perhaps destination as well, if these change... no need to use BIDS; just run from SSMS, like a SP?Done the configuration setup. Added and set those for each package. What next? |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2010-03-03 : 10:53:58
|
quote:
Originally posted by mikebird
We have a package to loop multiple nested files importing into a table. Works fine. But to use it at all, have to open BIDS and run it in debugging mode. No bugs any more. I know there is to not debug while running it.When I make an IS connection from SSMS, not much is shown in the tree, but there is MSDB - completely empty. How to I get the package(s) in there to run, external parameter to choose directory to pull files from, perhaps destination as well, if these change... no need to use BIDS; just run from SSMS, like a SP?Done the configuration setup. Added and set those for each package. What next?
seehttp://www.mssqltips.com/tip.asp?tip=1428------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
|
mikebird
Aged Yak Warrior
529 Posts |
Posted - 2010-03-03 : 10:56:07
|
| Run from T-SQL.. you meanexec [packagename] (file_directory), (destDB_table) ?That's what I'm looking for.. or when the Job(?) appears in the SSMS tree |
|
|
|
mikebird
Aged Yak Warrior
529 Posts |
Posted - 2010-03-03 : 10:59:58
|
| Yes, I tried the Import Package command from SSMS, and at the prompt for package path!!! what's that?!?!?! I didn't put it anywhere! I played with it in BIDS! What do I put in that little window? |
|
|
|
mikebird
Aged Yak Warrior
529 Posts |
Posted - 2010-03-03 : 11:04:36
|
| This is what I get when clicking the ... button the specify the package path, after closing BIDS:TITLE: Import Package------------------------------An OLE DB error 0x80040E4D (Login failed for user 'GBSPIRE\birdmic'.) occurred while enumerating packages. A SQL statement was issued and failed.------------------------------ADDITIONAL INFORMATION:An OLE DB error 0x80040E4D (Login failed for user 'GBSPIRE\birdmic'.) occurred while enumerating packages. A SQL statement was issued and failed.------------------------------BUTTONS:OK------------------------------ |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2010-03-03 : 11:35:14
|
quote:
Originally posted by mikebird
Yes, I tried the Import Package command from SSMS, and at the prompt for package path!!! what's that?!?!?! I didn't put it anywhere! I played with it in BIDS! What do I put in that little window?
didnt you save it locally?------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
|
mikebird
Aged Yak Warrior
529 Posts |
Posted - 2010-03-04 : 16:43:16
|
| Yes. Locally. The question is: is that all we get? Save a package and run it by clicking the green play icon from in Visual Studio every day, from my C:\ drive, or Execute it by right-clicking the yellow background, or hitting F5?When the VS interface asks me "what is the package path" when I just saved the project in VS and I don't know where it is! I gave it a name days ago and why would I have to go C:\Program Files\Microsoft SQL Server\100\......... that's VS's job to know where it is!The names and details of my packages are in the the MSDB. I connect using Integration Services and al I see are Running Packages (none), Stored Packages (yeeaahhh!!). Don't want File System storage. Open MSDB, and nothing is there.I wanna move it on from VS, for a person in a different country and department to run this package with their own parameters. I thought that was the objective of a database. |
|
|
|
nelson_38
Starting Member
1 Post |
Posted - 2011-06-08 : 16:25:07
|
do u have 2 instance on the server.. Like Default and named instance.If so, Grant permission to the user for the 2 instance and try. |
|
|
|
|
SSIS Deployment