Tag Info

New answers tagged

4

You can create 3-4 different data flow tasks within your control flow (inside the Foreach loop container). Place a sql script before the DF containers. You can have the script actually do something or not. The idea is to create a conditional from this task that leads to the 3-4 data flow tasks. On the connector for each DF object, add a constraint that ...


0

I decided to experiment with creating the user with a random password, and everything worked. CREATE LOGIN [##MS_SSISServerCleanupJobLogin##] WITH PASSWORD=N'blahblahblah', DEFAULT_DATABASE=[master], DEFAULT_LANGUAGE=[us_english], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF GO USE SSISDB GO ALTER USER [##MS_SSISServerCleanupJobUser##] with LOGIN = ...


0

If you don't have the option of fixing the spreadsheet I would load the data into a SQL table and update it in SQL with the below code. Load test data CREATE TABLE FillTest (MyDate date, MyType char(3), MyAccount char(3), Id INT NOT NULL IDENTITY(1,1)) GO INSERT INTO FillTest VALUES ('1/1/2014','AAA','111'), (NULL, NULL, '112'), (NULL, ...


1

Two options come to mind. If you go with the local copy approach you can manually use the AutoFill feature to fill in the blank values. For an automated approach, the one approach I would think of in T-SQL is to use a cursor to loop through all the rows, capture the non-NULL Dates and Types into variables and when you encounter a NULL value, UPDATE the ...


0

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.


7

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. EDIT: For clarity on the three options presented by explicitly mentioning the SQLAgentOperatorRole as an option and by adding some explanation on the third solution. (1) If the user is allowed to manage the execution of all jobs, ...


0

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 ...


0

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.


0

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 ...


3

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 ...


0

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.


0

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.



Top 50 recent answers are included