<div>
Hi,<br />
<br />
Follow this steps to configure the SQL server for remote connections:<br />
<a href="http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/" rel="ugc">http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/</a><br />
<br />
For help in connection strings:<br />
<a href="http://www.connectionstrings.com/sql-server-2005" rel="ugc">http://www.connectionstrings.com/sql-server-2005</a>
</div>


Hi,

Follow this steps to configure the SQL server for remote connections:
http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/ [http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/]

For help in connection strings:
http://www.connectionstrings.com/sql-server-2005 [http://www.connectionstrings.com/sql-server-2005]

<div>
Classic &quot;Client Server&quot;.<br />

</div>


<div>
<div class="content wysiwyg-content">
Currently we have a C# .net windows application that uses a local desktop instance of SQL Server. &nbsp;We wanted to know the challenges of changing this model to using a single instance of a SQL Server on a network.<br />
<br />
First, I am assuming it is not a problem for a desktop windows form application to access a SQL server on a internal network given the connection parameters are provided. &nbsp;Please correct me if I am wrong. &nbsp;What other things do we need to consider if we decide to make this change?
</div>
</div>


Currently we have a C# .net windows application that uses a local desktop instance of SQL Server.  We wanted to know the challenges of changing this model to using a single instance of a SQL Server on a network.

First, I am assuming it is not a problem for a desktop windows form application to access a SQL server on a internal network given the connection parameters are provided.  Please correct me if I am wrong.  What other things do we need to consider if we decide to make this change?

WIndow form accessing a SQL Server on network

C# is an object-oriented programming language created in conjunction with Microsoft’s .NET framework. Compilation is usually done into the Microsoft Intermediate Language (MSIL), which is then JIT-compiled to native code (and cached) during execution in the Common Language Runtime (CLR).

Microsoft SQL Server 2005 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. It includes support for managing XML data and allows a database server to be exposed over web services using Tabular Data Stream (TDS) packets encapsulated within SOAP (protocol) requests.