Microsoft's SharePoint is an Intranet solution that enables users to share and manage content, knowledge, and applications to empower teamwork, quickly find information, and collaborate across the organization.
$5
Per User Per Month
SSIS
Score 8.0 out of 10
N/A
Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
Atlassian Confluence isn't as robust with document storage but it does provide a good way to share detailed information in article or Wiki format. Microsoft SharePoint is more like a lightweight webpage creation tool while Confluence more like an enhanced notebook. Microsoft …
Microsoft SharePoint is more feature rich but that also comes with the cost of complexity. Needing to learn how to set up folders, documents, etc, with the right permissions isn't difficult, but to make sure it is done correctly does take some time to understand where to do …
Egnyte is the superior solution due to the way it segments data and provides a holistic approach to sharing and access. Microsoft SharePoint provides this a bit but could improve but the value of Microsoft SharePoint is greater given it is included in our subscription.
I like Microsoft SharePoint over Google Drive for its organization. I believe that Microsoft SharePoint keeps things much more organized than Google Drive. Also, typically when you purchase Microsoft SharePoint, you get the rest of the Microsoft Suite. However, Google Drive has …
One drive I think is more for personal use as a cloud storage. SharePoint can be more of use in businesses where teams can easily collaborate in various documents and files. This can also automate other processes to make it easier for the business in their day to day work tasks.
SharePoint is more reliable in terms of data storage, security, and accessibility by only required users compared to ClickUp. Also, SharePoint is easier to learn and use for any user, as tutorials are easily available online. Also, SharePoint is a product of Microsoft, which …
From what I have seen, Google Workspace seems to get the balance better. I think both tech giants are in a position to be indifferent to end user experience.
The reasons for selecting MS SharePoint are: SharePoint provides ease of use and web design assistance and support SharePoint helps you schedule your content for publishing. enables users to share documents with external parties and offers a better internal structure of the …
Since Microsoft SharePoint comes with the MS business office package, it is fully integrated with other office products and really works together with other MS Office products like Word, PowerPoint, Excel, Access, Publisher, etc.. in real-time, so it's really easy to maintain …
Microsoft SharePoint definitely has the highest ranking for use with MS Office packages and integration into Windows devices--mobile or normal desktop devices. The cost for Microsoft SharePoint is also competitive in comparison and with local hosting options within APAC regions.
I prefer Atlassian Confluence for file sharing, wiki markups, and as a better tool for engineering documentation. Microsoft SharePoint is the tool that was chosen for my current organization, and I do miss using Confluence. Both tools get the job done and it is largely a …
MS Sharepoint is much more simpler way to use if we compare it with BOX, Box is very slow loading app not that user friendly. Box need really good quality of connectivity. MS Sharepoint provide good after sales support. Query resolution time is really fast in case of MS …
Both Confluence and Sharepoint have similarities, but they also have significant differences. In both cases, people can use the wiki to exchange information with each other. Many platforms, including Mac, are easier to use with Confluence's better user interface. Compared to …
Dropbox has been used, but this is strictly for getting files from point A to point B with them being backed up. It is great and has great integration with the file explorer to access files. Adobe Sign is great for documents needing signatures but only serves this one purpose.
Both are very similar. Azure is cloud based. It is easier for the organization who uses cloud based application. The SQL Server Integration Services is cost effective. Azure was more on the expensive side for our organization. Azure was a little complex, it needed special …
I think SQL Server Integration Services is better suited for on-premises data movement and ADF is more suited for the cloud. Though ADF has more connectors, SQL Server Integration Services is more robust and has better functionality just because it has been around much longer
Fivetran, Stitch, and Etleap are all 1000x more modern than SSIS and 100x less aggravating. While those tools are mainly used to sync data rather than transform it, the ELT model works much better than the ETL model in most situations.
We just selected SSIS because we use SQL Server Management System (SSMS) to manage our database. As SSIS is a component of the Microsoft SQL Server there are no problems with integration and everything works perfectly. In addition, we don't have to learn how to use another …
Low-cost relative to other products - in fact, zero cost if one is considering the license cost as being for the database engine with Integration Services added on. It has a comparable range of functionality and performance and as such it's a 'no-brainer' to use SSIS over …
SnapLogic and Azure Data Factory are better than SQL Server Integration Services mostly because they are Integration Platform as a Service (IPAAS) services, whereas SQL Server Integration Services is an on-premise. So the basic differences such as, need a VPN to connect to the …
SSIS is similar to Alteryx and Informatica PowerCenter in a way because these are all drag-and-drop ETL tools with similar functionality. Alteryx is a step ahead because it has some advanced ETL functionalities including statistical calculations etc. and a better ability to set …
Alteryx Designer is easier to use for machine learning models. The functionality of drag and drop is the most valuable. It is a very user-friendly tool that can be understood easily. My teams also work with other solutions, such as Integration Services, and these solutions are …
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 …
SAP Business Objects was a primary concurrent software against the MS SSIS but it has a more steep learning curve and requires additional investment into the SAP-related software infrastructure. With SSIS one can start easily with simple data extraction / DTL tools of Express …
I personally prefer SSIS. There are items that each do better than the others, but the ease of use of SSIS, along with its extensibility to 3rd party, ability to write any code required in the tool, and uses the same IDE for the MS BI suite (more of an issue if you're not a …
I used the Pentaho Data Integration (PDI) ETL tool. The PDI ETL tool does not have a public user collection like the SQL Server Integration Services(SSIS) ETL tool. Therefore, you may not be able to find instant solutions for your problems. But it has advantages over the SSIS …
SQL Server is already in our wheelhouse so it only made sense to utilize the tools we already had available to us--SSIS, SSAS, & SSRS. Other non-technical users seem to be more comfortable using alternatives to SSIS. However, these alternatives are not as good as SSIS at …
These are all great products and, honestly, can move data faster. They include more enterprise features and have some great qualities about each. However, they all cost a lot depending on the implementation you need. With SQL Server Integration Services, you do not have any …
When looking to evaluate different options, we looked first to the experience and software we had in-house that would accomplish the job. When assessing alternatives outside we were looking for the tool that would offer the most flexibility.
It’s basically a free tool and it has more features than anyone would ever need. If you look online for answers for SISS packages you will find a world of information that can cover almost any situation for your business. This tool can be used in any business and it provides …
SSIS is a very basic, developer-oriented ETL tool and while it lacks many of the nice UX features of its competitors it is a powerful tool that comes as a part of SQL Server and, in the hands of experienced developers with domain knowledge, can meet most organizations' ETL …
SSIS and Denodo differ in their approaches to ETL and Data integrations. SSIS is more affordable from a cost and licensing perspective (if you have Microsoft licensing), but Denodo is no slouch. If you go with Denodo, you are not creating data, there are pros and cons to …
SQL Server Integration Services does a good job for our SQL Server environments and was selected for that reason. For a SQL Server-only implementations, I would recommend SQL Server Integration Services. When we compared SSIS to other ETL providers against SQL Server, SSIS was …
SharePoint Document Management excels as a central repository for storing, organising, and retrieving documents. It supports version control, metadata tagging, secure access, and integration with tools like Power Automate. At our organisation, it's used for managing contracts, policies, and supplier documents. SharePoint Workflow Automation integrates with Power Automate to streamline approvals, gather feedback, and automate recurring tasks. This reduces reliance on email chains and manual trackers.
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.
We have too much invested at this point to do anything different and there are too many reasons as a company our size to keep it. We are heavily licensed out for Microsoft and have 12 years of SharePoint development baked into who we are. Extracting that as a tool at this point would be dumb and devastating. There are no like-kind competitors to it at an enterprise level that scale and integrate as well.
SSIS is responsible for running core business processed managing core business data. It can be managed, improved and expanded using minimal internal resources. It is also able to support all of our current data infrastructure. Replacing SSIS would be time consuming and costly with no apparent ROI.
No usability issues reported. Individual teams also have allocated areas which replace legacy shared drives on local LANs. Access to Sharepoint resources is fully integrated with corporate Active Directory with additional two-factor authentication required for administrative users. Users have access to Microsoft Services Hub which allows you to create, manage, and track support requests while staying current on Microsoft technologies with access to select self-paced learning paths
It is easy to learn, works great on many features, but needs improvement on ETL troubleshooting and performance monitoring functionality. Great tool on Microsoft stack. it is great with simple, structured datasets. Once logic gets fancy like nested conditionals complex joins, reusable transformations, versioned logic …SQL Server Integration Services (SSIS) packages become hard to read and harder to maintain. Source control is painful. Errors can be cryptic Logging takes effort to set up well Debugging in production is limited.
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.
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.
The face to face training I received was on SharePoint Administration. It was rushed as there was a lot of information to cover and the application of the labs weren't that great either. I like to be able to relate what I am learning to what I am currently doing.
I like to learn at my own pace and online training allows for that. Additionally, you can skip through pieces of content that you already know or are already comfortable with. Microsoft actually offers great videos on their website for basic fundamental SharePoint Training. I have used these training videos in some of my own training sessions with end users.
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
The reasons for selecting MS SharePoint are: SharePoint provides ease of use and web design assistance and support SharePoint helps you schedule your content for publishing. enables users to share documents with external parties and offers a better internal structure of the content and better indexing and searching capabilities.
Both are very similar. Azure is cloud based. It is easier for the organization who uses cloud based application. The SQL Server Integration Services is cost effective. Azure was more on the expensive side for our organization. Azure was a little complex, it needed special training to use it. Azure was not accurate with complex data.
We've recently implemented Microsoft SharePoint access via iPads for our Template teams out on job sites. They can easily upload CAD / Laser files into Microsoft SharePoint for our production team to review in real time. Serious ROI when we don't have to wait for our Template team to get back to the shop!
We have multiple physical locations. Microsoft SharePoint allows users at each location to collaborate by working on documents simultaneously. Allowing us to solve multi-site problems & strategize on multi-site initiatives much faster!
We can also share key information with external partners. As long as they have a registered MS account (not necessarily an O365 account) we can share our information with them in a variety of ways. This allows consistent & concise communication with our partners.
Without this, we would have to manually update a spreadsheet of our SQL Server inventory
We would also have poor alerting; if an instance was down we wouldn't know until it was reported by a user
We only have one other person who uses SQL Server Integration Services , he's the expert. It would fall to me without him and I would not enjoy being responsible for it.