Post reply

SSIS Package Error

  • January 20, 2013 at 1:38 pm

    #268843

    Hello Everyone

    I know this is a SSIS Package issue. But I cannot find a category for "2008 SSIS Packages"

    I have a step in a package that calls a sproc. No big issue, the package runs fine until this point. The issue is there must be a "DBCC CheckIdent" statement in the sproc.

    This is the error that I am receiving during the Development processing of the package. I am executing the package from within BIDS. I have not tried executing the package from the SQL Job as of yet.

    Error:

    [Execute SQL Task] Error: Executing the query "EXEC dbo.INS_Labs_from_ETL_to_Prod"

    failed with the following error: "User 'guest'

    does not have permission to run DBCC CHECKIDENT for object

    '#Labs

    There is Not a "Guest" account on this box and not a guest account in SQL. One, how do I fix this so that the package will execute and succeed.

    This is the line of code in the sproc:

    DBCC CHECKIDENT ('#Labs', RESEED , @NextRowNumber) WITH NO_INFOMSGS

    Or does anyone have a suggestion or a better way of performing this process to reset the Seed Identity of the table?

    Thank you in advance for all your help, suggestions or comments.

    Andrew SQLDBA

  • January 20, 2013 at 3:21 pm

    #1579055

    I'm curious what the business case is for reseeding the identity value? What problem is this solving?

  • January 20, 2013 at 4:24 pm

    #1579058

    HI Lynn and all others

    This is a heading banging against the wall type of thing that I have been trying to get the upper management to understand for a little while now, right after I first discovered it. They are using the same schema in not only SQL Server, but in DB2.

    So when I create a table variable to load data, thru my ETL process. I use 8 to 10 different tables to route the data accordingly. I fill a RowID very easily and simple in SQL Server. But I have to turn right around on the next step, query a "Keys" table to select the rowcount, which someone named "Count"(a nice reserved work in SQL Server) , select the count for the table where I am loading said data, and then reseed the temp table that I am using.

    Makes me want to beat the crap out some of the old time thinkers.

    I did figure out that I can use a hard table, since only the ETL process will be touching and only once a day, to get around this issue. SSIS will use the service account to perform the reseed, and it does this with no errors.

    Notice my little guy at the computer pulling his hair out, that is exactly the way I feel some of the time working with a poor performing schema of DB2 within SQL Server. I am thankful this is for only one little database and one fairly simple data load ETL. All the other, I have designed using SQL Server process, standards and coding methods.

    Thanks

    Andrew SQLDBA

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply