Skip to main content

Gotcha-yours When Working With XLSX In SSIS


I encountered many challenges during the last one and half weeks with my first commercially billable SSIS work. Following are few of the Gotcha-yours

-          The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine.
When                    -  Encountered  this error when importing data from “XLSX” to OLEDB component
Component            – “Excel Source Editor”
Fix                        -   Download and  install AccessDatabaseEngine.exe
                                     http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=23734

Note      
Without this driver the excel file is will not be read 100% , in other words the "Excel source Editor" component completes but does not scan through the entire file.

-          Index and length must refer to a location within the string.Parameter name: length (mscorlib)
When                    - Attempting to view the excel data from the work sheet
Component           - in the preview of “Excel Source Editor” component
Fix                        - Changing the name of the work sheet to not have a prefix with numeric

-          IF the package is to do with Excel you need to finalize if the “Run64bitRuntime” needs to be disabled
When                    - If the package is built on 64 bit this will be set by default to True, But excel does not seem to have the required drivers for 64 bit

Comments

Popular posts from this blog

High Watermarks For Incremental Models in dbt

The last few months it’s all been dbt. Dbt is a transform and load tool which is provided by fishtown analytics. For those that have created incremental models in dbt would have found the simplicity and easiness of how it drives the workload. Depending on the target datastore, the incremental model workload implementation changes. But all that said, the question is, should the incremental model use high-watermark as part of the implementation. How incremental models work behind the scenes is the best place to start this investigation. And when it’s not obvious, the next best place is to investigate the log after an test incremental model execution and find the implementation. Following are the internal steps followed for a datastore that does not support the merge statements. This was observed in the dbt log. - As the first step, It will copy all the data to a temp table generated from the incremental execution. - It will then delete all the data from the base table th

Create a dacpac To Compare Schema Differences

It's been some time since i added anything to the blog and a lot has happened in the last few months. I have run into many number of challenging stuff at Xero and spread my self to learn new things. As a start i want to share a situation where I used a dacpac to compare the differences of a database schema's. - This involves of creating the two dacpacs for the different databases - Comparing the two dacpacs and generating a report to know the exact differences - Generate a script that would have all the changes How to generate a dacbpac The easiest way to create a dacpac for a database is through management studio ( right click on the databae --> task --> Extract data-tier-application). This will work under most cases but will error out when the database has difffrent settings. ie. if CDC is enabled To work around this blocker, you need to use command line to send the extra parameters. Bellow is the command used to generate the dacpac. "%ProgramFiles

How To Execute A SQL Job Remotely

One of the clients needed its users to remotely execute a SQL job and as usual I picked this up hoping for a quick brownie point. Sure enough there was a catch and there was something to learn. Executing the job through SQLCMD was a no-brainer but getting it to execute on the remote machine was bit of challenge. On the coding Front 1    1.)     The bat file included the following code                 SQLCMD -S "[ServerName] " -E -Q "EXEC MSDB.dbo.sp_start_job @Job_Name = ' '[JobName]" 2    2.)     The Individual users were given minimum permissions  to execute the SQL job Ex. use msdb EXECUTE sp_addrolemember @rolename = 'SQLAgentOperatorRole', @membername = ' Domain\UserLogin ' At the client machine              This took a fair bit of time till our sysadmin got me an empty VM machine.  Thanks Michael G                   I’m just going to copy the exact instructions that I copied to OneNote and passed on