I have created a SQL 2005 database with about 100 tables. It was actually
mostly created on 2000 and attached. I have started creating a VS VB
application. I am able to use any and all the tables in the applications.
I
have updated individual tables.
I have published the appl and have installed it on a different PC. When I
do, I get this message: An error has occurred while establishing a
connection to the server. When connecting to SQL Server 2005 this failure
may be caused by the fact that under the default settings the SQL Server doe
s
not allow remote conncections.
I have previously configured the SQL server to allow remote TCP/IP
connections. However, I named the instance of the server when I created it.
My computer is BAA1 and the instance is BAA1\BAA2. I don't really want the
application to attach to my computer, but to the SQLEXPRESS (runtime?)
version of the database that goes with the application.
Can I buy a clue here? This is killing me.
Thanks in advance.
David BennerFor the first problem - connecting to the instance, run through my short
tutorial on connecting. It covers instance names, ports, firewalls, and the
protocols. It's in the Books Online tutorials, or at
http://msdn2.microsoft.com/en-us/library/ms345318(SQL.90).aspx
As for moving the database, after you are connected to BAA1\BAA2, run
sp_detach_db (http://msdn2.microsoft.com/en-us/library/ms188031.aspx) and
then on your SQL Express instance run CREATE DATABASE ... FOR ATTACH,
example E at http://msdn2.microsoft.com/en-us/library/ms176061.aspx
Rick Byham
MCDBA, MCSE, MCSA
Documentation Manager,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Benner" <Benner@.discussions.microsoft.com> wrote in message
news:0B6DB41B-68B3-4CDF-B48D-420DC1738DAB@.microsoft.com...
>I have created a SQL 2005 database with about 100 tables. It was actually
> mostly created on 2000 and attached. I have started creating a VS VB
> application. I am able to use any and all the tables in the applications.
> I
> have updated individual tables.
> I have published the appl and have installed it on a different PC. When I
> do, I get this message: An error has occurred while establishing a
> connection to the server. When connecting to SQL Server 2005 this failure
> may be caused by the fact that under the default settings the SQL Server
> does
> not allow remote conncections.
> I have previously configured the SQL server to allow remote TCP/IP
> connections. However, I named the instance of the server when I created
> it.
> My computer is BAA1 and the instance is BAA1\BAA2. I don't really want
> the
> application to attach to my computer, but to the SQLEXPRESS (runtime?)
> version of the database that goes with the application.
> Can I buy a clue here? This is killing me.
> Thanks in advance.
>
> --
> David Benner|||Rick:
Thanks for your reply.
I think I was not clear enough in describing my problem. I have no problem
connection to the database and using that database with a connection in VS
2005. I have updated the database with both the SQL Server Mgmt Studio and
with the application I have created. I am having trouble when I publish the
VS 2005 windows application and try to use it on another computer. I am not
trying to connect with the application back to my first or main computer, bu
t
expect the application to connect to a "runtime" version of the database on
the same computer as the application.
I don't have an instance called SQLEXPRESS. I am not sure if my
installation choices precluded that from installing or what. Can I create
the SQLEXPRESS instance or do I need it to do what I am describing?
David Benner
"Rick Byham [MS]" wrote:
> For the first problem - connecting to the instance, run through my short
> tutorial on connecting. It covers instance names, ports, firewalls, and th
e
> protocols. It's in the Books Online tutorials, or at
> http://msdn2.microsoft.com/en-us/library/ms345318(SQL.90).aspx
> As for moving the database, after you are connected to BAA1\BAA2, run
> sp_detach_db (http://msdn2.microsoft.com/en-us/library/ms188031.aspx) and
> then on your SQL Express instance run CREATE DATABASE ... FOR ATTACH,
> example E at http://msdn2.microsoft.com/en-us/library/ms176061.aspx
> Rick Byham
> MCDBA, MCSE, MCSA
> Documentation Manager,
> Microsoft, SQL Server Books Online
> This posting is provided "as is" with
> no warranties, and confers no rights.
> "Benner" <Benner@.discussions.microsoft.com> wrote in message
> news:0B6DB41B-68B3-4CDF-B48D-420DC1738DAB@.microsoft.com...
>
>|||You need to install SQL Express on the machine you want to run the
application on. When you do, it will create a SQLEXPRESS instance by
default. There's more information on User Instances here:
http://msdn.microsoft.com/sql/expre...expuserinst.asp
and more information on embedding express in your setup here:
http://msdn.microsoft.com/library/d...>
xCustApp.asp
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Benner" <Benner@.discussions.microsoft.com> wrote in message
news:A8DFB820-E29A-4266-A913-B58A5EEE3B25@.microsoft.com...[vbcol=seagreen]
> Rick:
> Thanks for your reply.
> I think I was not clear enough in describing my problem. I have no
> problem
> connection to the database and using that database with a connection in VS
> 2005. I have updated the database with both the SQL Server Mgmt Studio
> and
> with the application I have created. I am having trouble when I publish
> the
> VS 2005 windows application and try to use it on another computer. I am
> not
> trying to connect with the application back to my first or main computer,
> but
> expect the application to connect to a "runtime" version of the database
> on
> the same computer as the application.
> I don't have an instance called SQLEXPRESS. I am not sure if my
> installation choices precluded that from installing or what. Can I create
> the SQLEXPRESS instance or do I need it to do what I am describing?
>
> --
> David Benner
>
> "Rick Byham [MS]" wrote:
>
