Bob wrote:

> I am using SQL Server 2005 and using a database program that was installed
> on the C:\ drive of the server. The 12gb partition has 1.8gb left and I
> need to move it to the 550gb D:\ drive. Simple, yes and no. I have an
> external MS Access 2003 report program that connects to the database via a
> ODBC DSN file connection that I used to link certain tables.
>
> The question is what happens to my connection if I move the SQL database to
> the other drive? Will I lose my connection?
>
> I shouldn't, so I thought. So I wanted to test my theory. The program I am
> connecting to allows you to install a training or release version of the
> database on the server, which I created a TEST file installed to the D:\
> drive where I want the real one. I have also played with Access in creating
> a new project file and an upsized MDB program on the same server. By
> default they were created on the C:\ drive and I have access to them.
>
> Now I tried to create a new ODBC connection to my TEST database that I
> installed on D:\. I get to the part where you select which database to
> connect to and it is not listed as one of the default files on the server.
> In fact only the ones found on the C:\ drive are listed except the sample
> databases like Northwind. There is no way to type in the name I want
> because it says it doesn't exist. If I copy the database file that is
> listed, that copy is not listed either.
>
> Another question: how do you make a database file part of the default
> listing so it can be connected too? Or do I just have to figure out how to
> use connect strings in VBA? Is there a way to edit this in the server
> manager library of programs?

Bob wrote:

>> Did you install a second copy of SQL Server? If so, then it probably
>> set itself up as a named instance, in which case you need to specify
>> that name to connect to any of its databases.

> No just one installation of SQL server 2005 loaded. I am pretty new at all
> this as a database admin using this program. I can create new databases but
> when I physically move them to another drive will they still be available?
> Just don't know yet. Tomorrow I am going to try moving one of my testing
> files that show up in the list to the other drive just to see what happens.

"Ed Murphy" <emurphy42@socal.rr.com> wrote in message
news:461981d2$0$17126$4c368faf@roadrunner.com...
> Bob wrote:
>
>> I am using SQL Server 2005 and using a database program that was
>> installed on the C:\ drive of the server. The 12gb partition has 1.8gb
>> left and I need to move it to the 550gb D:\ drive. Simple, yes and no.
>> I have an external MS Access 2003 report program that connects to the
>> database via a ODBC DSN file connection that I used to link certain
>> tables.
>>
>> The question is what happens to my connection if I move the SQL database
>> to the other drive? Will I lose my connection?
>>
>> I shouldn't, so I thought. So I wanted to test my theory. The program I
>> am connecting to allows you to install a training or release version of
>> the database on the server, which I created a TEST file installed to the
>> D:\ drive where I want the real one. I have also played with Access in
>> creating a new project file and an upsized MDB program on the same
>> server. By default they were created on the C:\ drive and I have access
>> to them.
>>
>> Now I tried to create a new ODBC connection to my TEST database that I
>> installed on D:\. I get to the part where you select which database to
>> connect to and it is not listed as one of the default files on the
>> server. In fact only the ones found on the C:\ drive are listed except
>> the sample databases like Northwind. There is no way to type in the name
>> I want because it says it doesn't exist. If I copy the database file
>> that is listed, that copy is not listed either.
>>
>> Another question: how do you make a database file part of the default
>> listing so it can be connected too? Or do I just have to figure out how
>> to use connect strings in VBA? Is there a way to edit this in the server
>> manager library of programs?
>
> Did you install a second copy of SQL Server? If so, then it probably
> set itself up as a named instance, in which case you need to specify
> that name to connect to any of its databases.
>
> Copying the underlying file definitely won't work, because the copy
> isn't attached to SQL Server.

"Ed Murphy" <emurphy42@socal.rr.com> wrote in message
news:4619ae35$0$9912$4c368faf@roadrunner.com...
> Bob wrote:
>
>>> Did you install a second copy of SQL Server? If so, then it probably
>>> set itself up as a named instance, in which case you need to specify
>>> that name to connect to any of its databases.
>
>> No just one installation of SQL server 2005 loaded. I am pretty new at
>> all this as a database admin using this program. I can create new
>> databases but when I physically move them to another drive will they
>> still be available? Just don't know yet. Tomorrow I am going to try
>> moving one of my testing files that show up in the list to the other
>> drive just to see what happens.
>
> (Please don't top-post. Fixed.)
>
> If you're just moving files while the SQL Server service is stopped,
> then the service will lose track of the database. You need to either
> (1) use SSMS to move the files, or (2) detach the files beforehand
> and re-attach them afterward.