Sql Server Reporting Services and Multiple Sharepoint Farms - sharepoint

I was wondering if you can have a single SSRS 2008 server be used for two different sharepoint farms? I have a SSRS 2008 box and would like to have two different reporting instances, one for each farm. We're in the middle of a transition from WSS --> MOSS, and I need to be able to support reporting on both.
It seems when you run the sharepoint configuration on the reporting box, it asks for the farm to connect to.
Any suggestions welcome.
Thanks,
-- Chad

Reporting Services contains 2 parts, the SQL instance and the front-end.
If you want to use Reporting Services in SharePoint Integrated mode, you need to create an instance for each farm. However, both SQL instances can be in the same SQL box.
However, the reporting service front-end will need to be part of your SharePoint farm, so this part will need to be separated.
If you're planning to use the old RS webparts (iframe) or access RS webservices through code, you can do anything you want.

Related

SPFx to connect to local SQL Server Tables,Stored Procedures & view.. Approaches to follow

I am working on a migration from SharePoint 2010 to SharePoint Online. Where inside the on-premises the customer has a configurable Web Part (Server-side of course), which allow users to do the following:-
Specify a connection string to connect to on-premises SQL server
Specify the Table or Stored Procedure or View to connect with.
optionally to pass a Parameter to the Database.
After that the web part will show the results from the database and allow the users to filter the data which will be shown in a tabular format.
Here is a screenshot of the web part setting:-
Here is a screenshot of a result from one web part instance:-
So can we build similar web part using SPFx? If the answer is Yes, then is there an available 3rd party web part we can benefit from? Finally , i am also open to other approaches to achieve our work other than build/using SPFx web part.
Please note that I am already aware that i can create API for the DB and connect SharePoint Online to On-prem DB using gateways.. but my main question is; how we can develop a dynamic web part (similar to the current on-prem web part), which allow us to show & filter data from on-prem database's Tables,Views & Stored procedure, by just specifying which components (table,view or Stored Procedure) we want to show the data from .. Is there a documentation to create such SPFx web part? or if there are 3rd part SPFx web part that we can benefit from?
You have two possibilities to solve this challenge:
If you only have the possibility to refactor this Farm Solutions
Web Part to SPFx, consider using a local data gateway to
help as an artifact to generate the connections from the local
environment to the cloud, and suddenly, you can persist these
registered connections into a restricted access SharePoint List (for example) and consume with a combo box. But if you
can't make progress with this approach, you'll need to consider the
2nd possibility (this one is more difficult);
Develop a Provider-Hosted SharePoint Add-In, which can be hosted on on-premises IIS and can connect to your various on-premises databases as a shared connection string in your example image above.
I've using Microsoft Graph Connector to pull On-prem SQL data into Microsoft Search (via Microsoft API), and then combine that with PnP Modern Search for query/filter results by selecting Graph as data source.
This feature is listed under MS Search & Intelligence. You can
Specify a connection string to connect to on-premises SQL server
Specify the Table or Stored Procedure or View to connect with
-- You define it in the PnP <Modern Search web part. Note that you can only filter/query/refinable if you've defined it in step 1 or 2 above.

Requirements to set up a document repository for the client using SharePoint from Azure

I have to develop a document repository on SharePoint from Azure. As I have new to Azure, I do not know about the requirements to set up the entire SharePoint and make it run like the SharePoint online, 2013, etc.
As much as I have read, it says we need a VM, a SQL server and Sharepoint. I am unsure if this all what we need and what is the role of the VM and SQL server in this.
Can anyone please share the suggestions or the experiences for this?
If you are going to host document repository, you need to check
Office 365's OneDrive or SharePoint components. This is the PAAS
model.
If you want to have a dedicated portal using full SharePoint features, you need to setup a virtual machine, on which you setup the entire installation of SharePoint just like you do on a actual server. This will be the IAAS model, where Azure just offers you hosting service for the VM. SQL server is required for hosting the backend database for SharePoint (documents, users, roles etc)

Retrieving a PerformancePoint dashboard in Windows 8 application

