We want to have scalable Reporting services. And we need to install Custom Rendering Extensions on this scalable Reporting Services. This is the main requirement for us. SQL Azure Reporting doesn't suite the requirements, because it is impossible to extend this service with custom rendering extension. We had an idea to install Reporting Services on each instance separated from SQL Azure and Azure Reporting, but Rendering Extensibility is not available in free editions of SQL Server and it costs too much to use paid edition. The database of these reporting services instances will be stored in SQL Azure and we will be able to leverage scalable Reporting Services tool with the required rendering extension. The problem is price, complexity and no benefits from SQL Azure Reporting. So, we got stuck with Microsoft clouds. And don't see any reasonable solution with Microsoft clouds.
So we considered Reporting Services on EC2 as they have special cloud license. And we are not quite sure whether it is possible to achieve what we need or not.
We've found that it's possible to install SQL Server2008R2 on EC2 so that the data of the database will be stored in EBS which is available to all the instances. So we have scalable Reporting Services in that case.
The question is lying in the Amazon Virtual Images:
We suppose that we need to install predefined configuration with Windows OS and SQL Server 2008R2 and we wonder if it (1) includes Reporting Services, (2)is it possible to install some more software on this predefined virtual machine (rendering extension), (3)is it possible to organize such scalable Reporting Services with Custom Rendering extensions and to leverage load balancing and etc.?
You don't have to use the AWS provided SQL Server 2008 R2 AMI if you don't want to.
If you bring your own licenses, you could go with a base EC2 install, and then install whatever software you want over the top of it.
ie - install the Windows AMI, and then run the SQL Server installation of your choice. The second step then is to install any additional extensions you require.
I would also recommend that once you complete the installation that you create an AMI of it so that you can repeat the installation at a later date.
Related
When subscribing to the Azure SQL SaaS. Can I get access to SSIS and SSRS?
SSIS: Does a Azure SQL subscription allow me to build SSIS package on my local computer.
SSRS: Do I need another on-premises license to run a reporting server? As I understand, there is no SaaS version for SSRS, does this mean I will have to buy a full SQL server license for reporting?
Thank you in advance.
Microsoft's SaaS offering for BI and Reporting is Power BI. Which is adding support for traditional SSRS reports, and self-service data flows. See announcement here.
And if for all SQL Server development, you can always use the free SQL Server Developer Edition and SQL Server Data Tools on your local machine.
You need to have a VM to run SSRS which means you need IAAS. For SSIS you have Azure support using Integration Runtime means you would be using SSIS Catalog in Azure SQL Database.
When you procure a VM, you could always opt for VM with Sql Server installed else you could bring your own licensed version with you. Also there is the free Sql Server Developer edition available for solely personal usage. For SSIS, not really that you have to make the development in cloud - you would be using SSDT and then publish your packages to cloud.
Links - deploy & run ssis package in azure & procure Integration runtime
We have assumed maintenance of a legacy 32bit application. I installed TFS 2008 to use in maintaining the project.
We will never use reporting or sharepoint. I cant create a project because of issues with SSRS.
(The Project Creation Wizard encountered a problem while creating reports on the SQL Server Reporting Services on OHSENSS801. The reason for the failure cannot be determined at this time. Because the operation failed, the wizard was not able to finish creating the SQL Server Reporting Services site. )
How can I disable reporting and sharepoint in TFS 2008?
Thank you.
Unlike TFS 2010 and above version, you have to install the SharePoint components for TF2008.
TFS2008 is a very old server version and out of support for a long time. You could use TFS2010 instead, the SharePoint is no longer a prerequisite when you install TFS2010. You can go for TFS2010 Basic Configuration which is the most compact TFS installation possible.
In Basic Configuration, SharePoint and Reporting Integration will not be possible. It will install and configure Source Control, Work Item tracking and Build Services only.
Highly recommend you to move to a newly versioned TFS server. If you insist on using TFS2008, you could try to troubleshoot the configuration of SQL Server Reporting Services. Details please refer this thread in MSDN: SQL Server Reporting Services is not configured correctly
About how to remove Sharepoint and Reporting Services from TFS, you could go through this question. However, afraid removing these components, you will still not able to create team project. After all, if it will work, there is no need to be a prerequisite for installing TFS2008.
I have two sql server database at two different locations. Source is developer edition of sql server and destination is web edition of sql server. Can i create ssis package in developer edition, for data transfer from developer to web edition.
Yes*, you can create an SSIS package in the Developer Edition and it will transfer data between the developer edition database and the web edition just fine. It will be a straight data transfer between two SQL Server instances.
That pesky asterisk though, that might be make this a No answer. The Web edition is not licensed for Integration Services. There is the import/export wizard which builds an SSIS package but if you persist it and execute the package, then it will fail as the machine will report it does not have the right components installed. It's certainly nothing you can schedule. You might think that you can make an end-around and run the SSIS package from the development server but that will likely violate your license as the dev license is not supposed to communicate with production systems.
SQL Server 2012
SQL Server 2008R2
SQL Server 2008
Summary
There is no technical restriction preventing an SSIS package from pushing from a developer edition to an web edition but there is likely a legal restriction for doing so.
YMMV, IANAL, consult your licensing agent.
I am trying to find out if it is better to deploy Reporting Services and Sharepoint Server on the same Server or not and what would the reason be for either case. Any help will be greatly appreciated.
The most common reason that Reporting Services is not integrated with SharePoint is licensing restrictions. I am not a licensing expert, but I believe any server on which Reporting Services is installed must have a SQL Server license. Since SQL Server is usually installed on servers other than the SharePoint app servers, this involves extra SQL costs.
SharePoint and SSRS integration allows reports to be stored in a SharePoint library and provides an easier way to store report output (subscriptions) to SharePoint libraries.
For everyone playing with SQL Azure, what are you using for reporting? Do the Visual Studio reports connect seamlessly? What about reporting services?
Reporting Services will still connect and work as normal, BUT there is no SSRS service on the Azure platform. So it means that you will connect (most likely through ADO) from a different data centre (either your own or hosted SSRS) to SQL Azure, meaning that potentially a lot (too much) data has to come down the wire.
SSRS and SSAS for Azure are not officially on the Azure roadmap yet
My recommendation for a very fast, full featured reporting solution is Izenda Reports. It runs on SQL Azure and is designed for OEM integration with other Azure apps. It streams data from an Azure db or from an off-site db. Just give it a connection string and go.
SQL Azure Reporting was just announced at PDC10 (Oct 28, 2010) and a CTP should be available by the end of the year:
Link
We have at least one customer using ActiveReports with SQL Azure. Just connect with the normal SQL provider for ADO.NET or you can use unbound mode with ActiveReports.