It’s been so long after my last article. Looks like I been lazy for few years now 🙂
I assume lot of people using  SSIS package deployment utility after they support project deployment model. I always use the ispac for easier deployment though it doesn’t support environments variables in deployment. Today we deployed a project to our environment which contains new package and no modifications to the existing packages were made. New package worked fine but some of the old packages started failing, I checked internal versions of the package and couldn’t find any changes. Errors were happening in Script Task. Continue reading SSIS 2014 Exectuion Error while validating Script Component→
I was working on a SSIS package in SQL 2014 which was working there without any issues. Due to few factors we need to downgrade to work in SQL Server 2008 R2 for few months. I developed the packages in SQL 2008 BIDS and deployed. No changes done to any of the database objects as I thought I’m going to use the same in my package as well. Continue reading SSIS Error Code 0xC02092B4→
I was working in a package and I was requested to set the import task as transaction consistent. In SSIS you can do all sorts of ETL stuff so when you import data you need to make sure the import is in consistent state which means either all the data should gets loaded or it should be rolled back to the previous state. You can enable this option either in package level or container level or at task level. Based on your requirement you can set the transaction property so the final output is in consistent state.
Couple of weeks back I was working with a SSIS package development. My requirement is to check whether the file exists before I start importing the data. If it doesn’t exist then the package should update the db table. When I heard this requirement I thought I can make use of the “File System Task” in SSIS toolbox. When I start the work I came to know that you can’t get this piece of information from that task. It’s really weird for me as you can move\copy a file or folder using this task however checking the file existence is not possible with that task as shown below.
We can use SQL Server Integration Services to transfer the logins and jobs from SQL 2005 to another SQL 2005 or SQL 2008. This comes in handy when its difficult to script each of the jobs . Firstly we need to create an SSIS package.