I am using SharePoint 2013 and Windows 8 application.
Is it possible to connect to a PerformancePoint dashboard via the application and display items like the dashboard, graphs with drill to/drill down options?
I have no real experience with SP 2013 and PerformancePoint, the dashboard will be created by others. I need to connect to it and retrieve items.
Can you point me in the direction of a tutorial?
Thanks,
Andrew
Not knowing your Windows 8 application it hard to answer this. To truly use PerformancePoint for what it is intended, the Windows 8 application would need to expose the data thought an SQL Server Analysis Services (SSAS) Data Cube.
If it does you can build a PerformancePoint dashboard based on the cube's data. If you do not have an SSAS Cube, PerformancePoint may not be the solution for you.
I recommend reading this article on MSDN to get an overview of PerformancePoint, PerformancePoint Services in SharePoint 2013.

How to migrate the data between two SharePoint Farms?

I want to perform the data migration between two SharePoint farms located on the same active directory. I don't know on how to migrate the data from one SharePoint from to another new SharePoint Farm
Several ways of doing this:
1) Backup content database on source farm and restore in target farm, then attach to a web application.
2) Create (i.e. export) a content migration package on the source farm and import on the target farm
3) Set up a content deployment path between the source and target farms (probably not appropriate in this case)
All of these are documented extensively on Technet. If you have custom or third-party code you will need to deploy these to the target server also.
The fundamental processes will be like this:
Create a new web application in your new WSS server.
Follow the instructions in Move content databases between instances of SQL Server.
However you may not be able to perform all of the steps exactly as written if your previous server farm is not available. The main thing is that you get the most recent backup of the databases restored on your SQL Server, then follow these steps from the linked article:
In Central Administration, on the Application Management page, in the SharePoint Web Application Management section, click Content databases.
On the Manage Content Databases page, click Add a content database.
On the Add Content Database page, type the exact name of the transferred content database, and then click OK.
Repeat steps 14 and 15 for each database you are adding. Be sure that you select the correct Web application from the Web Application menu for each database.
I don't know your farm topology but if you are sharing the same SQL Server used for the dead server farm, make sure that the dead farm is completely powered off. You don't want two different SharePoint farms accessing the same data (especially if one is in an inconsistent state).
If the old farm is alive and not in inconsistent state then you will be better off using a migration tool even if the versions of new and old are same.
The reason is that service packs, patches as well as order of their installation causes differences in SharePoint instances which can mess backup-recovery mechanism.
Migration is much more forgiving as it pre-assumes that differences exist between source and destination.
Several migration tools are available with Sharegate being my favourite.

Sharepoint - Providing data outside intranet

I know that using SharePoint internally is free, but what if I create an application that will provide some of the data stored in SharePoint externally? Is it legal way to do things or do I have to pay for full SP licence to do that?
The cheapest option in your case may be to install WSS + Sql Server 2008 Express on Windows Server Web Edition (~£400) to avoid paying for CALs or External Connector.
Only Windows Sharepoint Services (WSS 3.0) is free and included in Windows 2003 and 2008 and thus being licensed along with it. If users need to authenticate on the site (i.e. using forms auth), then you either need a Windows CAL for each user or an External Connector License. If you do not have user accounts ("Anonymous access"), then you should not need any additional licensing.
On the other hand, Microsoft Office SharePoint Server 2007 (MOSS 2007) is a commercial product that requires licenses for any use, internal or external.
IANAL, so check with MS Licensing for this.
Using SharePoint internally is not free. You need server licenses for each server copy you have and client access lincenses (CALs) for every client that uses it - internally. There is a separate model for licensing SharePoint hosted and published externally.
You should talk to your microsoft licensing provider about this, it's not really a programming question, it's a licensing question.
There is a licensing fee for providing SharePoint connected to the intrenet. the situation where you have your own application reading data from SharePoint (e.g. webservices/rss) and exposing that to the internet is quite different and not likely to be considered for licensing.
Given that you are only exposing part of the data and none of the interface, you should be okay. If you are using CALs to access SharePoint, I believe the user running the application you access SharePoint with would use up one of those CALs.
You would really need to check with your SharePoint licensing guys to be 100%.

Resources