I'm new to SSIS and am in need of some expert help!
I've created an SSIS package that uploads a .txt file to a FTP site. I've then Stored the Package in SSMS Integration Services, and created a SQL Server Agent job to run the package on a schedule to upload the .txt file to the FTP. The package executes perfectly and the file is uploaded to the FTP as expected, however the .txt file is truncated to 5KB on every upload! I'm not sure if I'm missing a setting in SSMS or what, when executing the package in BIDS it loads correctly and doesn't truncate so I'm guessing it has to be something with SSMS Integration settings?
Any help in resolving this problem will be greatly appreciated!
Regards,
Ryan
Related
Hoping for some help with a package execution error I am receiving. I have a basic SSIS Package that has an FTP task to log into an FTP site and copy everything out to a network drive folder. The folder is hard coded in the LocalPath and added as an existing folder in the Connection Manager.
If I run the package in SSIS it runs without any issue.
I deployed the package to an SSISDB in the Integration Services Catalog in SSMS. If I select the package and simply execute it I get the following error.
It states the directory is not specified, but I am not seeing the short coming.
I tried researching the issue but am coming up short on a solution to have the package run.
I create simple ssis package to import data from Access mdb.
Using OLEDB source to connect the mdb file and OLEDB destination on SQL server.
I create sql agent job job to run the the package.
If I used file on local c drive then it's working ( able to import data).
If I used the file on network then it will not working (the error said not see the file on network)
Some people said need to use UNC path \server\xxx\xxxx
However on visual studio to create the package and dont see how to use UNC network path on OLEDB connection file.
Can someone can help me with this issue. Many thanks.
I have an SSIS package that simply exports a database field into a excel file. When I run it in BIDS OR SSMS it outputs perfectly however when I run it from an SQL Job it only creates an empty excel file.
If your SQL server agent get the package from Integration Service Catalog, make sure the deployed package has every task enabled, or you could enable the certain importing task and deploy again to the server. Sometimes the deployed package has disabled tasks which may not noticed by the one who deploy the package.
If you use file system, also make sure certain task has been enabled.
More important, make sure that you are using the UNC path for tasks getting access to that file.
I am new to SSIS package and don’t have enough knowledge of the same. Below are some of my requirements:
I have a C# web application which reads data from an excel file, and we just need to give the folder path and its reads all excel files data in that folder.
Then I am putting that data in sql database.
I want to associate this C# web application code with an SSIS Package.
Can anyone give me steps how to create an SSIS package and how to associate this package with the c# code?
Yes you can do by following steps.
1. Create SSIS package - Please do search how to create SSIS package.
2. Host web application with dynamic loading package there you can update all configuration parameters dynamicaly.
3. I hope folder you mentioned in the server, if not then it has to be
go through this - Programatically load SSIS package configurations
please let me know if you need further help
I am wondering if it is possible to:
1) Develop SSIS Package for Data Flow Task
I am aware of how to do this on a local or network SQLServer,
However is it possible to create a package that uploads to a "remote" sqlserver, ie one that is not on site or on the LAN.
any guidance would be great
Thanks
Since I don't see anyway the package could see the other server, I would suggest loading the data to one or more flat files and putting them on an FTP site. Then having the remote server run an SSIS package to pick up the file(s) and process it into their system. This is basically what we do when our clients need data from us.