SharePoint, Document Library

For years, SharePoint 2007 is about to appear on the market, SharePoint 2003 seems to be something that is history (exaggerating ...). Many companies have adopted SharePoint during the past year. The good thing is that I've seen a lot of small companies for the purchase of SharePoint last year. SharePoint's popularity is growing day by day and is considered a standard portal product. Document libraries are collections of files you can share with team members in a network based on Windows SharePoint Services. Want to know more about Document Libraries? Read more about Document Libraries on this site:

Suppose that when a document is added to the document library, you need to store the name (identity) of the document and when that was added in the database. How can he do that? Why do that? You can capture all the consequences shot in the document library. When ever a document is added, updated, deleted, etc, can appropriate the event and add your own business or logical system basically capture information from the document and save it in the database. Why store the document data in the database? Well, there may be concluded. You may have to provide reports for senior management need to review the documents added to the library from time to time. You may need to track the history of the document or you may need to add a workflow to the document library. All this can be complemented by the Event Handler Toolkit ".

Before continuing, let me say the purpose of this writing. There are many excellent articles on the internet that shows how to capture events from the document library and not transformation, but still many people come to me and ask me the same question over and over again and the issue is related to the capture of information in the document and storage in SQL Server. Seeing the demand, I decided to write a short article that will show you how to capture information from the document library and store it in SQL Server. You can do many things