Re: How do i move an SQLDatabase to another location?



Hello Bill.

From your reply, i thought you were trying to give me a hint as to where to
look to figure out what i want to do. I read some of the SQL Server
Management Studio Express documentation and it does not seem to contain info
about what i want to do.

I guess i should have been more specific in explaining what i ultimately
want to do.

I want to be able to take a finished project with an empty database to a
client location, install it and have it run using the database without
having connection string, security, SQL error message and program bombing
issues.

I figured this could be done inside the program by creating some kind of
dynamic connection string, but i just don't know where to look to find out
how to do it.

Do i need to bring SQL Server Express with me to the clients?

Do i need to know what the connection string will look like before i go
there?

How do i determine if i want to have a shared server-based database or do i
want to have one that installed independently on the client?

I don't even know what these terms mean. I just want to be able to take my
stuff somewhere and have it work without getting a bunch of error messages.

Thanks,
Tony

"William (Bill) Vaughn" <billvaRemoveThis@xxxxxxxxxx> wrote in message
news:uB1YEfmaHHA.808@xxxxxxxxxxxxxxxxxxxxxxx
Where you place your database (.mdf and .ldf) file(s) is up to you. If you
use the VS UI tools, there are a number of defaults that kick in and (as you
found) SQL Server uses it's own "favorite" place to keep databases--you
aren't given a choice to pick your own location. SQL Server Express Edition
adds even more options (and complexity) as it permits you to have a
user-instance of SQL server with its own (another) copy of the database.
Yes, you can choose to put your database in the project as well. As I
illustrate in the book, you can end up with 6 or more versions of the
database in minutes. While each of these database instances can be updated,
it might appear that they are not due to the

I'm of the opinion, that one needs to decide on a deployment strategy before
clicking through the defaults. You need to decide if you want to have a
shared server-based database, one that's installed independently on the
client or one that's associated with your project. How you manage these SQL
Server servers and instances and the databases you create is really up to
you. Do the VS IDE tools help? Yes, but not very much. SQL Server Management
Studio gives you a lot more options and (thus) control over what gets built
where and when.

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)
-----------------------------------------------------------------------------------------------------------------------

"Tony Girgenti" <tony(nospam)@lakesideos.com> wrote in message
news:OOf5a%23laHHA.4788@xxxxxxxxxxxxxxxxxxxxxxx
Hello.

I realize my other post was a bit lengthy, so i'd like to repost this
question.

Developing VS2005, SP1, .NET 2.0, VB Windows form program on WIN XP Pro,
SP2. It has a Dataset with two tables using an SQL 9.0 Server Express.

After creating a new database from the VS server explorer, it seems that
the
new database always resides in \C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data.

When i create the datasource, it asks if i want to copy it to my project.
If i answer yes, i cannot update the database.

How do i move the database to another location?

Any help would be gratefully appreciated.

Thanks,
Tony



.



Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... an Access database in former times this was a lot of work which took me ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... client for programming easy, fast and good applications. ...
    (microsoft.public.sqlserver.connect)
  • Re: Quick Question on SQL Server 2005 Express
    ... you can't attach a database in a remote machine in your network as Andrew has already mantioned. ... One database can be used only by one SQL Server instance and as far as I understand the database in question is already attached to a SQL Server instance. ... Why not installing only SQL Server Management Studio and connect to your remote instance and perform actions this way? ... The Client can live anywhere as long as it has TCP access to the server. ...
    (microsoft.public.sqlserver.setup)
  • Re: Permissions problem on SBS 2003 R2 for SQL Server 2005 clients
    ... use SQL Server authentication instead. ... I've been testing a SQL Server 2005 Express database in a multiuser ... environment using Window Small Business Server 2003 R2 with Windows XP ... On a given client computer to which I may have logged on with Windows ...
    (microsoft.public.windows.server.sbs)
  • Re: Quick Question on SQL Server 2005 Express
    ... I have not seen any documentation yet that states connecting other editions of SQL Server using SSMSE would break any license agreement. ... As Ekrem stated they should have a licensed edition of the full client tools and then all they have to do is register the server in the registered servers dialog and they should be all set. ... I have installed SQL Server 2005 Express, and now I want to connect to the remote database and use the Management Studio to manipulate the database. ...
    (microsoft.public.sqlserver.setup)
  • Re: Why not Access...?
    ... Next, I DID NOT SAY Oracle was considered a "best choice," only a sufficient ... It is a desktop application and the database in also on the same machine. ... I also want to know why Oracle is considered a best choice as compared to SQL Server. ... > Also, you need to answer the question regarding whether or not each client> will be using an individual database, and individual copy of a central> organization database, or making straight calls to a centralized ...
    (microsoft.public.sqlserver.server)