I am setting up SharePoint 2010 on one machine with SQL Server on a separate box to server as both the data store and serve reporting services (through SSRS/SP Integration).
In the past, I would install the WSS 3.0 for SharePoint 2007 on the SQL Server Box. It appears that there is no existing option for SP 2010. Am I missing something? Thanks.
It is possible, I believe you can specify a Database server when you are configuring the product.
This is probably a good start: http://technet.microsoft.com/en-us/library/ee667264.aspx
There are a number of "buried" articles ( for some reason I couldn't google them) in the Microsoft Sharpoint Documentation Tree:
(since I could not pust multiple links youre stick with this one)
Configuring on Multiple servers - my specific case
Related
I've installed SQL Server 2016 (Standard Edition) on a Windows Server 2016, selecting Integration Services to be installed too. I've also installed SSMS and SSDT from the same installation media.
I am running SSMS as administrator and can connect to the local Database engine.
My user is a Windows and SQL Server admin.
However I cannot connect (explicitly using the server name) or even browse to the local Integration Services?
Receiving the following error.
SSIS not browsable and can't connect
Having already searched for an answer to this problem, many suggest checking that the service is running etc. which can be seen in the Services and SQL Configuration Manager.
Services shown as running
I've also tried turning off the Windows Firewall to establish if that is the cause of the problem but it had no effect.
Anyone got any ideas what might be preventing it from being accessible?
I've had this problem last month. In my case I had to install the 32-bit version of access database engine (on my 64 bit windows).
Sql data tools works with 32-bit
https://www.microsoft.com/en-us/download/details.aspx?id=54920
The later SSMS versions (16.x and 17.x) will only connect to their respective versions SQL 2016 and SQL 2017. Microsoft is planning to retire the older method in favor of the SSISDB, which is more secure.
Link to the official statement from Microsoft (in the note box).
I have had the same problem and the solution was to install the old interface on top of the existing one (SQL Server Management Studio 2016). Here's link to the installation file. After having installed this, I can now connect to the integration services. You will have to set it up of course and give yourself Rights
I just installed MS SQL Server 2012 (Express). I went through the whole install process from SQLManagementStudio_x64_ENU.exe (other things were already installed) with checking all the checkboxes, so I thought I had everything necessary.
When I try to connect to .\sqlexpress, I get a message saying "Cannot connect to .\sqlexpress". See below for message detail, I copied it from another question because mine is in Dutch :-)
Cannot connect to .\sqlexpress
I did some research through my friends Google and Stackoverflow, but none of the solutions work.
1. There is nothing in Database Engine -> Local Server Groups -> Register Local Servers (it says "No local servers of type "Database Engine" were found"
2. I cannot restart the services as I only have one "SQL related" service (SQL Server VSS Writer)
3. There are no services listed in Sql Server Configuration Manager -> SQL Server Services
Does anybody know what's wrong? Please let me know if you need additional details.
Thanks, a SQL Server newbie
The SQLManagementStudio_x64_ENU.exe as the name says only contains SQL Server Management Studio, which is the GUI used to manage servers. It does NOT includes any DB engine or anything else but the client tool, so it's normal that you don't have the service installed.
Look at the downloads at the official download website. The file named SQLEXPRADV_x64_ENU.exe or SQLEXPRADV_x86_ENU.exe are the full installs that includes both the client tools and database engine together. It's normally the best possible download I can think of from all the choices.
If I recall correct the file SQLManagementStudio_x64_ENU.exe only contains the management tools and not the server software. You need to download another file (SQLEXPRADV_x64_ENU.exe if you want the complete package with server and reporting services etc.).
See this page for more information
I assumed that you have completed whole installation process without any error.
It may possible that you have installed it with another instance name and possibly because of that you are getting this message.
Following thing you have to check.
Try to access on Same machine where you have installed SQL Server using Management studio.
Start menu or Search for SQL Server Configuration tool. At that tool you will find SQL server instance. name.
Make sure that your instance is running mode.
Which authentication mode you have choose during installation and take proper step during making connection
If above step will not work then please provide more detail.
You need to Download the SQL Server Express Edition with the Advanced Services option.
ADV - with advanced services (reporting services)
Perhaps this was asked before but I can't find a whole lot on this, so I would appreciate some help.
Our architecture is as follows: Win 7 desktop on a domain with VS 2010. MS Sql server R2 on Win Server 2008 R2 Ent; SharePoint 2007 on Win 2003; SharePoint 2010 on Win 2008 R2 Ent; Visual Sourcesafe on yet another separate Win Server 2008 R2 Ent server. On this server I have just installed TFS and was running Advanced Config Wizard.
As I'm new to TFS all my selected options are based on intuition and perhaps common sense but Reporting Services and SharePoint aren't working. With reporting services after I add my sql server name (and I've tried IP address and dns name) neither the Report Server URL nor Report Manager URL is populated. (Note: What do I need reporting services for anyway?)
So I've opted not to use reporting services, which as I said, I don't know what is the benefit of it.
Next, in the SharePoint configuration, I wanted to use the existing SharePoint farm which is installed on a separate servers. Testing the Site and Administration URLs would throw an error: "The following site could not be accessed. ... Either ... not installed the Team Foundation Server Extensions, or Firewall... "
I suspect it is not the firewall so then the TFS Extensions. Having search that topic as well seems to point back to the TFS's configuration, so I'm a completely at a loss.
Any ideas?
Thanks,
Risho
/posted from a smartphone since employer blocks this site/
Edited: I was looking at this article http://msdn.microsoft.com/library/dd631915.aspx but I don't have the options listed in the step-by-step solution. TFS Admin Console has this: Top tear - server name, below is Application Tear then Proxy Server, build Configuration and Logs. Expanding Application Tear shows Team Project Collections, SharePoint Web Applications, Reporting, and Lab Management.
You have to configure the SharePoint extensions on each SharePoint machine you wish to connect to TFS. Install TFS on whichever SharePoint machine (or both, if you plan to use both). In the configuration wizard, you should have the option to configure SharePoint Extensions. Once done, you should be able to re-run the readiness checks in the Advanced Wizard on your Application Tier machine.
I have a reporting services project with lots of reports developed in SQL server business intelligence development studio that comes with sql server 2008. I want to deploy these reports to a server that has reporting services 2005 only but the deployment is failing. I'm wondering if any one around here has been able to deploy reports developed in business intelligence development studio 2008 to a server running reporting services 2005 only.
If it isn't passible, is there a way of downgrading my report project back to reporting services 2005 so i can be able to deploy my reports?.
Unfortunately this is not currently possible.
The following thread contains a discussion from the MSDN forums pertaining to a similar query. If you read through it, you will discover that an MVP raised this as a development/support request with Mcrosoft.
http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/686cac48-bc14-4978-b7bf-acbc0c90384e/
Is it really that bad?
For going from 2005 -> 2000, you just had to strip a couple of lines of xml out of the rdl file.
Can't you do something similar? Assuming you don't use 08 specific things like Tablix
?
Microsoft, you don't know how huge of a pain in the butt this problem is. And we're left to find out about this incompatibility only after creating reports in VS 2008 and trying to run them on SQL Server 2005.
This is extremely poor product management on Microsoft's part.
I am going to use SSRS to generate report for my website.
Scenario:
I have 2 servers, Application server & Database Server.
I want to have reports(.rdl files) sitting on Application server(IIS) accessing data on SQL server(Database Server)
In order to fulfil these requirement I require to install SQL server 2k5 on my Application server just for having SQL server reporting service. So I am just waisting one of licence of SQL server by installing that on Application server.
Is anyone having any idea how to install only reporting service with SQL server 2k5??
In order to have Reporting Services on your Application server, you would have to use a SQL license. You can install just the Reporting Services section of SQL Server, but it is still technically part of the SQL Server application and requires a license for use on that processor(s).If that is a huge issue, then I would have to recommend keeping the Reporting Services section installed with the rest of the database installation on your Data server.
http://www.microsoft.com/sql/prodinfo/previousversions/rs/howtolicensers.mspx
The server components of SQL Server 2000 Reporting Services include the Report Server and the Report Server Database. The Report Server processes and renders reports, and handles scheduled events and report delivery. The Report Server Database stores report definitions, report metadata, subscription information, and so on. Each Report Server requires either a local or remote connection to a Report Server Database. To use any of these components, each computer on which the Report Server and the Report Server Database are installed must have a valid SQL Server 2000 license.
You could install SQL Server Express on the application server.
It's free, and there's an edition which comes with Reporting Services.
In comparison with the "real" editions, SQL Server Express Edition is limited concerning how much CPU and RAM it can use, but it will probably be fast enough to run your reports.
blatantly incorrect. You do not need a SQL Server license to use SQL Server Reporting Services, you can use SQL Server Express edition. I've use SQL Server Express Edition in addition to linked servers-- to query stuff on -ANY- database server. And it works great.
SSRS is a great platform, I Just hate it when people run around saying that you NEED a license to use it. I'll bet that guy works for Oracle corp!
You do have an alternative. You can embed reports directly into your code projects in .Net. In this case the report runs through the Microsoft.Reporting.WinForms and Microsoft.Reporting.WebForms namespaces, ReportViewer object. Each report will have a ".rdlc" extension instead of ".rdl", though the two files types are actually equivalent. There is an ASP.Net version of the ReportViewer that allows you to integrate these reports into your website. You just need to drag the ReportViewer control from the toolbox into your website to configure it. For more information, see the MSDN overview of ReportViewer Controls.
If you dont want to use a whole license you can always use reportviewer. Just so I dont put too much answer out here, the big site for this is gotreportviewer.com.
The reportviewer control does the work of the reporting services server when it comes to the generation of reports. RDL files are like xml files and dont do much until they are interpreted. If you embed the reportviewer in your application on the web the work will be done on the user side. It is simialar to microsofts xps format, it has to be interpreted.
If you don't want to create an application for your reports the new version of sql2008 with advanced controls allows you to install a free version of reporting services. It doesnt have all of the goodies but it works for simple deployments.