Hi i followed Microsofts "Implementing Row-and-Cell-Level Security in Classified Databases Using SQL Server 2005"
this works fine when i insert delete data on a normal script (mangement studio)
my project runs in a SSIS package, different users. i cannot do a bulk insert using OLEDB data Destination i get the following error
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Conflicting locking hints are specified for table "dbo.tblUniqueLabelMarking". This may be caused by a conflicting hint specified for a view.".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Conflicting locking hints are specified for table "dbo.tblUniqueLabelMarking". This may be caused by a conflicting hint specified for a view.".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Conflicting locking hints are specified for table "dbo.tblUniqueLabel". This may be caused by a conflicting hint specified for a view.".
Error: 0xC0209029 at Data Flow Task, OLE DB Destination 1 [1741]: The "input "OLE DB Destination Input" (1754)" failed because error code 0xC020907B occurred, and the error row disposition on "input "OLE DB Destination Input" (1754)" specifies failure on error. An error occurred on the specified object of the specified component.
Hi Duane.
Access Mode = OpenRowset Using FastLoad
Fast Load Options = TABLOCK,CHECK_CONSTRAINTS
these are the default values in the OLE DB Destination. is this correct?
|||Yes, those are the default values.ajedi2k wrote:
Hi Duane.
Access Mode = OpenRowset Using FastLoad
Fast Load Options = TABLOCK,CHECK_CONSTRAINTS
these are the default values in the OLE DB Destination. is this correct?
What type of connection manager are you using in the OLE DB destination?
|||I'm using a OLE DB connection to an SQL server 2005 DB.
is this what you mean?
|||
my bad,
i was actually inserting to a view, and view had triggers.
must set FastLoadOptions = FIRE_TRIGGERS
works fine
No comments:
Post a Comment