We received yesterday the acceptance of the first SharePoint project I have being involved with the customer I provide services.<\/p>\n
It has been an important experience for me in all terms. I have a list of lessons learned in my mind that I cannot even write. But I will try to do a polite short list.<\/p>\n
This is my personal point of view so I’m sure I’m wrong in some of the things shown here, so take care. It just focus on what is new for me: SharePoint. So…<\/p>\n
Lesson 1, how is SharePoint behaviour.<\/p>\n
In a nutshell I would say that SharePoint is a black box where you add things and provides the necessary response to the end users.<\/p>\n
To keep the stability of the system you have to take care about all changes in its environment: a windows patch, a configuration change: everything that is linked directly or indirectly with the connections between the SQL server and the SharePoint server is something you have to attend as first priority.<\/p>\n
One of the things that this project has failed is the fact that our customer didn’t want to hire a service support for the SharePoint server. They have new servers and they decided that was better to have service at the end of the project. This has meant that several performance problems has been appearing again and again when the server has environmental factors affecting to it.<\/p>\n","protected":false},"excerpt":{"rendered":"