How can I connect SQL Developer to an Exasol DB? Is this possible?
I tried to download the Exasol driver but is not recognized by the SQL Developer.
No, that's not supported. SQL Developer's 3rd party JDBC connectivity is provided for one use case - migrations to Oracle Database.
There's no support on that for Exasol DB, so there's no connectivity support provided.
If you want a generic jdbc db client, that's not Oracle SQL Developer.
Related
Is it possible to access a table in an Oracle 10g database using DB from an Oracle 19c database?
Per MOS Doc ID 207303.1, connections between those versions are not supported. The oldest version that 19c can connect with is 11.2. Based on other comments I have seen, some people have gotten it to work with 10g, but it should not be used in a production environment without full support, as results are not guaranteed or predictable.
I am trying to connect to database from Integration Service project from Microsoft visual studio. How do I create a database from SQL SERVER 2012.
SQL Server Management Studio (SSMS) will allow you to create a database and tables through its graphical user interface. However, I'm guessing what you're looking for is actually an SSIS Connection Manager to an existing database. Look at the connection managers in SSIS, create a new one, and fill in the boxes. What you're doing is building a database connection string. You will need credentials (username and password, or a Windows authenticated user) to connect to the database. Also, you may need to spend some time reading the documentation.
Hey guys i am wondering how is it possible to either sync pervasive sql to another database or directly connect it to ruby on rails?
My accounting system uses pervasive sql and at the moment i am trying to use an ODBC connection from the database to my ruby application.
I am currently working with this website:
http://odbc-rails.rubyforge.org/
Has anyone made this happen before because so far i am getting really confused with how to do the connection and get data from the remote database.
I realize this is a bit late, but on windows based systems you can use OLE DB to connect to pervasive by doing something like this:
require 'win32ole'
conn = WIN32OLE.new('ADODB.Connection')
conn.Open = ('Provider=PervasiveOLEDB;Data Source=DEMODATA;')
recordset = ('Select * from some_table',conn)
data = recordset.GetRows.transpose
recordset.Close
There is no adapter for ole db and active record though. It might work by just setting the adapter to odbc, but i'm not positive.
If you can setup and odbc dsn you can also connect to pervasive the way described here.
If you can use JRuby, you have access to JDBC connections as described here.
We have a requirement where a Grails application is required to connect to an external SQL Server 2005 (i.e. client's database server via a linked server). Our grails application will have its own SQL Server database instance for user authentication (so will mostly have only one domain class) and then it needs to connect to the external SQL Server database to fetch (only SELECT permission provided) data from 10 or 15 tables (out of 250 tables available) and show it the grails application.
I would like to know would be the best approach to take in this scenario.
Thank You.
Jay Chandran.
You can use the http://grails.org/plugin/datasources plugin and configure the external server as a read-only datasource to ensure that only reads are performed. If you don't want to map domain classes on that server you can use groovy.sql.Sql to execute SQL queries.
At the MSDN website it says, "Connecting to SQL Azure by using OLE DB is not supported."
There are other places on the web where folks report that it works fine for them after tweaking the server name in the connection string, such as here and here. Even SQL Server's Analysis Services uses OLE DB to connect to SQL Azure!
I develop a native/unmanaged application in Delphi that connects to SQL Server using ADO through the OLE DB provider for SQL Server. I'm considering adding SQL Azure support. It would be really helpful if I could reuse the majority of my code without not too much change. I probably wouldn't consider going this direction otherwise.
It would be helpful if Microsoft were more clear on why "OLE DB is not supported". If there are certain limitations within the use of OLE DB, what are they? Maybe I can work around them, or maybe it wouldn't affect me.
Microsoft also mentions that ODBC is supported. So could I use the "OLE DB provider to ODBC" and connect this way? Or is any combination that includes OLE DB "not supported"?
You can use it, however it has not been thoroughly tested for all cases. Essentially, it should work for most things, but there might be a few edge cases where it won't work. Until we document those cases, it remains unsupported. That being said, if you were to use and run into errors, we would love to know about it and prioritize that to be fixed.
Vote for the OleDB support for Azure here:
http://www.mygreatwindowsazureidea.com/forums/34685-sql-azure-feature-voting/suggestions/407269-ole-db-provider-for-connecting-to-sql-azure?ref=title
You can use ADO using the SQL Native Client although this information is hard to find you can read about it here http://msdn.microsoft.com/en-us/library/ms130978(SQL.110).aspx and here http://msdn.microsoft.com/en-us/library/ms131035(SQL.110).aspx.
In the connection string instead of using Provider=SQLOLEDB; we can use Provider=SQLNCLI10;. Also it is recommended to use DataTypeCompatibility=80;. So a SQL Native Client supported connection string would look like this:
"Provider=SQLNCLI10;Server=tcp:MyServerName.database.windows.net;Database=AdventureWorks2008R2;Uid=MyUserName#MyServerName;Pwd=MyPa$$w0rd;Encrypt=Yes;DataTypeCompatibility=80;"
You can also add "MARS Connection=True;" to the connection string for multiple recordsets.