When any kind of slowdown occurs within a SharePoint system, the immediate solution is to go for addition of more web servers in order to handle the load in a better fashion. However, these front-end servers are dependent upon the same back-end database server. Incidentally, it is the back end where most of the issues crop up. This is because it depends upon SQL as a file as well as a database system. The processing demands of SP brings to light the disk I/O as the most most common bottleneck. Let us discuss the steps that need to be taken for avoiding or mitigating the logjams that can hinder SQL Server throughput.
It is advisable to get the binary large objects such as the file attachments, out from the database. SQL Server as well as SharePoint render support to Microsoft’s RBS ( Remote BLOB Storage) technology. This conveniently allows putting all the Excel, Word or other documents back within the NTFS file system wherein they actually belong.
NTFS has the capability of writing and reading files rapidly. On the other hand, SQL Server needs to manage them along its database pages of 8KB, which can consume a great amount of disk space as well as server resources. To do away with this, files are kept by RBS in NTFS and pointers are also provided. This implies that the file attachments can be written to completely separate disks that the one which contains the chief database. This helps in maintaining speed by reducing disk contention.
Regular Maintenance and Premium Storage
One of the most significant performance management investments with respect to SharePoint is buying fast storage. Initially, it is good for organizations to focus on gaining momentum in planning the purchases since this constitutes one of the most costly aspects of storage. Rapid storage area networks coupled with robust drive caches are capable of rendering high quality storage performance, which is a great need of SharePoint. It is advisable to make sure that adequate amount of storage capacity is available for every data developed with respect to a SP installation.
Regular maintenance is extremely important for ensuring the efficiency of ongoing SQL server. The SP collaboration platform is able to generate considerable amount of data, especially in case of heavily used document stores wherein versioning occurs in order to track changes within documents. Moreover, manifold versions are maintained for reference purpose. Appropriate database maintenance, incorporating reorganizing or rebuilding indexes along with updating of statistics, allows SQL Server to remain clean-cut and suitable for quality performance. Moreover, database files can be defragmented as the fragmentation level starts to go beyond 7% or 8%.
Breaking it up
Owing to the inherent scalability of the web, SharePoint is able to scale without any major issues. SQL server is unable to do it in a similarly convenient manner. Because of this, managers of a number of big SharePoint environments develop manifold server farms, each having a dedicated back-end system. For instance, a company can possess a set of SharePoint servers as well as a related database for the document library across the company, for special projects, for users' blogs and the like. This yields better results than putting everything into the same SQL Server database.
SharePoint administrators can also consider acquiring certain extra tools in addition to visiting Microsoft’s TechNet website, which presents solutions to particular performance problems and best practices to ensure speedy crawling of SharePoint environments.
Defined Performance Metrics
It is also a significant aspect to develop some measurable and reasonable performance expectations for SharePoint development. The basic formula is to try and base these upon the end-user experience. Simply speaking, acceptable performance can be defined by the maximum time a user has to wait during checking of a document accomplishing a task or accessing a blog. You can then break down these metrics into a number of prospective back-end performance metrics. This is a great means to assess the performance quality.
When user-experience metrics get defined, it is required to measure them regularly in order to identify the trends. In this way, it will be convenient to detect whenever a SharePoint system fails to live up to the organization’s expectations.
We provide SharePoint bespoke development services. If you would like to talk to one of our certified SharePoint programmers, please get in touch with us at Mindfire Solutions.
Whenever it comes to the loading of SP Data in the server integration of SQL, the very first thing that developers of integration package services are bothered about is the best- possible ways in which the data can put in as well as brought out from the SharePoint list. The source of the list and the destination sample of the SharePoint offers an optimized solution with a user friendly interface. The sample also comes with an API for an efficient accomplishment of the tasks apart from the Integration Services.
Ways of Working with SP Data
Following are some of the prominent ways in which the SharePoint data can be extracted or loaded:
- Making use of the SharePoint APIs to add or remove items individually
- Generating as well as submitting the XML by means of the use of the SharePoint Batch API
- Using the Lists Web service that makes use of the same XML as the Batch API
The web services come up as great ways of transferring information to and from SharePoint without altering the platform server itself.
SharePoint Source List and Destination: Features
A discussion on the prominent features of the list source as well as destination of SharePoint is essential in this regard. Now, these actually make use of the public web services of the platform. Here is a list of features that improve their level of performance and functionality:
- The required fields are only returned from the web application development platform
- The somewhat large lists are divided in batches with a batch size that can be configured
- The information of column type is utilized for the purpose of mapping to Integration services data types
- Addition of CAML queries to the query is facilitated to separate the rows that need to be returned
- Simple updating as well as deleting of operations from the Integration Services package
- Integration services expressions can be used to set the essential custom properties of the source and destination
- Supports SQL Server as well as x64 and x86 processors
Process of Using the Destination and Source
Few steps need to be taken prior to using these parts of this SharePoint development platform. The foremost thing to be done is to download the right installer package from the codeplex site. Once downloaded, the installer needs to be run. It has to be kept in mind in this regard that Complete Install needs to be selected, as this allows the installer deploy connectors for each of the version of SSIS on the targeted machine. This is followed by the final step that involves addition of the source and destination to the Toolbox.
Extracting the Information from SharePoint with List Source
The extraction is usually done through the following steps:
- Addition of the SP connections
- Addition of components to the SSIS data flow
- Setting the properties of the SharePoint list source'
- Writing data to SP by means of the SP list destination
With regards to the extraction and loading of SP information, few more factors need to be considered apart from the above. For instance, if you are looking up for a value in a SP list, the Lookup transformation in the data flow can be used to load the lookup table. Again, if you are replacing values in the data with the values found in the loop, loading the altered data back to SP can be done by including the ID from the lookup column.
There is absolutely no doubt about the point that the SP list source as well as destination sample makes getting data into and out of a SharePoint list much hassle- free. What's more, the sample also facilitates a utility library that makes working with SP lists out of integration services simpler.
We provide SharePoint bespoke development services. If you would like to talk to one of our certified SharePoint programmers, please get in touch with us at Mindfire Solutions.
Owing to the user-friendly aspect, a large number of organizations are increasingly realizing the need to migrate from WordPress to Sharepoint. These companies prefer to host the content within distinct libraries or lists utilizing a metadata structure. Moreover, they want to make use of a powerful search engine that would empower users to conveniently arrive at the data they are searching for.
The WordPress to Sharepoint migration projects are very intricate, but yield effective results once the problem areas are tackled before going for the actual process. In fact, moving to SP is much more than copying the content to any SP site from the source destination of the data.
Content Analysis
A good understanding of the content as well as its usage is important. This analysis phase involves the verification of the content volume and usage along with the permission setup. It is significant to comprehend the manner of data usage and the procedure that is involved in creation and modification of content. Knowledge of this is a great help while setting out libraries and sites. Here data is organized into categories depending upon what can be moved rapidly, what is possible to be archived and what might create problems. Hence, when you are migrating from WordPress to SharePoint, this phase is crucial for planning the project as well as its successful completion.
Cleanup and Preparation
Migrating offers a great opportunity to clean archive content and directories which have become obsolete. One of the key aspects to ensure a successful migration is to solely move those items which require moving. This leads to a short migration life cycle and also enhances the content's usability through retention of that data which is actually relevant in today's business perspective.
Taking care of site configuration
Once you arrive at a specific amount of data that is ready for migration, the generic configuration of the site libraries as well as the site itself can be defined. You can also go for search engine configuration, defining metadata and also establishment of permission groups.
One issue that you might face is defining the metadata. The content that needs migration may be present within an environment wherein there is no metadata, for instance a file server where the content resides in a folder structure This folder structure should not be used for classification of data since content in SP always revolves around metadata. In such case, a robust metadata structure should be built within the destination library which assists the users to locate the content. Following this, content types, lists or libraries need to be created with specific focus on the source location's security setup. It is best to split the content into a number of libraries or ascertain fresh permissions setup for business owners.
Testing
After configuration of the destination sites, you can perform certain test migrations making use of a limited set of documents to ensure that there is proper configuration of the current site structure. Involvement of key users is advisable for carrying out certain tests through addition or modification of documents.
Migration of data
This is the phase wherein the real migration from WordPress to SharePoint takes place. There are a number of migration tools which enables successful migration.
Testing during migration
Owing to a number of organizations or technical concerns, migration jobs are usually carried out in batches. So there is good opportunity to perform certain testing procedures after the completion of each batch. This makes it convenient to quickly correct any faulty migration procedures, thereby ensuring an appropriate working ambiance in the end.
Once all these steps are meticulously followed, it ensures successful migration from WordPress to SharePoint. For more effective results, you can always involve the end users. Define certain key users, let them comprehend SharePoint and then gather their feedback. This will help you collect useful information and also enhance the user adoption procedure. This would help you leverage the benefits of SharePoint portal development.
We provide SharePoint development services. If you would like to talk to one of our certified SharePoint developers, please get in touch with us at Mindfire Solutions.
The popular business application, SharePoint, is now widely preferred by most software companies. With the newest versions coming up, this web application platform is used for a number of purposes, out of which the sharing of electronic documents and images of the scanned paper documents are the most prominent ones. SharePoint enables developers to create websites, which further allow an easy uploading as well as managing of documents. Even the communities can be formed around particular functions, necessitating access to the documents. These documents then become ready for searching, collaboration, management, updating or archiving.
The Need for Integration
While SharePoint with its multiple functionalities is of immense use, it cannot be denied at the same time that it is not so useful when it comes to the business intelligence system. It is here that the integration of SharePoint with Crystal Reports becomes necessary. The integration largely helps in making the information accessible as well as ready to analyze from the organization. Once the integration is done, the data can be drilled into different sets, which makes the process of categorizing them easier. The integration supports accomplishment of the following tasks:
- Analyzing data in thorough details
- Identify the relationship between costs as well as revenues of your organization
- Identify processes and products that are adding value as well as reducing the margins.
Now, there are few things to be considered to ensure that the integration of SharePoint and CR goes off well while also paving the way for the required benefits.
Points to Consider for Successful Integration
To begin with, a CR scheduler should be incorporated, which allows scheduling of reports that need to be sent at specific date and time to the particular business users in the desired format. The incorporation of the Crystal Reports scheduler offers the members of the organization with the required information without a wastage of time and efforts and they can, therefore, engage in quick decision making. The reports created by the business users can also be stored centrally with the help of SharePoint and accordingly, accessed by the staff members who are in need of the same. Crystal Reports pave the way for scheduling reports on the use of SharePoint to get an idea about how the web application platform is influencing the work of the staffs.
Yet another important factor that has to be considered in this regard is that of using the SharePoint system in the automation of business process. The newly integrated report scheduler, if used, on an event-driven basis, enables a rather process automation. Consequently, modification to files or databases lead to a chain of actions, saving the hard work that had to put into the task otherwise by an employee.
The events include receiving orders from customers and triggering an automatic sending of the packing slip to the warehouse, reducing of the inventory levels, ordering the new products along with materials to fill up for the lack of stock, scheduling delivery of the given order and also billing the customer. Earlier, these actions had to be not only performed by the individuals but also necessitated the inputs from several professionals belonging to the various departments of the organization. Now, the automation is done electronically, saving the transactions that seem to be lagging behind, cost of staffing and the obvious chances of human errors.
Considering the importance of the integration of SharePoint with Crystal Report, companies are now going for Crystal Reports Distribution or what is also known as CRD. CRD can actually work wonders in reducing costs while at the same time, increase the margins and efficiencies. Scheduling and automation of information across any organization is easier than ever before. Custom sharepoint development teams can help you build projects within allocated budgets and time schedules.
We provide SharePoint application development services. If you would like to talk to one of our certified SharePoint developers, please get in touch with us at Mindfire Solutions.
Lotus Notes, a prominent application development platform, became popular in the 90s. Most of these platforms helped in catering to the varying demands of the departments. The rapid development of the platforms led to the production of a variety of applications that were implemented without proper governance. Eventually, this led to the necessity of migrating from Lotus to SharePoint.
Now, the switching from Lotus Notes to SharePoint can be carried out using various paths. The precise ways and the process revolving round the migration needs to be considered to allow this to be successful. Here is a list of few ways of migration from Lotus applications to Microsoft SharePoint.
Migration of Standard Lists: This is the first point that needs to be taken into account. SharePoint, at the time when it was designed, came with several templates designed to execute precisely the same job as the numerous Lotus Notes’ mostly used standard application templates. The templates include task lists, calendars, discussion databases, contact lists and more. The basic functionality is same in spite of slight differences between the interfaces.
Migration of Custom Lists: Very much like the standard lists, the most essential thing to be considered while migrating from custom applications to custom lists is that of mapping all the database fields of the Notes to the suitable custom list columns.
Migration of Document Libraries: When it comes to Libraries, there are many things common between Lotus Notes and SharePoint with slight variations. The documents are actually binary files with several associated data properties. Considering this, the binary files attachments should be extracted and put in the library. This needs to be done during the Notes database migration.
Conversion of Microsoft Word: There is no denying the point that Microsoft Office, which is the dominant standard for creation of documents, integrates closely and effectively with the SharePoint libraries apart from being easy to handle. Now, the integration of Lotus Notes and SharePoint enables building of powerful applications. Additionally, users have the option of opening, editing and saving documents from the libraries without any hassles whatsoever.
Conversion of PDF: For businesses that have large amounts of Notes Databases incorporated with rich ext documents, PDF is the most suited platform for switching. Searching of PDFs in SharePoint requires installation of a free add-on from Adobe. PDF conversion leads to a satisfactory user experience, which may not, however, be as good as the one offered by Microsoft and SharePoint integration.
Conversion of InfoPath: InfoPath is considered an essential tool for switching for certain reasons. The applications might include complicated data structures, disabling them from getting stored in a list. The applications, on the other hand, encompass complex form designs along with ranges of difficult features.
Use of Document Sets: Document Sets come up as an essential way of storing several related files in a single and logical document group. This is like storing the entire thing in a single folder. In a document set, one can version, approve as well as secure the files while also presenting them in a usable and versatile interface.
Web Part Pages Migration: Web Part Pages Migration is the best option for exercising extra control over the manner in which the various elements in the web page are placed.
Migration of Publishing Pages: The reason behind this is precisely the same as Web Part Pages Migration. The only difference is that publishing pages require separate visual layout and styling from the authors of the content.
Migration of Wiki Pages: Creating a new page in SharePoint from the create menu leads to the wiki page. Now, wiki is the most popular page type when it comes to migrating Notes content. It is easily doable with proper migration tools.
Keeping these issues and their solutions in mind would assist you in getting a successful sharepoint site migration done from Lotus Notes to SharePoint.
We provide SharePoint porting services. If you would like to talk to one of our certified SharePoint developers, please get in touch with us at Mindfire Solutions.
Every time a software company brings out a new technology or product in the market, the focus is directed towards the endeavor of catering to the demands of users/customers concerning a specific functionality. Owing to such a need, companies often take route to creating an all – inclusive administrative solutions with the aim of selling a complete package. However, it must be noted that all documents and data created within the system often holds onto an importance, which reaches beyond commercial lifetime of a particular application of creation.
The importance of documents and data often surpasses the actual scope of parent or main application. For instance, documents that have been created in a proprietary system of document management might require an access from a corporate intranet or data present within system of custom relationship management might serve as an input to process of business documents creation.
Now, introduction of SharePoint 2013 has brought into fore the prospect of an effortless integration between a particular application and other external systems that has been implemented within technologies that are not of Microsoft. Well, in such a scenario, the RESTfull web service of SharePoint API increases communication with web application of Java. The chrome control of SharePoint enables the web application of Java to feature a similar kind of styling to that of hosted website.
The Layer of Communication with SharePoint
The web application of Java communicates to a car list in the hosted web, which is referred to as the Interopl and the data list is named as the Cars. The list features columns referring to the model, bran, and price. This particular application is named the Cars App and here is a quick look at the dependencies of the same within Java implementation.
- json-lib 2.4 – helper classes influencing Json objects
- resteasy-jaxrs 2.2.1.GA – RESTEasy enabled an easy access of the RESTfull SharePoint API
- commons-httpclient 3.1- dependent on RESTEasy
- httpclient 4.1.1 - dependent on RESTEasy
- spring-web 2.5.6
- spring-core 2.5.6
- spring-webmvc 2.5.6
- commons-logging 1.1.1
The Car service has been defined in order to write and read into Cars list featuring declaration file CarService.java. The implementation of Cars service features a member variable, which define parameters of authentication along with web service URIs endpoints pertaining to SharePoint and Cars list field names.
The particular service also incorporates a number of helper methods. The callRestEasyService helper methods read the data by conducting a HTTP Get as against the RESTfull API of SharePoint. The URI that is given in the req parameter defines just what is being recovered and retrieved. It strictly follows the protocol syntax of OData. In this particular scenario, it would refer to the items of the Car list.
To go for object creation in SharePoint through the RESTfull API, which refers to the Cars list items, it is required to provide a Form Digest, which can easily accessible via a POST To the hosted web endpoint “/_api/contextinfo”. The addRestEasyRetrieveDigest helper conducts the posts and goes through Form Digest. The actual definition of URI is given in the urlDigest of the variable.
The addRestEasyPost helper enables object creation in SharePoint through POSTs as mentioned in the protocol of OData. This particular method helps adding cars to the particular list. The parameter req features the URI of object creation, which refers to the Cars list here. Another detail that is often regarded while creating objects is the need of stating the type. In the particular list, the items refer to the SP.Data.CarsListItem type, which follows the convention SP.Data.<ListName>ListItem.
The parseJsonDigestValue helper method integrates the JSON response from the “/_api/contextinfo” endpoint recovering the form digest.
The parseJson helper translates the response of the JSON to the payload class of Cars retrieving the list.The Cars service explains the method getCars to read the items; whereas, the technique insertCar is used to write the items.
Custom SharePoint development teams can help you build projects within allocated budgets and time schedules.
We provide Java and SharePoint Integration services. If you would like to talk to one of our expert SharePoint developers, please get in touch with us at Mindfire Solutions.
DotNetNuke Corporation, a premier provider of adaptive web software which keeps the online presence of a business effective and relevant, came up with the availability of an improved SharePoint integration in the year 2012. This new SharePoint Connector is capable of rendering support to SharePoint 2007 as well as the 2010 version. It offers seamless integration between outstanding document management and web content management solution of DotNetNuke. Here we bring to you certain best practices which you must consider for proper integration.
1. Document Management: SharePoint is the finest document management system that is applicable for all businesses irrespective of the size. Utilizing this system, which is built within the cloud in order to make room for maximum accessibility and storage, group members are able to collaborate and share an apparently unlimited quantity of data and documents. It effectively integrates with Outlook and makes use of social tools for amplifying the organized, collaborative, atmosphere. It also facilitates transformation of raw data into interactive, beautiful reports by team members.
2. Integration with SharePoint: Automatic integration of DotNetNuke is possible, which implies that if the system is operated, no additional work is needed. But, when it comes to DNN Community, it can also integrate quite comfortably through custom modules. The goal is to develop a system which enables SharePoint to go for effective communication from behind firewalls with the public-facing website. This indicates that you will be capable of pushing documents towards a portal efficiently as well as safely on your DNN website. Filter rules can also be designed in order to find out where individual documents are going.
3. The DNN Enterprise: For those utilizing SharePoint as the document management system, and wishing to integrate the same into their website, the Nuke Enterprise edition is a good choice. With the help of this edition, custom integration is possible at a highly affordable cost. Through the connector, firewall issues can be bypassed and the content can be kept fresh, while publishing directly from the Document Library. Every document that is published is offered protection by the DNN role-oriented security network.
4. Avoidance of Firewall: Many companies make use of SharePoint as the document library and DNN as the public-facing website. In most cases this implies that the SharePoint server resides within the trusted zone while the DNN is made available to the public. All communications that take place between the two servers begin from the SharePoint server. This feature can be used without making any kind of modifications to the security policy.
5. Leveraging filtering views: The built-in views provided by document management system for filtering facilitate the use of the Create View UI. The views that have already been created can be used without the requirement for maintenance of two distinct filter sets. More time can be spent for development of core features as the time spent on development of filtering and associated UI features is reduced to a great extent.
6. Extended web application: When there is already a SharePoint web application making use of Active Directory for authentication, the same can be extended to support users from DotNetNuke. For this a DNS or hosts file entry needs to be created for the upcoming SharePoint site.
7. Modification of web.config files: A number of changes need to be considered within the web.config file in the SharePoint application. Before making any kind of modifications, it is advisable to create a backup.
8. Taking care of file size: With respect to the file size, DotNetNuke possesses an option beneath the host settings which limits the file size on the website. The files are compared against that number by the Connector. Files bigger than the stipulated limits of the website are not published.
9. Deletion from the document management system: In case “propagate deletions” is selected, the file that is deleted from the document management system also gets deleted from DNN. However, if the deleted file possesses references from a module, it will reveal broken links.
10. Handling permissions: Remember that permissions from a SharePoint to a DNN site are managed by DNN’s security model. It is not possible to manage permissions across SharePoint and DNN. This in because, in a number of cases, users and roles are different when it comes to the intranet and the public website.
Seamless integration, when effectively accomplished, empowers organizations to securely and effectively publish documents directly from SharePoint into their respective exterior-facing websites. Custom SharePoint development teams can help you build projects within allocated budgets and time schedules.
We provide SharePoint application development services. If you would like to talk to one of our expert SharePoint developers, please get in touch with us at Mindfire Solutions.
The dynamics which existed between hospitals, physicians, patients, laboratories and other hospitalists is fast undergoing a lot of changes. Blame it on the metamorphosis of the healthcare ecosystem. It is now widely accepted that Physicians need to be connected to better insights, decision making tools, patients and other required stakeholders to be able to execute their job better. This is where active use of info systems has made a huge difference. But the result has been an explosion of digital content which needs to be handled in a secure manner given that it is expected to be shared across all the stakeholders involved in healthcare at some stage. From all this arises the need for a platform which provides the facility for efficient collaboration and communication in addition to ensuring high security. Microsoft’s SharePoint is one such platform which has stood out for the amount benefit it has offered to its users in the healthcare industry. Starting from improving the efficiency, driving down operational costs to finally improving the quality of care, the platform has rich features which can be used to develop excellent customizable healthcare solutions to suit the needs for healthcare setups.
SharePoint provides a platform which is quite comprehensive in terms of meeting the demands of the dynamic changes which have been taking place in the healthcare landscape. For instance the main focus areas for all stakeholders in the healthcare are as follows:
- Excellent data management adhering to the regulatory compliances
- Better efficiency in operations
- Reduction in costs for providing care and in running healthcare setups
These factors if achieved are expected to result in better outcomes. Now the outcomes of implementing SharePoint, as is depicted by the wheel, can easily map the aforesaid requirements. With excellent content management features, the platform makes it possible to handle varied types of data i.e. web, records, images, rich media etc. all using a single platform. It becomes a one shop solution to handle the complete content life cycle. This is well complemented by the search facility available that is based upon allocating unique identification numbers to documents. This makes it possible for each document to have a permalink and so be identified irrespective of where it is stored. Even looking for people based on identified traits for e.g. department, experience, specialty etc. is also possible. There are also solutions available to ensure that the data is handled as per the the Health Insurance Portability and Accountability Act (HIPAA) privacy and security standards.
One of the benefits of using info systems, apart from the efficiency factor, is that it gives you access to a lot of data – which can be subsequently analyzed and used in multiple ways. The Insights capability of SharePoint makes it possible for users, who need not be IT literate, to pull out customized reports and dashboards in seconds. Various types of analytics can be performed on the valuable data available to make more informed decisions. Without having to write codes, the Composites feature in SharePoint makes it possible to build collaboration platforms using easy-to-use interfaces. Thus, depending upon need, stakeholders can use customized platforms to successfully collaborate amongst themselves and share best practices besides communicating in an effective way. With its capability for process and system integration besides workflow automation, a number of actions can be easily performed using this platform resulting in tremendous increase in the efficiency levels. There is also a flip side to this. The collaborative platforms also increase chances of cyber-attacks. Since information is expected to be shared across various players in the healthcare value chain, it opens up opportunities for hackers to gain access to critical patient information. Use of mobile devices – laptops, tablets, and smartphones also put patient data at risk since data is accessed remotely in these cases. It is the job of the IT administrators to address such challenges and build impregnable networks to avoid such attacks.
Implementation of a SharePoint application can be in either On-Premise, Cloud or Hybrid. It kind of offers you the flexibility to choose the option most suited given the size of your operations. With its integrated suite of collaborative capabilities, the platform makes it possible for healthcare setups to meet the demands of modern healthcare infrastructure – provision to collaborate, achieve better clinical outcomes, high levels of efficiency and reduction in the cost of operation. Custom SharePoint development teams can help you build projects within allocated budgets and time schedules.
We provide SharePoint application development services. If you would like to talk to one of our expert SharePoint developers, please get in touch with us at Mindfire Solutions.
It is advisable to get the binary large objects such as the file attachments, out from the database. SQL Server as well as SharePoint render support to Microsoft’s RBS ( Remote BLOB Storage) technology. This conveniently allows putting all the Excel, Word or other documents back within the NTFS file system wherein they actually belong.
