Connecting to a SQL Server Database Using ASP.NET 3.5
Before you upload your ASP.NET 3.5 application onto your hosting server, you need to modify the connection strings section of your web.config file.
NOTE: You may want to back up the web.config file on your local computer or simply comment out your current connection strings before you make any changes. This way, you can easily return to developing your application on you local computer.
This is an example of the connection strings section that will connect an ASP.NET 3.5 application to one of our SQL Servers:
<add name="Personal" connectionString=" Server=whsql-v04.prod.mesa1.secureserver.net; Database=DB_675; User ID=user_id; Password=password; Trusted_Connection=False" providerName="System.Data.SqlClient" /> <remove name="LocalSqlServer"/><add name="LocalSqlServer" connectionString=" Server=whsql-v04.prod.mesa1.secureserver.net; Database=DB_675; User ID=user_id; Password=password; Trusted_Connection=False" providerName="System.Data.SqlClient" />
NOTE: You can find your server name, database name, user ID, and password in the SQL Server section of your Hosting Control Panel. These connection string values map to host name, database name, user name, and password, respectively. The user name and password values are those specified during SQL database (not hosting account) creation.
What Is Medium trust level and how does it affect my hosting account?
What ASP.NET runtime version should I choose?
Is Parent Path Enabled on Shared ASP Hosting?
What is ASP.NET 3.5?
What should I use to develop ASP.NET 3.5 Web sites?
Why are ASP.NET runtimes 2.0, 3.0 and 3.5 grouped together?
Your message was successfully sent.
There was an error in sending your message, please try again.
Have a question about the content of this article?