Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Is a Named Pipes connection necessaryIs a Named Pipes connection necessary
Previous
 
Next
New Post
2/11/2008 1:08 PM
 

I have run my DNN sites successfully for a long time from databases on Servergrid.com -- but there are occasional outages, and their techs say the problem is that DNN is using Named Pipes to connect to the SQL server. They say it should use a TCP/IP connection instead for optimal performance.

Is it even possible to make this change in DNN and access the databases remotely? How would I do it, and would it change the performance of DNN?

Thanks in advance!

 
New Post
2/11/2008 4:46 PM
 

I don't believe it's necessary at all. I think that the connection as setup will connect on what ever is available, although I could be wrong. If you want to require that it use tcp/ip, then add Network Library=DBMSSOCN into the connection string and you may have to specify the port the the tcp/ip protocol is listening to for sql, the default is 1433.


A sample connection string would be:

Server=192.168.1.1,1433;Database=DNNDBName;uid=sa;pwd=sa;Network Library=DBMSSOCN;

If you specify DBNMPNTW for the Network Library then that is Named Pipes and you wouldn't need the ,1433 added to the IP.

Again, I'm not sure what is picked for the network library if both are configured for SQL Server, but if you specify as above then at least there is no guessing.

Hope this helps

 




Richard Edwards
www.dnnstuff.com
Quality DotNetNuke Modules, Unrivaled Support (since 2004)
All 6 modules for as low as $49
 
New Post
2/11/2008 10:24 PM
 

Thanks -- will give this a try.

 
New Post
2/12/2008 1:40 PM
 

You don't need the 1433 port number as SQL listens on that by default.  If you set SQL to a non-stndard port then you need that port number.

Jeff

 
New Post
7/13/2008 11:28 PM
 

Thank you for this -- I finally had to implement this because of a connection error, and it seems to work.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Is a Named Pipes connection necessaryIs a Named Pipes connection necessary


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.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out