Is creating a misconception about SharePoint tables?

Question

I have only been working with sharepoint for three months, but from the very beginning I was told that the content of the SharePoint content is not limited, since MS can change the scheme at any time. The recommended route is to use the object model, and in most cases I understand this.

Now I need to join some lists to present content grouped by specific fields. Instead, repeating each list, I would prefer to link our own db, which is on the same database server, to the WSS content database and just create a view for the tables. This representation should be in our database to make sure that we do not change ANYTHING in the database of the content content of WSS.

Am I on my way to the eternal damnation or not?

Answer 1

Yes you. Microsoft is very clear that any changes to SharePoint tables make you unacceptable.

It is not recommended that you modify the SharePoint database or its data because it puts the environment in an unsupported state.

Now linking to your own database that queries the SharePoint database is shaky. Personally, I would do one of two things:

• If this is a critical application, run it after MSFT support.
• If this is something else, just make sure your view does not block the database during the query.

, , - , .

Answer 2

SharePoint "" . , SharePoint, SharePoint.

SharePoint , , sharepoint .

- , SharePoint.

SharePoint SPQuery.

Answer 3

Check out SLAM, the SharePoint Communications Manager. This makes it easy to transfer SharePoint data to SQL, including complex joins (one to one, one to many, many to many). And it synchronizes data in real time.

http://slam.codeplex.com

Answer 4

Well, if the connections you need to make are pretty simple, defining a linked data source in SharePoint Designer might work for you