...

Dear DotNetNuke 8.0.3 Experts,

Does DNN always and only use the "SiteSqlServer" connection string?

That is, Is the following still true for 8.0.3 in DotNetNuke..

http://www.dnnsoftware.com/wiki/connection-string

"

The connectionString node in web.config is where asp.net retrieves connection strings from. DotNetNuke ships with the files for installation on sql server, and by default a connection string of SiteSqlServer is used to determine what connection string to use.

This is referenced in 2 additional locations:

add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="SiteSqlServer" enablePasswordRetrieval="true" enablePasswordReset="true" requiresQuestionAndAnswer="false" minRequiredPasswordLength="7" minRequiredNonalphanumericCharacters="0" requiresUniqueEmail="false" passwordFormat="Encrypted" applicationName="DotNetNuke" description="Stores and retrieves membership data from the local Microsoft SQL Server database"

add name="SqlDataProvider" type="DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider" connectionStringName="SiteSqlServer" upgradeConnectionString="" providerPath="~\Providers\DataProviders\SqlDataProvider\" objectQualifier="" databaseOwner="dbo"

"

...or not?

Please advise.

Thanks.

-- Mark Kamoski

...

Joe --

I appreciate the follow-up.

I check my DotNetNuke site, appSettings and found no connection string there.


<appSettings>
<add key="InstallTemplate" value="DotNetNuke.install.config" />
<add key="AutoUpgrade" value="true" />
<add key="UseInstallWizard" value="true" />
<add key="InstallMemberRole" value="true" />
<add key="ShowMissingKeys" value="false" />
<add key="EnableCachePersistence" value="false" />
<add key="HostHeader" value="" />
<!--Host Header to remove from URL so "www.mydomain.com/johndoe/Default.aspx" is treated as "www.mydomain.com/Default.aspx".-->
<add key="RemoveAngleBrackets" value="false" />
<!--optionally strip angle brackets on public login and registration screens.-->
<add key="PersistentCookieTimeout" value="0" />
<!--use as persistent cookie expiration. Value is in minutes, and only active if a non-zero figure-->
<!--set UsePortNumber to true to preserve the port number if you're using a port number other than 80 (the standard).
<add key="UsePortNumber" value="true" /> -->
<!-- Services Framework Tracing is primarily useful for developing and debugging -->
<add key="EnableServicesFrameworkTracing" value="false" />
<add key="UpdateServiceUrl" value="http://update.dotnetnuke.com" />
<add key="Telerik.Web.UI.ScriptFolders" value="~/Portals;" />
<add key="Telerik.Web.SkinsAssembly" value="Telerik.Web.UI.Skins, Version=2013.2.717.40, Culture=neutral, PublicKeyToken=121fae78165ba3d4" />
<add key="InstallationDate" value="7/19/2016" />
<add key="PreserveLoginUrl" value="true" />
<add key="loginUrl" value="~/Login.aspx" />
<add key="DefaultDevicesDatabase" value="DesktopModules\DevicePreviewManagement\Resources\defaultDevices.xml" />
<add key="InstallVersion" value="08.00.03" />


Thanks.

-- Mark Kamoski

You can use any number of connection strings and you can call them based upon the name you give them.

I have hit mssql, oracle, db2, postgres, etc DBs from within DNN. This is one of many reasons I prefer dnn over other CMS solutions.