[
https://issues.jboss.org/browse/TEIID-5386?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-5386.
-----------------------------------
Fix Version/s: 11.0
Resolution: Done
Added a new method to the metadata processor to alter the procedure name in source and
added an override for sql server.
Wrong procedure import from MS SQL Server
-----------------------------------------
Key: TEIID-5386
URL:
https://issues.jboss.org/browse/TEIID-5386
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.12.13.6_4
Reporter: Jan Martiska
Assignee: Steven Hawkins
Fix For: 11.0
When using automatic procedure import from SQL Server (I used 2016) with a model like
this:
{noformat}
<model name="mymodel">
<property name="importer.useFullSchemaName"
value="false"/>
<property name="importer.UseQualifiedName" value="false"
/>
<property name="importer.procedureNamePattern"
value="echo%"/>
<property name="importer.importProcedures" value="true"
/>
<source connection-jndi-name="java:/mssql2016"
name="mySource" translator-name="sqlserver" />
</model>
{noformat}
There is a procedure named {{echo}} in SQL server. It is imported into the VDB as
{{"mymodel"."echo;1"}} (not sure why the ;1). When I afterwards try to
execute it using
{noformat}
EXEC "mymodel"."echo;1"();
{noformat}, I will get this exception from SQL server which suggests that Teiid mapped
the procedure to the wrong name in the source database:
{noformat}
com.microsoft.sqlserver.jdbc.SQLServerException: Could not find stored procedure
'echo;1'.
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)