Re: URGENT: ConnectionString for SQLServer db
- From: "W.G. Ryan" <WilliamRyan@xxxxxxxxxxxxxxxx>
- Date: Fri, 7 Dec 2007 10:38:32 -0500
Attaching a file does effectively cause the Sql Server instance to 'use' the
file. Remember that real Sql Server datafiles are .mdf so yes, it ends up
using it as the data file.
"Cirene" <test@xxxxxxxx> wrote in message
news:e11a3ZIOIHA.5224@xxxxxxxxxxxxxxxxxxxxxxx
Does attaching a database basically import it into an SQL Server DB, or
does it actually use the SQL Express mdf file?
"William (Bill) Vaughn" <billvaRemoveThis@xxxxxxxxx> wrote in message
news:00E45622-F611-4FE6-8481-6596E93F9D38@xxxxxxxxxxxxxxxx
A remote SQL Server database needs to be addressed in two ways:
1) The system or machine name. When the database was on the local system
this was "." but we have no way to know what that is. Let's say it's
"George".
2) The SQL Server Instance name. We have no way of knowing the instance
name on the target server would be. Let's say it's "Fred".
In this example the ConnectionString would look something like this:
"Server=George\Fred;integrated security=SSPI;initial catalog=ASPNETDB"
There is no need to reattach the database since you already attached it
to the remote server master database.
See Chapter 9 of my book.
hth
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no
rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------
"Cirene" <test@xxxxxxxx> wrote in message
news:OlD5Ad5NIHA.4584@xxxxxxxxxxxxxxxxxxxxxxx
I developed my ASP.NET 2.0 web app using SQL Express. Now I'm moving it
to production.
On my web server I attached the SQL Express mdf database to a new SQL
Server database. The (example) SQL Server settings are:
DB Name: rnz_mydb
Server IP: sql123.MyHost.com
Login ID: rnz_admin
Db Type: MSSQL 2005
The current web.config connection string is this:
<connectionStrings>
<remove name="LocalSqlServer" />
<add name="LocalSqlServer" connectionString="Data
Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\zASPNETDB.MDF;Integrated
Security=True;Initial Catalog=ASPNETDB"
providerName="System.Data.SqlClient" />
<add name="ConnectionString" connectionString="Data
Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\zASPNETDB.MDF;Integrated
Security=True;Initial Catalog=ASPNETDB"
providerName="System.Data.SqlClient" />
</connectionStrings>
What should the connection string be now (to point to the new SQL SERVER
db)?
Thanks!
.
- References:
- URGENT: ConnectionString for SQLServer db
- From: Cirene
- Re: URGENT: ConnectionString for SQLServer db
- From: William \(Bill\) Vaughn
- Re: URGENT: ConnectionString for SQLServer db
- From: Cirene
- URGENT: ConnectionString for SQLServer db
- Prev by Date: Re: Simple Adapter.Update problem
- Next by Date: RE: Error while connecting remote SQL server
- Previous by thread: Re: URGENT: ConnectionString for SQLServer db
- Next by thread: Enumerate providers on System / Understanding providers and dataproviders
- Index(es):
Relevant Pages
|