MS SharePoint / SQL refers to Microsoft Sharepoint, a web-based collaborative platform, being used in tandem with Microsoft SQL Server to provide business intelligence analytics and reporting. They can provide BI content such as data connections, reports, scorecards, dashboards, and more.
N/A
Sigma
Score 9.1 out of 10
N/A
Sigma Computing headquartered in San Francisco provides a suite of data services such as code free data modeling, data search and explorating, and related BI and data visualization services.
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 …
Simple: MS Sharepoint/SQL is the best and robust databases motor now are incorporating some features in order to improve users and DB admins experience.
Box is a content storing portal where you can host and share documents/files to others. But it does not have [Sharepoint's] capabilities like... versions, automation, email approvals, etc. And Microsoft Exchange is a mailing database that can be used for exchanging data using …
Has better support than MySQL and more developers are familiar with it. Oracle syntax is more cumbersome and less developers are experienced these days with Oracle.
If you are looking for a document management and collaboration tool to use as a web portal that comes with SQL data base and easy to manage and something you can learn very quick, look no further than SharePoint but if you need a pure database then this is not for you.
We use MS SQL more just because of how widely it's used and how popular it is. It's easier to install, maintain, and support compared to the other ones we've tried.
Vice President, Chief Architect, Development Manager and Software Engineer
Chose MS SharePoint / SQL
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 …
At its core, MS SharePoint (with SQL) is for managing document-based content. It falls just short of being a best in class records manager (it does offer some features for this though), and it isn't the easiest to solution to make great looking modern and engaging web sites. …
We looked at Google Drive but it didn't have the API and integration that SharePoint has with 3rd party software providers. Also, Google Drive has basic functionality compared to MS SharePoint and how you can customize and build-out.
I haven't used any other products that compete with it. I started my career at Microsoft and the two subsequent locations have also been Microsoft shops.
Dropbox is a user-friendly product, but Sharepoint is a native Microsoft product that can be implemented into any Microsoft products, which are used mostly in our environment. Finding solutions on the internet is much easier, as it is used commonly by other organizations as …
I have used both Google Drive and Zoho Docs which seem similar to MS SharePoint. The main differences I noticed as a user is that the user interfaces in both Google Drive and Zoho Docs were much more intuitive and they were much easier to navigate than MS SharePoint. There …
We had staff resources able to create, configure, and mange our sharepoint environment, so it made sense for us and gave us greater flexibility than these turnkey solutions. Certainly each solution has its merits and each are completely different price points. We already had …
We evaluated Atlassian Confluence and compared it to our current SharePoint implementation. We felt that the two products were quite similar in the user experience but we chose to keep our SharePoint farms up and running. This was mainly due to the cost of switching and the …
I am not an expert in any of these, though from my brief exposure to Looker it felt like a steeper learning curve, more appropriate to companies with dedicated and skilled BI engineers, whereas Sigma (and Tableau, and Looker Studio) offer a quicker and more intuitive interface …
Sigma Computing exclusively uses Snowflake as its data source, which enhances data security by not caching or extracting data locally. Tableau, on the other hand, allows a broader range of internal databases and files like SQL Server, Postgres, etc., and supports extracted …
maintianed is very user friendly. Its various ways of embedding helped us in various aspects. The usage of control ids of the filters as parameters helped us in optimizing very longSQL queries. The live Support team every weekday is a very great intiative that helped in quick …
I'd rate Sigma to be extremely similar to Sisense except it looks not as nice. I would say that as a tool, Sigma is more user-friendly than Tableau, Power BI, Trevor, and Metabase.
I do feel that Looker is far more powerful and looks great, but I also recognize that Looker does …
Sigma computing has better pricing than the competitors. We're always looking for what is good for the price but also gives us all we need to complete our reporting. It also brings about a lot of updates that are nice to see. The embedding helps other BI tools sometimes.
Sigma has a better view of tables and it is much easier to create new data sets/aggregations. Tableau is better in some visual aspects because there is more customization available, albeit more confusing than Sigma to do. Sigma is very intuitive and did not take long to learn …
Sigma Computing had better functionality and is beginner friendly. While Tableau is a more well known product, Sigma Computing has a better user interface that is easier to comprehend for those without a non-technical background. This makes it easier to showcase dashboards to …
Sigma is the easiest to use from a workbook developer perspective, and from a non-technical end user perspective. Everything from administration, semantic layer setup, to creating dashboards is easier in Sigma than these other tools. Developing content in Sigma is enjoyable, …
Sigma has the capabilities of the other BI tools. I think it's pretty user friendly and easy to learn. Many of our stakeholders are used to using Excel so it's nice that it is a smooth onboarding process for them. We haven't looked into much of the visualization capabilities so …
I have found that Tableau can be used to create a greater variety of custom and complex visuals, though these visuals are far more difficult to create in a quick turnaround. While Sigma may be more limited in terms of what types of visuals can be create or how customized they …
With Looker, to be effective, a substantial amount of coding & modeling needs to happen in LookML. Being another language to learn, users have to context switch again from at a minimum either SQL or Python into LookML. The concept of being able to source control, code review, …
Less visually appealing. Feels like fewer pixels. Harder to make graphs and visuals. Really good integration with snowflake and intuitive usage for custom equations and filters.
sorta in the middle. One thing that differs than domo or power bi, is that those softwares bring in the data into the platform, instead of how sigma runs a query against our data warehouse each time a user interacts with the dashboard (there is some small caching, so not always)
Sigma is by far the best. It is easiest to learn and easiest to use on a day to day basis. I never have to wait for dashboards to load and it's very easy to understand the variables that are going into my visualizations. Best of all I can manipulate the data within Sigma …
flexibility, works really well with snowflake, export capability, level of support, the fact that Sigma Computing is a start up and improving so quickly. Web based software
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.
Scenarios where Sigma Computing is well suited: - Data Reporting and Visualisation : It is suitable for dashboards that integrate data from multiple back-office systems - Search and Filtering Capabilities: It provides a robust platform for searching through datasets and visualisations. Scenarios where Sigma Computing is less appropriate: Handling of null values and dynamic table adjustments
Viewer level license is quite limited. These users can't download data or even add filters on datasets. Something to keep in mind.
Directly querying the underlying data warehouse will lead to increased usage. Not a big deal on something like Redshift, but your Snowflake consumption will increase, potentially by a lot.
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.
Because we are very satisfied with the product and would most likely renew because of the services it provides. It is a tool that you bring into your organization and let it change the way you analyze your data, present your data and share you date within the Respective teams
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.
It has a clean and modern interface. However, it is not completely intuitive. I think it would be better and easier to navigate with more Windows style drop down menus and/or tabls. There is a significant learning curve, but that may be due in part to the technical nature of this type of software tool.
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.
They are very friendly and informative. They are quick in resolving our queries and help us understand very minute things as well. They are quick in creating feature tickets based on our custom requirements, and they would also create a bug ticket if there is any discrepancy and get that checked on time.
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.
I am not an expert in any of these, though from my brief exposure to Looker it felt like a steeper learning curve, more appropriate to companies with dedicated and skilled BI engineers, whereas Sigma (and Tableau, and Looker Studio) offer a quicker and more intuitive interface for smaller companies like ours without dedicated BI resources on staff.
Monitoring health of cloud platform has allowed the company to anticipate issues before they affect customers – Sigma prompted us building a canary monitoring process that provides customer container health.
Customer success has used an activity report to discover customers running runaway processes that they were unaware of, creating an alert to contact the customer and prevent an embarrassing situation.
Customer success uses the activity report to prompt conversations regarding increases or declines in behavior that led to increasing contract limits or addressing churn concerns.