Hello,
This question straddles the Oracle and ASP.NET worlds -- I hope this is the right place for it:
I'm working on a legacy ASP.NET 2.0 website that uses an old Oracle database on the backend. There is also an admin console wepapp which services the main website, but is a seperate application, not an Admin subfolder.
The Oracle database has two "schemas", named WEBSITEADMIN and WEBSITEUSER, which have identical tables and stored procedures. Oracle seems to use the word "schema" to refer to groups of tables within a database - i.e. the two schemas seem to actually be distinct and seperate, as when I add columns to a table in the WEBSITEADMIN schema, the additions do
not appear in the same table under the WEBSITEUSER schema.
The main webapp has an <appSettings> key pointing only towards the WEBSITEADMIN schema in the Oracle database, and indeed it appear to read and write only to that schema.
The admin console website, however, has the following in its web.config folder:
Code:
<appSettings>
<add key="connectionString" value="user id=websiteadmin;data source=DATABASE;password=xxxxxx"/>
<add key="DataConnection" value="user id=websiteadmin;data source=DATABASE;password=xxxxxx"/>
<add key="domainName" value="adminsite.company.com"/>
<add key="MachineName" value="mbd01235pd"/>
<add key="Administrator" value="COMPANY\myemail"/>
<add key="AdminAddress" value="[email protected]"/>
<add key="ServerSideViewState" value="true"/>
</appSettings>
<connectionStrings>
<add
name="ConnectionString"
connectionString="Data Source=DATABASE;User ID=WEBSITEUSER;Password=xxxxxxx;Unicode=True"
providerName="System.Data.OracleClient"/>
</connectionStrings>
...so, the admin console webapp has an "appsettings" key referring to the WEBSITEADMIN schema, but the <connectionstrings> tag refers to the WEBSITEUSER scheme... erm.. what the heck?
Any idea why this app would have connections to both schemas if the main website appears to be only displaying data from one of those schemas?
Thanks for any advice.