Logi Symphony vs. MS SharePoint / SQL

Considering it's price point in the market, Dundas BI offers a lot of functionality. They are constantly adding features and bug fixes which is great, but also means there are always updates to take if you want everything to work as expected. The standard user interface is pretty easy to understand, but it takes a while for developers and power users to become independent of documentation.

Incentivized

As I mentioned in my previous answers, MS SharePoint is very useful as a shared drive for the organization and is very easy to manage. It also helps us import data from SharePoint directly into PowerBI for creating reports. According to my understanding, only share link features should be improved.

Incentivized

• Project organization from Development to Production, you get a production and development license but I think the best way to do it is with DEV and Prod project in the Production box. Use the development box for testing updates and really crazy things. With the Dev and Prod projects on the same box, you just publish from Dev to Prod and you are done. Users only have access to the Prod projects so no one can mess up what you are working on.
• Security - If you have a hierarchy (subsidiaries, divisions, department, teams) and you want each group to see only their data, then Security hierarchies are for you!
• Dependent filters! What's this you ask? Here is an example of how it can be used, in your company you have departments and who works for what department is in your database. You make a dashboard that has a department filter (only show these departments), a managers filter, and employee filter. Not every manager or employee is in multiple departments usually only one. With dependent filters you can say that the manager and employee filter are dependent on what is selected in the departments filter so when you go to filter them they only show the managers or employees that are part of that department, and you can even it do so employees are not only dependent on department but on manager as well. Then it gets even better as it can be done in reverse as well so when you select a manager then go to the department it only shows the departments he works for (there are better situations where this is more useful).
• It is scriptable! From calculate columns, null replacements, button actions, load actions, hover over events there a way to do what you want.
• They are constantly improving and listens to your suggestions.

Incentivized

• Flexible - able to make any changes we would like vs traditional service desk system.
• ROI - We were already using SharePoint for internal intranet, so we are simply getting more use out of licensing we had already committed to.
• Easy to use for end users.

Incentivized

• Not too many cons for how we use the application. It really is easy and powerful. Very powerful.
• Licensing is one thing that could be looked into. It is simple, but a little confusing. For example, if I get a license today, but a new release comes out tomorrow, it seems that the license doesn't work with the new release. Maybe that is by design, but it would be nice to clearly understand.

• It is hard to setup and nightmare
• It requires a of infrastructure, thus it could be costly because of requirement and licensing required for everything to run smoothly
• If it is not setup and organized properly from the beginning it could be maintenance nightmare
• It is hard to have "test" environment to do patches or similar

Incentivized

This was a long-term buy-in from a corporate perspective, to remain in the SharePoint space. Migration is certainly possible, which is good for planning and having options further out. At this point, the only planned migration is to eventually move the architecture up to SharePoint/SQL 2013. At that point, we will be able to leverage some greater efficiencies, some enhanced content design and management features, and some more current social features. It is well worth a full consideration in any shop looking at a new implementation of or migration to SharePoint (although you will probably be considering 2013 versions or beyond in those discussions), but the platform should be a strong competitor to any alternatives. Realizing the capability of a fully-branded and customized website was not part of the original choice for the architecture at Lincoln, but seeing it implemented and functioning now with this capacity far beyond original expectations has certainly cemented plans to continue using it.

We are still in the implementation phase, but so far we are finding it to be easy to use and learn. The eLearning courses that they have made available for free, as well as User Forums and other training videos have made even difficult concepts easier to understand.

I gave this rating due to MS SharePoint being a big help with our userbase. We have a lot of users that are just old enough to not have much technical skills or they have been in this industry long enough to where they haven't really needed to utilize much technology. MS SharePoint helped us move beyond that barrier without too many bumps and bruises.

Incentivized

We have bi-weekly calls with our Success Manager, as well as access to support as needed. Any question that I have had, multiple people have been willing and able to jump on a call to talk me through it, or send an email with the solution

I've only had to call in to support on one occasion but they were able to work though our issue and find a solution that did fully resolve the issue in a timely manner. I can't always say the same about support from other companies so it was a refreshing change to have support that did help.

Incentivized

Providing that you have the client's needs well known, creating BI content using Dundas BI is a walk in the park!

Mo major insight regarding the implementation if very well documented for standard products.

Incentivized

We have tested Tableau prior to Dundas BI and though Tableau is a great package in itself, Dundas BI is much more cost-effective for our needs and requirements and hence zeroed in on Dundas BI. We have also tried microstrategy but it has a very dated UI and doesn't suit our needs in today's more modern world

Incentivized

At the time of the two large projects, SharePoint was the enterprise solution so we were required to use that. We have since lobbied the enterprise teams to review and consider Atlassian Confluence and were successful. Confluence is cheaper than Sharepoint which is why we wanted to bring that in. The enterprise has now made Confluence an enterprise solution as an alternative to SharePoint. After using both I think SharePoint has many more add-ins than Confluence. It has much more customization ability than Confluence. SharePoint is not good for mobile readiness. Confluence is so there is a difference that might lead you to Confluence over SharePoint. I would also say that SharePoint is very document-centric and that Confluence has better KM than SharePoint does. even with the use of SQL Server. We were told that we could not use Google Drive even though it had features we liked.

Incentivized

• Coming from an SQL based standard delivery model, Dundas BI has provided a fantastic rate of ROI.
• The preparation and delivery time has reduced from weeks to just a few hours.

Incentivized

• ROI for ms SharePoint/SQL considering that is the best database engine with excellent features that help you to have all information in your hand.
• Something negative could be license format.
• These are the best relational databases in the market with powerful features that complement your system.

Incentivized