Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Does DNN always and only use the "SiteSqlServer" connection string?Does DNN always and only use the "SiteSqlServer" connection string?
Previous
 
Next
New Post
4/25/2018 1:11 PM
 
...

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

...
 
New Post
4/26/2018 8:50 PM
 
I believe that DNN 8 still uses the TWO connection strings that you'll find in the web.config. One is in the connectionStrings section and the other is in appSettings. Both should be set to the same values.

The appSettings connection string is there for compatibility with older modules. It has been removed in DNN 9.



Joe Craig
Patapsco Research Group, Ellicott City, MD
DotNetNuke Development and Services (http://patapscorg.com)
 
New Post
4/27/2018 10:12 AM
 
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
 
New Post
4/27/2018 1:16 PM
Accepted Answer 
Mark,

I guess the question is whether or not you are seeing any errors/problems related to database access. If you aren't, I'd assume that your site is not using modules that require the second connection string. In other words, you are fine.

If you are experiencing problems, then you'll want to add the second connection string to web.config and see if that fixes things. To do this, get a copy of the install package for the version of DNN you are using. As it's a zip file, open it up and take a look at the included web.config file. Copy the needed line from there to your web.config.




Joe Craig
Patapsco Research Group, Ellicott City, MD
DotNetNuke Development and Services (http://patapscorg.com)
 
New Post
5/7/2018 8:13 PM
 

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.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Does DNN always and only use the "SiteSqlServer" connection string?Does DNN always and only use the "SiteSqlServer" connection string?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  

What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out