Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Enlisting WSS object model/API calls in a transaction with LOB data

  Asked By: Ramsey    Date: Aug 05    Category: Sharepoint    Views: 798

Has anyone run into the need to enlist a WSS object model/API call in a
transaction, for example, with other database transactions?

One of the simplest examples is uploading a file or changing the metadata
about a file in a document library in the same transaction where a
line-of-business database also needs to be updated.

...and you want both the document library update and LOB data update to
occur ...or neither, in the case where one of the updates doesn't succeed.

How common are these types of scenarios?

Share: 

 

4 Answers Found

 
Answer #1    Answered By: Alisha Itagi     Answered On: Aug 05

The question comes up a lot, but there's no support in the product for it and
most of the strategies that can be used to implement it would break support on
WSS since it would require direct database  access.

 
Answer #2    Answered By: Octavio Dotson     Answered On: Aug 05

most of the strategies that can be used to implement it would break
support on WSS since it would require direct database  access ;)

Most but not all Byran,

We've been been able to implement full MS DTC transactional support for a
workflow server API (where we don't have direct access to the database).
...the approach is standard .NET and the design can be replicated for WSS.

 
Answer #3    Answered By: Judy Pittman     Answered On: Aug 05

My understanding was that approach was also a problem, but it's been a while
since I looked into this.

 
Answer #4    Answered By: Tricia Mullins     Answered On: Aug 05

What about making a call  to the SharePoint web service API from a .Net stored
procedure in SQL Server 2005? Does that work?

 




Tagged: