New answers tagged ssis
The answer to this is yes, we had to convert the package to SQL 2012 format. For now we keep our packages in SQL 2008 format in source control, and at deploy time migrate the page to 2012 format. Once done, the performance is on par.
It is possible to set up a method to grant rights to run a job that a user does not have enough authority to run on its own. Erland Sommarskog has written a lot on how to grant permissions through stored procedures using counter-signatures. He has a solution at: http://www.sommarskog.se/grantperm.html#countersignatures The key point is: "To be able to ...
I could not resolve this issue and changed my approach to utilize a SQL Job instead of running the package directly from a powershell script. Summary of solution: SQL Job with one Job Step The Job Step executes the SSIS package To run a SQL Job with a custom you must also create: an instance-level Credential a Proxy Account which should be mapped to ...
figured out the issue. didn't know the ssisdb procedures already were doing 'execute as' and didn't know you needed to use an AD account for impersonation to work.
We had to create a special tool to perform this function. Specifically, we needed to obfuscate sensitive fields, and since the database is so huge, if we are testing only part of the system, we could extract and load only the slice of the database (configuration data and transactions) that is relevant for the particular software being tested. The ...
Since you mentioned you want to copy table data only I guess SSIS would be perfect. I have been using it and it works just fine for me. It also depends on level of competency you hold with SSIS. You can go for backup restore but it would also restore tables whoes data you dont want to change. If you want complete refresh then of course no better option than ...
2 options : Preferred one : Backup with compression and restore it on Dev server. You can automate it using sql agent or PowerShell. Use BCP out and Bulk Insert in. I have tried and tested it if you want some tables only. Its very fast as I have implemented it in my environment as it suits my specific needs. You can even schedule it using sql agent job.
Thanks for your advice. I found the issue. It was due to different date formats being used in Oracle data. The year part was yyyy for some dates, while just yy for other dates. So for eg: when a user enters '98 as the year, the system saved it as 0098 rather than 1998. Hence, the data was not processed at oledb source itself in bids.
You need to use derived column transformation and with help of expressions perform required conversion operation on original columns. To replace null with default value use REPLACENULL(expression 1,expression 2) in derived column transformation. REPLACENULL returns the value of second expression parameter if the value of first expression parameter is ...
First, make sure you have a user in msdb associated with their login. USE msdb; GO CREATE USER username FROM LOGIN loginname; Next, deny execute on sp_help_job and sp_start_job for that user. USE msdb; GO DENY EXECUTE ON dbo.sp_help_job TO [username]; DENY EXECUTE ON dbo.sp_start_job TO [username]; Next, create two wrapper stored procedures that ...
If header names are same across all the delimited files, then you can use Script Task/Script component inside Foreach Loop Container. You can put the logic ( by hard-coding header names) - First check file's delimited type (Comma/Tab etc) and then extract data for only those columns you are interested from that flat file.
Top 50 recent answers are included