DDevelopment & Design

Accessing Microsoft SQL Server from Oracle

Once we had a need of accessing a table on an Microsoft SQL Server database from an Oracle database. Thus we had to install Oracle Transparent Server on the computer hosting SQL Server. Oracle Transparent Services is a kind of adapter for non-Oracle servers and allows access to it through database link. During the instalation of Oracle Transparent Server you have to choose modules dedicated to particular databases. The modules can translate calls to some functions and allows to call a T-SQL stored procedure from Oracle.

Oracle Transparent Server can be downloaded from 

http://www.oracle.com/technology/software/products/database/oracle10g/htdocs/10201winsoft.html  Description of its solution can be found here: http://oracle-apps-dba.blogspot.com/2008/04/oracle-transparent-gateways-general.html Instalation instructions are here… : http://oracle-apps-dba.blogspot.com/2008/04/oracle-transparent-gateway-for-ms-sql_16.html and here: http://forums.oracle.com/forums/thread.jspa?messageID=2720049&#2720049 However, most of the configurations files were located in the directory network\admin and not in tg4msql\admin as described I found that access to the data is slow – the simplest queries last for 4 seconds. However, increasing the efficiency is another topic.

— Previous article

<!--:en-->Solving package dependency problem using synonyms<!--:-->

Next article —

<!--:en-->Subtle feature of CONNECT BY<!--:-->

You May Also Like
DDevelopment & Design

Writing JAXB in Groovy

Suppose you want write a jaxb class in groovy. Why? Because you do not have to write these all getters, setters and other methods. You only have to write your fields down.@XmlRootElement@HashCodeAndEquals@ToStringclass Person { String firstName String ...
DDevelopment & Design

New HTTP Logger Grails plugin

I've wrote a new Grails plugin - httplogger. It logs:

  • request information (url, headers, cookies, method, body),
  • grails dispatch information (controller, action, parameters),
  • response information (elapsed time and body).

It is mostly useful for logging your REST traffic. Full HTTP web pages can be huge to log and generally waste your space. I suggest to map all of your REST controllers with the same path in UrlMappings, e.g. /rest/ and configure this plugin with this path.

Here is some simple output just to give you a taste of it.

17:16:00,331 INFO  filters.LogRawRequestInfoFilter  - 17:16:00,340 INFO  filters.LogRawRequestInfoFilter  - 17:16:00,342 INFO  filters.LogGrailsUrlsInfoFilter  - 17:16:00,731 INFO  filters.LogOutputResponseFilter  - >> #1 returned 200, took 405 ms.
17:16:00,745 INFO  filters.LogOutputResponseFilter  - >> #1 responded with '{count:0}'
17:18:55,799 INFO  filters.LogRawRequestInfoFilter  - 17:18:55,799 INFO  filters.LogRawRequestInfoFilter  - 17:18:55,800 INFO  filters.LogRawRequestInfoFilter  - 17:18:55,801 INFO  filters.LogOutputResponseFilter  - >> #2 returned 404, took 3 ms.
17:18:55,802 INFO  filters.LogOutputResponseFilter  - >> #2 responded with ''

Official plugin information can be found on Grails plugins website here: http://grails.org/plugins/httplogger or you can browse code on github: TouK/grails-httplogger.