Showing posts with label ssis. Show all posts
Showing posts with label ssis. Show all posts

Tuesday, March 20, 2012

Quoted Field and Escape Character Issue

I am attempting to import a flat file and have come accross and issue that I do not know how to fix in SSIS. The issue is that some of the text fields use quoted identifiers. This is not an issue in itself. The problem is they also use quotes as escape character if quotes are on the field.

So I see instances of "" because inside the quoted field is a quote. How do i specify an escape character?

Unfortuanately, the current Flat file parser does not know how to parse embedded qualifiers.

As a workaround, you should probably keep the qualifiers in the flat file source and process them downstream using either the script component or Derived Column.

Thanks.

Wednesday, March 7, 2012

Quick Question - Need some advice on troubleshooting SSIS Errors

Hi Everyone:

I have a SSIS Package which in brief moves data from one SQL data store to another. On my local machine, the package executes fines, and does what it is supposed to do, by moving data from Point A to Point B. I have both Point A(DB) and Point B(DB) on my local machine. But when I deploy this package over to ASSEMBLY which is basically another environment, I get weird intermittent errors. What should I do? Can someone give me some tips on how to do good error logging in SSIS? I am currently writing to Windows Event Log, and I seem to look at some errors that are coming thru. What else can I do on SSIS Package side, to improve error reporting and handling, so troubleshooting is faster and more effective. I just need some stable advice on how to setup my package to do error logging where troubleshooting issues in different environments is more effective. Also I need to know, what could be causing these issues? Thanks.

MA

Try turning on package logging. Set it to log to SQL Server. It will then be in the chosen databases' sysdtslog90 table.

Right click on the control flow background to get at package logging.|||

There are plenty of resources out there....

SSIS Logging

http://www.databasejournal.com/features/mssql/article.php/3562406

http://msdn2.microsoft.com/en-us/library/ms167456.aspx

http://www.microsoft.com/downloads/details.aspx?FamilyID=526e1fce-7ad5-4a54-b62c-13ffcd114a73&DisplayLang=en

Custom Logging:

http://blogs.conchango.com/jamiethomson/archive/2005/06/11/SSIS_3A00_-Custom-Logging-Using-Event-Handlers.aspx

|||

Do i have to specify this table in the configuration column when setting up the log provider to write to SQL Server tables? Where do i find sysdtslog90 table? Thanks.

|||

MA2005 wrote:

Do i have to specify this table in the configuration column when setting up the log provider to write to SQL Server tables? Where do i find sysdtslog90 table? Thanks.

When you set up logging, you have to chose a database/connection. In that database you'll find the sysdtslog90 table.|||

Here is the error I keep getting, which I am not getting in my Local Machine Environment. Hmmmm... any ideas?

Executing the query "exec dbo.uspSaveMain_CEAImport ?, ?, ? OUTPUT" failed with the following error: "Grantor does not have GRANT permission.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set

correctly, or connection not established correctly.

|||It looks like your user lacks some DB permission in the env where you are pointing to.