Document Library and SQL Server, SharePoint

Years ago, SharePoint 2007 is about to appear on the market, SharePoint 2003 seems to be something that is history now (Exaggerating ...). Many companies have adopted SharePoint for the past one year. The good thing is that I've seen a lot of small businesses acquiring SharePoint during the past year. SharePoint's popularity is growing day by day and is considered a top-level product portal.

Document libraries are collections of files you can share with team members on a network based on Windows SharePoint Services. Want to know more about the document libraries? Read more about the libraries of documents on this site:

http://office.microsoft.com/en-au/assistance/ha011412871033.aspx

This link will show you how to create and use a document library. You can extend the functionality of these libraries of documents using the "Event Handler Toolkit" that can be downloaded from the Microsoft site.

http://www.microsoft.com/downloads/details.aspx?familyid=4B2C2F1B-D74A-482A-903A-45BB44C5DEC4&displaylang=en

Suppose, whenever a document is added in the document library, you want to collect the name of the document and the time it was added, in the database. How can you do that? Why would you do that? You can capture events evoked in the document library. When ever a document is added, updated, deleted, etc, you can capture the event and add your own business logic or simply capture document data and store it in the database. Why would you store document information in the database? Well, there can be many reasons. You may want to create reports for the senior management who may want to look at the documents added to the library from time to time. You may want to track the document history or you may want to add a workflow to your document library. All this can be done by using the “Event Handler Toolkit”.

Before, they proceed, let me tell you the purpose of writing this. There's plenty of excellent articles on the net that show you how to capture document library events and do processing but still plenty of people come to me and ask me the same query again and again and the query is related to the capturing of document information and storing it in SQL Server. Seeing the demand, I decided to write a small news story that will show you how you can capture the document information in the library and store it in SQL Server. You can do so plenty of things, for example:

1. When a document is added, you can copy or move it to another document library.
2. You can delete a document.
3. You can capture document information and store it in SQL Server.
4. You can update document information by updating the properties associated with the document.
5. You can add workflow mechanism to your document library. For example, when a document is added to the document library, you send an email to the approver and ask him to approve the document. Document, after getting approval from approver 1, goes to approver 2 and so on.

These are only some of the important things that you can do with Document Library EventHandler. I wish I could show you all of the above in my article but unfortunately that is not possible due to shortage of time but I promise I will try my best to update this tutorial from time to time and add more content to it. In this article, we will see how you can capture document information when a document is inserted in the library and store this information in a DB.