MS SharePoint / SQL vs. TARGIT

A simple and important scenario well suited is that you can configure alerts to notify you when the production server fails. another best feature is the report server is the central component of reporting services. For me something less appropriate is that the admin must ensure optimal performance for farm operations, they recommend that you install SQL Server on a dedicated server that does not run other farm roles and does not host databases for other applications.

Incentivized

Targit is very strong when the data is presented to the system. Because of this, we are able to report on almost all of the information that is valuable to us. When we have questions or ideas on how to better leverage Targit, they are great to work with. We track our sales progress/process in Targit and AP tracks things such as outstanding invoices, open invoices, etc

• 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

• Quick start-up and report turnaround time.
• Easy drag and drop capabilities as well as user friendly command options.
• Ability to share reports among other users making it easy to use an already created report and simply changing the criteria to suit your own needs.
• Ability to save a base report that can be modified as needed repeatedly, instead of recreating from scratch.
• Easy visual for final layout.
• Ability to run multiple reports within one screen without jumping around.

Incentivized

• 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

• Probably one of our biggest complaints from the user community is the inability for the user to see the details behind the data. I know with the tool you can write reporting services reports that would allow users to see the detail by right clicking on a measure and selecting Actions, but for a very lean IT shop there simply has not been time to build these Actions for every possible scenario a user might want to see detailed reporting on.
• Another complaint I've heard is the inability for the user to know exactly what the data represents from the source. If Targit had maybe some type of capability to hover over a measure or dimension and see a pop up of a more detailed description this might help resolve that issue.
• The most difficult concepts to teach our users is how and when to use comparisons and the syntax for calculations. Creating comparisons has become much simpler with the 2k11 release but it is still difficult for my users.

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.

It is very easy to use and I am proficient at this point to be able to figure out how to run most of the reports I need. I have had the time to "play around" in TARGIT and really teach myself about the visibility settings and other aspects - though other users have needed help with some of these aspects - but once you conceptually understand how to build the reports, it is very simple from a power user perspective.

Incentivized

SharePoint is very complex. This makes usability somewhat difficult from an IT perspective. An IT generalist will be able to pick it up and run with basic tasks. More customized functions would require significant specialized training and therefore limit what a standard user would be able to achieve. From an end user perspective, it's pretty straightforward to use.

Incentivized

Everything on the back end needs to be correct, which sometimes it may not be set up or missing some variables. Some of the more difficult parts of Targit require a lot more attention and object creation to work properly

It's been fantastic in terms of Premier Support so far. If there is an issue and if you report if the product has an issue, they will act upon it immediately. In some cases, if you design/develop something using the platform, Microsoft appreciates it and... publishes it on their public website. But you have to wait for some time if it is a non-Premier Support issue as you may experience delays.

Everyone I've dealt with at Targit genuinely cares about me and my success, and they respond to questions quickly and accurately. There is literally nothing more I could ask for from their support.

Incentivized

Not implemented in best practice way, there are many customizations

Make sure all of the back end work is done prior to getting Targit set up. Every variable you may need for calculations needs to be correct and every item needs to be uniform so it is read properly.

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

It really met our business requirements when we were searching for a reporting/Bi tool and the flexible business model of being able to introduce additional functionally as your organization grows and requires it made the investment decision the right one for us. The functionality available in comparison to the investment is well worth it.

Incentivized

• I've installed SharePoint in many different industries and each industry has seen greater collaboration among their teams both locally and nationally. The ability to collaborate more efficiently has reduced the need to have employees centrally located.
• Companies which have used SharePoint in a end user training portal have had great ROI, since they can create the content once and share with all their users who subscribe to their training service. The web content management aspect of SharePoint is a very helpful feature.

• We have been looking at our Product Hit Rate by Customer instead of just looking into Customer hit rate and adjusted our offerings accordingly.
• Giving people the ability to run their own ad-hoc reports rather than to request them from IT is a great benefit to my department.