[
https://issues.apache.org/jira/browse/STONEHENGE-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Dewey closed STONEHENGE-23.
-------------------------------
Resolution: Invalid
Fix Version/s: (was: M1)
Each instance in SQL Server gets its own port number. As long as the port
number for the SQLExpress instance is accurate it should work okay.
> There is not property available for an Instance Name in WSAS db-properties.
> ---------------------------------------------------------------------------
>
> Key: STONEHENGE-23
> URL: https://issues.apache.org/jira/browse/STONEHENGE-23
> Project: Stonehenge
> Issue Type: Bug
> Components: WSAS_BS
> Reporter: Ben Dewey
> Assignee: S.Uthaiyashankar
> Priority: Minor
>
> A ran into another anomaly with the Named Instance of SQL Express. The jtds
> faq had this link that helped me find a solution
> http://jtds.sourceforge.net/faq.html#instanceName. What I did is very much
> an injection hack (notice the db property), I think we should Add a JIRA
> ticket for this optional parameter.
> org.wso2.stocktrader.mssql.MSSQLDAOFactory.host=localhost
> org.wso2.stocktrader.mssql.MSSQLDAOFactory.port=1433
> org.wso2.stocktrader.mssql.MSSQLDAOFactory.db=StockTraderDB;Instance=SQLExpress
> org.wso2.stocktrader.mssql.MSSQLDAOFactory.user=trade
> org.wso2.stocktrader.mssql.MSSQLDAOFactory.password=trade
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
