incubator-stonehenge-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Dewey (JIRA)" <j...@apache.org>
Subject [jira] Commented: (STONEHENGE-79) DotNet Config Service doesn't support SQLExpress
Date Fri, 10 Jul 2009 15:51:14 GMT

    [ https://issues.apache.org/jira/browse/STONEHENGE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729685#action_12729685
] 

Ben Dewey commented on STONEHENGE-79:
-------------------------------------

I was thinking a little about this last night, and we may be able to fix this without modifying
the Config Service contract.

If we add an extra column (InstanceName nullable) to the DBConfig table, we can modify the
SQL query in .NET to return the HostName as a concatenation of the address + "\" + instance
name (if present).

Is this too much hackery?  thoughts?  Should we just change the Config Contract?

> DotNet Config Service doesn't support SQLExpress
> ------------------------------------------------
>
>                 Key: STONEHENGE-79
>                 URL: https://issues.apache.org/jira/browse/STONEHENGE-79
>             Project: Stonehenge
>          Issue Type: Bug
>            Reporter: Ben Dewey
>             Fix For: M2
>
>
> The new STONEHENGE-67 Config patch doesn't support SQLExpress as a named instance.  The
config service would need to be modified to support a named instance of the database.
> The current work-around is to enable TCP/IP on the SQLExpress instance using port 1433.
 See the PHP/WSAS Installation guide for more information.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message