Layer2 Cloud Connector vs. SQL Server Integration Services

We had a scenario where our clients have thousands of external party vendors/committees who regularly sync SharePoint data. Managing thousands of external parties can never be possible without using a Layer2 cloud connector. We managed the local network sharing and SharePoint integration by using the Layer2 connector. Layer2 is convenient with a large amount of data as the per-user license is high.

Ideal for daily standard ETL use cases whether the data is sourced from / transferred to the native connectors (like SQL Server) or FTP. Best if the company uses MS suite of tools. There are better options in the market for chaining tasks where you want a custom flow of executions depending on the outcome of each process or if you want advanced functionality like API connections, etc.

Incentivized

• Layer2 provides best connectivity with SharePoint
• It syncs local network shared files to the SharePoint
• Provides details file history

• Ease of use - can be used with no prior experience in a relatively short amount of time.
• Flexibility - provides multiple means of accomplishing tasks to be able to support virtually any scenario.
• Performance - performs well with default configurations but allows the user to choose a multitude of options that can enhance performance.
• Resilient - supports the configuration of error handling to prevent and identify breakages.
• Complete suite of configurable tools.

Incentivized

• Per User cost is expensive
• A lot of pre-requisites
• UI needs to be more user-friendly

• SSIS has been a bit neglected by Microsoft and new features are slow in coming.
• When importing data from flat files and Excel workbooks, changes in the data structure will cause the extracts to fail. Workarounds do exist but are not easily implemented. If your source data structure does not change or rarely changes, this negative is relatively insignificant.
• While add-on third-party SSIS tools exist, there are only a small number of vendors actively supporting SSIS and license fees for production server use can be significant especially in highly-scaled environments.

Incentivized

Some features should be revised or improved, some tools (using it with Visual Studio) of the toolbox should be less schematic and somewhat more flexible. Using for example, the CSV data import is still very old-fashioned and if the data format changes it requires a bit of manual labor to accept the new data structure

Incentivized

SQL Server Integration Services is a relatively nice tool but is simply not the ETL for a global, large-scale organization. With developing requirements such as NoSQL data, cloud-based tools, and extraordinarily large databases, SSIS is no longer our tool of choice.

Incentivized

Raw performance is great. At times, depending on the machine you are using for development, the IDE can have issues. Deploying projects is very easy and the tool set they give you to monitor jobs out of the box is decent. If you do very much with it you will have to write into your projects performance tracking though.

Incentivized

The support, when necessary, is excellent. But beyond that, it is very rarely necessary because the user community is so large, vibrant and knowledgable, a simple Google query or forum question can answer almost everything you want to know. You can also get prewritten script tasks with a variety of functionality that saves a lot of time.

Incentivized

The implementation may be different in each case, it is important to properly analyze all the existing infrastructure to understand the kind of work needed, the type of software used and the compatibility between these, the features that you want to exploit, to understand what is possible and which ones require integration with third-party tools

Incentivized

We had also used Microsoft One Drive as a syncing tool but it requires Office365 for managing and syncing data across thousands of vendors which was not practically possible to manage users on Office 365. Layer2 resolved this issue by having 3 user licenses and they are enough to periodically sync all external parties' data with our SharePoint online.

I had nothing to do with the choice or install. I assume it was made because it's easy to integrate with our SQL Server environment and free. I'm not sure of any other enterprise level solution that would solve this problem, but I would likely have approached it with traditional scripting. Comparably free, but my own familiarity with trad scripts would be my final deciding factor. Perhaps with some further training on SSIS I would have a different answer.

Incentivized

• Layer2 resolves the time management issue
• Resolved data syncing issues across different external vendors
• LOE optimisation with using Layer2 connector.

• Data integrity across various products allows unify certain processes inside the organization and save funds by reducing human labour factor.
• Automated data unification allows us plan our inputs better and reduce over-warehousing by overbuying
• The employee number, responsible for data management was reduced from 4 to 1 person

Incentivized