Our organization has a Windows server running SQL Server Reporting Services (SSRS). We use SSRS to build reports that access an Oracle database. We were able to get SSRS to connect to our Oracle database by installing Oracle Data Access Components (ODAC) for Windows on our server. We installed the Xcopy versions - both 32-bit and 64-bit (don't know if we needed to do both; SSRS used to only accept 32-bit drivers). We were able to successfully set up a data source in SSRS that connected to the Oracle database.
However, we write our reports on development machines using SQL Server Report Builder 3.0. When building a report that uses a shared data source on the server - the one that accesses our Oracle database, we get the error
The selected data extension ORACLE is not installed or cannot be loaded...
What do we need to do to be able to write reports from our development machines that use a shared data source to our Oracle database?
You need to install ODAC on your development machines as well. Even though you are configuring your report to use a shared data source on the server, Report Builder 3.0 will use connection drivers on the local machine to build and preview report data.
Report Builder 3.0 still seems to be a 32-bit application (as of 6/3/2016), so you only need to install 32-bit ODAC package.
Related
I've installed SQL Server 2012, after I've installed all features including report services. I go to Report Manager link and wanted to add New Data Source, but in Data Source Types there is only Microsoft SQL Server and I want to add Oracle Data Source.
Other way I easily connected to Oracle Data Source in Business Inteligence Studio, but I can't deploy Report file (.rdl) to my report manager because it gives me an error message:
An attempt has been made to use a data extension 'ORACLE' that is either not registered for this report server or is not supported in this edition of Reporting Services.
Does anyone have any idea how to fix this?
You should install the .NET Framework Data Provider for Oracle on the server hosting the SSRS instance to be able to target an Oracle database.
Here is a link to download the latest version on Oracle.
Remarks
Before you can connect an Oracle data source, the system administrator must have installed the version of the .NET Data
Provider for Oracle that supports retrieving data from the Oracle
database. This data provider must be installed on the same computer as
Report Builder and also on the report server.
Source: Oracle Connection Type (SSRS)
Useful resources:
Using the .NET Framework Data Provider for Oracle
How to use Reporting Services to configure and to access an Oracle data source
If you are using the Express edition of SQL Server, then Oracle Data Sources are not supported:
Analysis Services, Oracle, XML, SAP, SQL Server Integration Services
(SSIS), OLE DB, and ODBC data sources are not supported.
Source: Features Supported by Reporting Services in SQL Server Express
It applies to SSRS 2012 Express as well, as stated in this post.
SSIS SP Connection using OData connector.
I was able to connect to Sharepoint site fine and was able to see the data thru preview and all.. but when i execute the task i get below error.
[OData Source [2]] Error: The OData Source was unable to process the data. Object reference not set to an instance of an object.
Note: Visual Studio 2012 with BI template not sure how different is that from SSDT 2012. When i go try to open SSDT 2012, i get VS 2010 shell, that's why i use VS 2012 with Business Intelligence template thinking that maybe same as SSDT 2012. If this has to do something with error message i get above.
Task:
OData Source with SP connection information
OLE DB Destination.
Let me know your thoughts!!
I would try setting the Project Properties / Debugging / Run64BitRuntime to False.
This will run your debug executions (e.g. Execute Task, Execute Package using Visual Studio) using the 32-bit version of the OData connector. Visual Studio (which you have used to design the task and preview the data) is a 32-bit app, so it will be using the 32-bit versions of the OData connector.
The same challenge applies to almost every connector or driver that has to be separately installed for SSIS. Typically they come in 32-bit and 64-bit flavors, with independent setup, configuration and sometimes bugs.
While I recognize that 64-bit components will generally deliver higher throughput, I have resigned to always install and use the 32-bit connectors and drivers. I find this minimizes wasted time and frustration trying to debug and resolve these issues on multiple developer machines and servers.
I have multiple reports that have been created over the years and anytime a RDLC file is opened in the VS2010, it is asking for an upgrade. I have seen many posts about changing the .config file, but these files are not using config files since they are application based. I have Microsoft.ReportViewer.Winforms, .Common, .ProcessingObjectModel and, .WebForms 9.0 and 8.0 installed on the lab machine.
After upgrading a report and trying to run it on the lab machine ( ms server 2008) I am returned an error of: "The report definition has an invalid target namespace 'http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition' which cannot be upgraded.
Does Report Viewer 2010 Redistributable Package fix this issue? I cannot find a distinct answer. If not, is there another workaround without changing server modes from local to server?
You should really be opening those using the SQL Server Business Intelligence Development Studio (BIDS), which can be found under the Microsoft SQL Server 2008R2 folder on the Programs menu.
I have an application written in MS ACCESS 2007 using VBA, connecting to an SQL Server at the back end. Both Access and SQL Server are running locally.
My machine runs Access 2010 and MS SQL Server Express 2008 R2 (both 32-bit, on WinXP) with no problem.
I have another machine, Win7 64-bit, running both Access 2010 and SQL Server 2008 (NOT R2) 64-bit.
When I run the Access application on the 64-bit machine, I have a drop down box to select the SQL Server which holds the various databases. When I select the server, after a few seconds I get an error:
Run-time error '-2147024703 (800700c1)':
Automation error %1 is not a valid Win32 application.
When I select the Debug option, the yellow arrow points to:
Set oServer = New SQLDMO.SQLServer
The next line is:
oServer.Connect ServerName, strSQLUser, strSQLPwd
In the watch list, I can see that ServerName, strSQLUser, and strSQLPwd hold the right values to access the SQL Server. I've tested these in sqlcmd and successfully was able to query tables.
Can anyone please help me out on this one? I'm not sure what to do next.
Seems like you've got registered a 32-bit SQLDMO on your system that is being used for connection to the 64-bit instance. Check your registry / file system for SQLDMO.dll versions and register the correct one.
Also check MSDN "Installing SQL-DMO" because SQLDMO was scheduled for remove after SQL Server 2008 R2:
Avoid using this feature in new development work, and plan to modify applications that currently use this feature.
SQL Server Database Management Objects (SQL-DMO) has been removed from SQL Server 2008 R2 Express and the SQL Server 2008 R2 Feature Pack. SQL-DMO also does not support Database Engine features introduced after SQL Server 2000. We recommend that you modify applications that currently use this feature as soon as possible. If you must support SQL-DMO, install the Backward Compatibility Components from the SQL Server 2008 Feature Pack from the Microsoft Download Center. Do not use SQL-DMO in new development work; use SQL Server Management Objects (SMO) instead. You can obtain the SMO documentation by installing SQL Server 2008 R2 Books Online.
Thanks for this.
I looked to find SQLDMO.DLL 64-bit version, but although using the Backwards Comparability package for x64, installing using the MSI did not do the job.
I had to manually extract the files and place the correct version (which is ~2MB larger than the x86 version as an indication to knowing which one is the x64) and then run 'regsvr32 sqldmo.dll ' in the command line (very important: need to run cmd as Administrator for this to succeed).
After the module has been registered, my Access front end run great.
I'm working on a school project desktop application in c# using Visual Studio 2010 (.NET 4.0) and the application uses a SQL Server 2008 database that's running on a SQL Server instance on the development machine I'm working with.
My question is how do I package up the database with the c# project so that the application works no matter what machine I'm using it on regardless of whether the machine it's installed on has SQL Server installed or not?
Thank you.
use SQL Server Compact Edition (SQL CE)
If it's not a web application and it's making a direct use of the database, how is it going to work without an instance of SQL server running?
I'd make an .msi for the application and I'd write a SQL script for installing the database and populating it with the data.
You can use SQLServer tools for scripting the tables and the data.