SSIS package creates a sql server replication snapshot trigger file but while the ssis package is still running, the file can't be opened. is it possible to stop DtsDebughost.exe locking the file?
The plan is to unlock the file and move to different folder.
Related
I am trying to import bulk text files (more than 100, 000) into a SQL database. I have created an SSIS package to do that. The package has a File System Task which is supposed to move the files imported to the database to another location (archive folder). This helps in case there is an error during importation so am able to identify where the job stopped.
When i execute the package in SSIS (Visual Studio), the files are being imported and moved.
When i however, execute the package in CMD, the package is only importing the files but not moving.
I have tried to run CMD as administrator but it has not worked as i thought that it was an issue with permissions.
I created an SSIS package which has 3 script tasks that checks if a different file exists for each and if the any of the script tasks finds the file, then it goes to a foreach loop which imports data to a sql server staging table, then copy and renames the file.
It works successfully within Visual Studio, however when I set up a sql agent job, the package only processes the last file and ignores the first two.
Any ideas why this may be occurring?
Probably either permissions of the SQL Agent, or invalid file paths on the SQL Server.
I am doing a SSIS dtsx file in which I access data in Dynamics CRM. This is the procedure:
* Someone copies files in a folder (.txt files from OCR, that's an external process).
* The SSIS grabs those files and copy them to another folder "Processed". Then the SSIS looks for data in those .txt and creates records for entities in Dynamics CRM.
* When some record can´t be created on CRM, it is an Error and the SSIS creates a temporal table in SQLServer with the error. Then the SSIS creates some .txt files which show all the errors, the number of the row and name of the original file.
I could run it from the Visual Studio, but I am not able to run it from a job. I've followed those steps: https://www.codeproject.com/Articles/14401/How-to-Schedule-and-Run-a-SSIS-package-DTS-Job-in , but still not running.
What may I do to handle this?
The dtsx in the job is in a SQL server and the files which I want to work with are in a CRM server.
Thanks very much for your help!
Finally ir worked!!
I followed the steps again and I could run the job successfully.
I have created a job in Talend which I want to schedule everyday through Windows Task Schedular on my dedicated machine. I have exported the job and gave the path of executable batch file to Task Scheduler. Now the issue is that when the job executes through the Task Scheduler it does not insert any data from source MySQL database tables (from a remote client machine) into destination MySQL database tables (at my local dedicated machine). Whereas, whenever I execute the same batch file just by clicking on it then it works perfectly fine.
Please help!
I have a temp directory on my website where users export data in .csv files.
The newer intranet apps delete the file after it's sent to the client but the legacy apps just leave the files in this directory.
I'd like to create a task to clean this directory nightly. There can be .csv files and directories with files in them.
Basically I want to run:
del *.* /s
rd /s
...every night at midnight.
Would love to do it with a SQL maintenance task but that only runs on the actual SQL server and doesn't work with mapped drives (unless I'm missing something).
How does one go about performing this task?
Can it be done through SQL server somehow?
You have the option of creating "Jobs" that run stored procedures or bits of code. These jobs can be scheduled to run daily, weekly, etc. Check out this thread: How can i create SQL Agent job in SQL Server 2008 standard?
Sounds like you may be using SQL Server Express Edition for which Microsoft removed the SQL Agent on 2008 and above. In cases like this you're best choice is using the Windows Scheduler to run your commands via a batch file.