I have oracle database named CRMS and using SQL developer to run queries.
I need to make reports using CRMS oracle as my datasourse.
I am using SSRS 13.0
Visual studio 14.0
MS .NET version 4.7
SQL developer 4.1.5
Using Microsoft OLE DB provider for Oracle
not sure how to connect to Oracle database. please guide me
You would probably need Oracle Client Components installed on your local machine (where you have SSRS installed) inorder to use the Connection Provider for an Oracle Database.
You might want to take a look at the link below:
http://www.oracle.com/technetwork/database/windows/downloads/index-090165.html
Related
Im using SSIS package which created SQL Sever data tools 2017 to load data from Oracle to SQL Server. I have setup the Oracle Client 32bit in SQL Sever and configure tnsnames.ora correctly. In OLE DB data source at Data Flow Task successfully connected to Orcal Database in SSIS. I have try simple query out some columns using SQL Command in OLE DB Source.
But Im getting following error when previewing the data,provider cannot derive parameter information and setparameterinfo has not been called. (Microsoft OLE DB Provider for Oracle).
I have tested packages which created in SQL data tools 2010,2012,2014 and those are worked fine and not generated any errors. But for 2015 and 2017 SQL Data tool packages above mentioned error is generating. So could you guide me how to fix this in SQL Data Tools 2017 version.
I am new to IBM Cognos and I am using Cognos 10 trail version.
I did some of reports using DB2 as a data source. Now I trying to use SAP as a data source and I surfed the web and have seen the IBM cognos guide and in that I went through the steps to connect with SAP BW and when I am doing same using my framework manager I got stuck at 8 step, please have a look into the following link
http://www-01.ibm.com/support/knowledgecenter/SSVRFT_1.1.0/com.ibm.swg.ba.cognos.dyn_query.10.2.1.doc/t_dqm_crt_proj_sap_bw.html
I only have the following drivers while I am trying to create Data source in it,
Drivers in Cognos:
IBM DB2, IBM Informix Dynamic server, Microsoft SQL server(ODBC), Microsoft SQL server(OLE BC),Microsoft SQL server( 2005 Native client), Microsoft SQL server(2008 Native Client), Microsoft SQL server(2012 Native Client), Microsoft analysis services 2008(ODBO), Microsoft analysis services 2012(ODBO), Netezza, ODBC, JDBC, Oracle, Progress OpenEdge(ODBC), IBM Red Brick(ODBC), Sysbase Adaptive Server Enterprise(CT-Lib), Sysbase Adaptive Server Enterprise(CT-15),
Teradata, IBM Cognos TM1)
In the 8 step of the above link they tell simply that use type SAP BW as a driver but in my framework manager I did not have the same driver as they said that in the above documentation link. I stuck there, I did not find any solution please tell me solution if any one knows.
Thank you in advance.
Why not just add the data source to your Cognos BI Server via. Cognos Administration?
It will then appear in FM as an available data source.
I'm facing following issue using Visual Studio 2012 when I'm trying to connect with MS SQL Server 2000 (in Data Connections window):
Strange is that it's actually getting list of databases when I'm using Microsoft SQL Server (SqlClient) as a data source.
Is there any way to connect VS 2012 and SQL Server 2000? Should I use different driver/provider? Is it possible at all to use those technologies together?
I figured out the solution. .NET Framework Data Provder for OLE DB -> Microsoft OLE DB Provider for SQL must be used.
I am new to remote database connections and I want to setup a very simple single table Delphi XE6 project to view a table ('CUSTOMERS') that I've just created in a small Windows Azure SQL database. I plan to use this access for both VCL code and FireMonkey on Android later. I can see and edit the table using the Azure dashboard.
To test the VCL code, i've dropped an FDConnection on my form with a TFDTable, TDatasource and TDBGrid. I've seen example connection info here but this refers to the MSSQL driver which I presume that I don't have because I'm using XE6 Professional. So I've used a TFDPhysSQLiteDriverLink and tried using the SQLite driver with connection params:
User_Name=user#56ss8sbeq
Database=tcp:56ss8sbeq.database.windows.net
Password=1234
Encrypt=Yes
MetaDefCatalog=DB123SQL
DriverID=SQLite
My table is CUSTOMERS and this is in the table name property of the TFDTable. When I run the project I get no connection errors but I do get "[FireDAC][Phys][SQLite] ERROR# no such table CUSTOMERS". Does this indicate that I'm being stupid in trying to use that driver? If so, do I have any way of accessing my DB with FireDAC?
AFAIK Windows Azure SQL database is a MS SQL database hosted on the cloud.
You need an MS SQL driver. You just can not link to MS SQL with a SQLite3 driver!
Upgrade your XE6 edition by buying the FireDAC bundle, or switch to other libraries, like ADO Components, which are part of XE6 Professional if I remember well.
Searched the net in and out and could not find proper info on that, we have a legacy setup that uses Delphi 7 and BDE to connect to SQL Server 2005.
Now we are planning to migrate to SQL Server 2012, what are the chances that it might work or not?
If you are using the SQL Links MSSQL driver then targeting SQL Server 2012 will not be possible. The only way that I have been able to use SQL Links with anything newer than SQL Server 2000 is to keep the database compatibility level set to "SQL Server 2000 (80)". This is not possible in SQL Server 2012. The oldest compatibility level available in this version is "SQL Server 2005 (90)".
SQL Links will send invalid SQL to the server, such as the "*=" syntax for an outer join. Databases set for SQL Server 2005 and above will not accept this syntax.
We've been using Delphi 7 with SQL Server 2012 without significant issue via the Delphi 7 ADO data control components (e.g. TAdoQuery, TAdoCommand). Stored procedures also work fine, and functions can be called via ADO commands objects (TAdoCommand).
We use the SQL Server Native Client 11.0 ODBC driver that comes with SQL Server 2012. Delphi just treats it as another ODBC data interface. Superficially it looks a lot like using MS Access with Delphi 7 (via ADO components and Access OLE driver). No issue with any of the Service Pack(s?) for SQL Server 2012 either. (Sorry, I don't remember exactly what SP's are released for 2012, but we've had no differences w/ or w/o these SP's, and we tested for it).
Most of the development was done on Windows 7 64-bit OS's, and executed on same as well as Windows Server 2008 and 2008R2, both 64-bit. No special settings were required to execute Delphi-compiled executables (which are all 32-bit, obviously).
If you use ODBC "aliases", be sure to use the 32-bit ODBC DSNs, not the 64-bit ODBC DSNs. The 64-bit ODBC Administrator is the one in the Control Panel\Administrative Tools for 64-bit Windows - don't use it here. Use the 32-bit ODBC Administrator, in Windows' SysWOW64: C:\Windows\SysWOW64\odbcad32.exe. The 64-bit ODBC DSNs live in a separate space from the 32-bit DSNs. Delphi 7 is a 32-bit application and won't have access to the 64-bit DSNs (different API I'm guessing).
We may also have had an issue with comments in SQL statements. I think the line comments ("--") didn't work, but multi-line comments worked ("/.../").
Note that while the BDE is preserved by Corel (distributed to this day as the Paradox Runtime; the engine is frozen, however, and does have some issues in modern Windows OS's), it's not needed to access SQL Server data. We use the ODBC aliases directly through the Windows ODBC API (we wrote wrappers in Delphi to make this trivial). However, you can still use the BDE as an interface to these ODBC DSN aliases. If you don't use aliases at all (and don't include any references to DbTables.pas in the source code) you shouldn't need the BDE at all. DbTables.pas initialises the BDE always when it initialises the global Sessions variable in its INTIALIZATION block. You can see this in the bottom of the DbTables.pas source code unit. Without this unit, the BDE isn't initialised or used. (Which also means you cannot use TTable or TQuery components, but those are only for Paradox data; the ADO components like TAdoTable (don't use it unless you want to load the entire data table into memory!), TAdoQuery or TAdoCommand are entirely independent.
Another trick is to use MS Access databases and linked tables to interface between SQL Server and Paradox data tables, if you still need to use BDE-native (i.e. Paradox) tables. But sometimes Access and the BDE don't play well together.
The migration is long done, I'm sure, but in case others are searching for the same answer. Legacy software has a habit of living on...
We've had success using BDE with SQL Server 2008R2. No special config.
Edit: I'm also having initial success on SQL Server 2014 today. Limited testing, but so far so good!
Greg