Move large table from DB to DB

I have a table of approx 1/2 million rows.

On a nightly basis, this table gets rebuilt in a temporary database. Once the table has been built and scrubbed, i need to move it into our webservers db.

I'd like to do this with minimal interuption to the website.

Possible techniques:

1) I could set up a DTS package to copy the table object overwriting the destination table

2) I could export to a flat file and then bulk import into the live table (after truncating it)

3) I could run a process to update smaller chunks of data at a time running delete queries and insert queries.

Anybody have a thought on the best way to do this so that the web users would be virtually unaware that anything was happening ?Is the webserver's db.. like at a remote location?

I'd go with loading that temp db to another temp db on the webserver, and reverse engineer it.|||The temp DB is on the same SQL server as the webservers DB.

so the questions remains....

What's the best way to move a table from DB to DB with minimal interuption to the user?|||I use DTS for almost the same thing, but my table is < 1gig. I dont notice any slowdown, but I probably only have 5 current users at any instance.|||are you object copying or bulk inserting ?

Move Database to client

Hi,
We have a database that we built for a client and we would like to make a
backup of the database and restore the database on our clients Sql Server
box. Both environments are running SQL Server 2000 SP3a.
We make a backup of the database on our server and when we go to the clients
site and run the restore it complains and gives an error message that states
SQL-DMO (ODBC SQLState: 42000) and states we should use the WITH MOVE. We
tried the WITH MOVE but aree not experienced DBA so we are not sure if we
configured it right.
RESTORE DATABASE TEST FROM DISK='C:\TEMP\CDR-Prod.BAK'
WITH MOVE 'TEST_Data' TO 'c:\program files\microsoft sql
server\mssql\data\CDR-Prod_Data.MDF',
MOVE 'TEST_Log' TO ' c:\program files\microsoft sql
server\mssql\data\CDR-Prod_Log.LDF'
We were able to restore the database some how and then it gives us an
SQL-DMO error 21776.
Any ideas on how we should best approach this situation so that we can get
the full database (structure and data)?
Thanks for the assistance.Please post the entire error message. Error 21776 is the
generic error used for an object not found in a collection.
The specifics of what object in what collection would be in
the entire error message.
-Sue
On Sun, 13 Mar 2005 18:55:02 -0800, "Rod S" <Rod
S@.discussions.microsoft.com> wrote:
>Hi,
>We have a database that we built for a client and we would like to make a
>backup of the database and restore the database on our clients Sql Server
>box. Both environments are running SQL Server 2000 SP3a.
>We make a backup of the database on our server and when we go to the clients
>site and run the restore it complains and gives an error message that states
>SQL-DMO (ODBC SQLState: 42000) and states we should use the WITH MOVE. We
>tried the WITH MOVE but aree not experienced DBA so we are not sure if we
>configured it right.
>RESTORE DATABASE TEST FROM DISK='C:\TEMP\CDR-Prod.BAK'
>WITH MOVE 'TEST_Data' TO 'c:\program files\microsoft sql
>server\mssql\data\CDR-Prod_Data.MDF',
>MOVE 'TEST_Log' TO ' c:\program files\microsoft sql
>server\mssql\data\CDR-Prod_Log.LDF'
>
>We were able to restore the database some how and then it gives us an
>SQL-DMO error 21776.
>Any ideas on how we should best approach this situation so that we can get
>the full database (structure and data)?
>Thanks for the assistance.|||Hi,
Sorry Sue, I should have elaborated more:
We have two problems:
1. we areunable to restore the database properly using either the GUI based
restore tool in the Enterprise Manager or usign the Query Analyzer with the
script included.
2. We some how managed to restore the database on the client's server and
when we try to access any component of the "restored" database, we receive
the SQL-DMO 21776 error. Which states the following
"Error 21776: [SQL-DMO} The name 'CDR-Prod' was not found in the Databases
colelction. If the name is a qualified name, use [ ] to separate various
parts of the name and try again."
So what i am looking for is what is the best mechanism to move our database
from out SQL Server 2000 environment to the clients SQL Server 2000
environment where we can preserve the table structure and data contained
within the database.
As well, how can we delete the database that we were able to create but now
is not recognized by the Enterprise manager due to the 21776 error.
I hope this provides a more detailed explanation of the situation we are
facing.
Thanks for the assistance,
Rod
"Sue Hoegemeier" wrote:
> Please post the entire error message. Error 21776 is the
> generic error used for an object not found in a collection.
> The specifics of what object in what collection would be in
> the entire error message.
> -Sue
> On Sun, 13 Mar 2005 18:55:02 -0800, "Rod S" <Rod
> S@.discussions.microsoft.com> wrote:
> >Hi,
> >
> >We have a database that we built for a client and we would like to make a
> >backup of the database and restore the database on our clients Sql Server
> >box. Both environments are running SQL Server 2000 SP3a.
> >
> >We make a backup of the database on our server and when we go to the clients
> >site and run the restore it complains and gives an error message that states
> >SQL-DMO (ODBC SQLState: 42000) and states we should use the WITH MOVE. We
> >tried the WITH MOVE but aree not experienced DBA so we are not sure if we
> >configured it right.
> >
> >RESTORE DATABASE TEST FROM DISK='C:\TEMP\CDR-Prod.BAK'
> >WITH MOVE 'TEST_Data' TO 'c:\program files\microsoft sql
> >server\mssql\data\CDR-Prod_Data.MDF',
> >MOVE 'TEST_Log' TO ' c:\program files\microsoft sql
> >server\mssql\data\CDR-Prod_Log.LDF'
> >
> >
> >We were able to restore the database some how and then it gives us an
> >SQL-DMO error 21776.
> >
> >Any ideas on how we should best approach this situation so that we can get
> >the full database (structure and data)?
> >
> >Thanks for the assistance.
>|||The best mechanism is a backup and restore. You can also use
sp_detach_db, copy the data and log files and have the
client attach the files with sp_attach_db.
I would guess many of the problems are from having a
non-standard database name. The rules for identifier and
what characters are allowed in what positions is in the
books online topic: Using Identifiers
In terms of how to delete the database now, try dropping the
database using query analyzer and putting brackets around
the database name.
drop database [CDR-Prod]
-Sue
On Mon, 14 Mar 2005 08:11:05 -0800, "Rod S"
<RodS@.discussions.microsoft.com> wrote:
>Hi,
>Sorry Sue, I should have elaborated more:
>We have two problems:
>1. we areunable to restore the database properly using either the GUI based
>restore tool in the Enterprise Manager or usign the Query Analyzer with the
>script included.
>2. We some how managed to restore the database on the client's server and
>when we try to access any component of the "restored" database, we receive
>the SQL-DMO 21776 error. Which states the following
>"Error 21776: [SQL-DMO} The name 'CDR-Prod' was not found in the Databases
>colelction. If the name is a qualified name, use [ ] to separate various
>parts of the name and try again."
>So what i am looking for is what is the best mechanism to move our database
>from out SQL Server 2000 environment to the clients SQL Server 2000
>environment where we can preserve the table structure and data contained
>within the database.
>As well, how can we delete the database that we were able to create but now
>is not recognized by the Enterprise manager due to the 21776 error.
>I hope this provides a more detailed explanation of the situation we are
>facing.
>Thanks for the assistance,
>Rod
>"Sue Hoegemeier" wrote:
>> Please post the entire error message. Error 21776 is the
>> generic error used for an object not found in a collection.
>> The specifics of what object in what collection would be in
>> the entire error message.
>> -Sue
>> On Sun, 13 Mar 2005 18:55:02 -0800, "Rod S" <Rod
>> S@.discussions.microsoft.com> wrote:
>> >Hi,
>> >
>> >We have a database that we built for a client and we would like to make a
>> >backup of the database and restore the database on our clients Sql Server
>> >box. Both environments are running SQL Server 2000 SP3a.
>> >
>> >We make a backup of the database on our server and when we go to the clients
>> >site and run the restore it complains and gives an error message that states
>> >SQL-DMO (ODBC SQLState: 42000) and states we should use the WITH MOVE. We
>> >tried the WITH MOVE but aree not experienced DBA so we are not sure if we
>> >configured it right.
>> >
>> >RESTORE DATABASE TEST FROM DISK='C:\TEMP\CDR-Prod.BAK'
>> >WITH MOVE 'TEST_Data' TO 'c:\program files\microsoft sql
>> >server\mssql\data\CDR-Prod_Data.MDF',
>> >MOVE 'TEST_Log' TO ' c:\program files\microsoft sql
>> >server\mssql\data\CDR-Prod_Log.LDF'
>> >
>> >
>> >We were able to restore the database some how and then it gives us an
>> >SQL-DMO error 21776.
>> >
>> >Any ideas on how we should best approach this situation so that we can get
>> >the full database (structure and data)?
>> >
>> >Thanks for the assistance.
>>

Move Database to client

Hi,
We have a database that we built for a client and we would like to make a
backup of the database and restore the database on our clients Sql Server
box. Both environments are running SQL Server 2000 SP3a.
We make a backup of the database on our server and when we go to the clients
site and run the restore it complains and gives an error message that states
SQL-DMO (ODBC SQLState: 42000) and states we should use the WITH MOVE. We
tried the WITH MOVE but aree not experienced DBA so we are not sure if we
configured it right.
RESTORE DATABASE TEST FROM DISK='C:\TEMP\CDR-Prod.BAK'
WITH MOVE 'TEST_Data' TO 'c:\program files\microsoft sql
server\mssql\data\CDR-Prod_Data.MDF',
MOVE 'TEST_Log' TO ' c:\program files\microsoft sql
server\mssql\data\CDR-Prod_Log.LDF'
We were able to restore the database some how and then it gives us an
SQL-DMO error 21776.
Any ideas on how we should best approach this situation so that we can get
the full database (structure and data)?
Thanks for the assistance.
Please post the entire error message. Error 21776 is the
generic error used for an object not found in a collection.
The specifics of what object in what collection would be in
the entire error message.
-Sue
On Sun, 13 Mar 2005 18:55:02 -0800, "Rod S" <Rod
S@.discussions.microsoft.com> wrote:

>Hi,
>We have a database that we built for a client and we would like to make a
>backup of the database and restore the database on our clients Sql Server
>box. Both environments are running SQL Server 2000 SP3a.
>We make a backup of the database on our server and when we go to the clients
>site and run the restore it complains and gives an error message that states
>SQL-DMO (ODBC SQLState: 42000) and states we should use the WITH MOVE. We
>tried the WITH MOVE but aree not experienced DBA so we are not sure if we
>configured it right.
>RESTORE DATABASE TEST FROM DISK='C:\TEMP\CDR-Prod.BAK'
>WITH MOVE 'TEST_Data' TO 'c:\program files\microsoft sql
>server\mssql\data\CDR-Prod_Data.MDF',
>MOVE 'TEST_Log' TO ' c:\program files\microsoft sql
>server\mssql\data\CDR-Prod_Log.LDF'
>
>We were able to restore the database some how and then it gives us an
>SQL-DMO error 21776.
>Any ideas on how we should best approach this situation so that we can get
>the full database (structure and data)?
>Thanks for the assistance.
|||Hi,
Sorry Sue, I should have elaborated more:
We have two problems:
1. we areunable to restore the database properly using either the GUI based
restore tool in the Enterprise Manager or usign the Query Analyzer with the
script included.
2. We some how managed to restore the database on the client's server and
when we try to access any component of the "restored" database, we receive
the SQL-DMO 21776 error. Which states the following
"Error 21776: [SQL-DMO} The name 'CDR-Prod' was not found in the Databases
colelction. If the name is a qualified name, use [ ] to separate various
parts of the name and try again."
So what i am looking for is what is the best mechanism to move our database
from out SQL Server 2000 environment to the clients SQL Server 2000
environment where we can preserve the table structure and data contained
within the database.
As well, how can we delete the database that we were able to create but now
is not recognized by the Enterprise manager due to the 21776 error.
I hope this provides a more detailed explanation of the situation we are
facing.
Thanks for the assistance,
Rod
"Sue Hoegemeier" wrote:

> Please post the entire error message. Error 21776 is the
> generic error used for an object not found in a collection.
> The specifics of what object in what collection would be in
> the entire error message.
> -Sue
> On Sun, 13 Mar 2005 18:55:02 -0800, "Rod S" <Rod
> S@.discussions.microsoft.com> wrote:
>
>
|||The best mechanism is a backup and restore. You can also use
sp_detach_db, copy the data and log files and have the
client attach the files with sp_attach_db.
I would guess many of the problems are from having a
non-standard database name. The rules for identifier and
what characters are allowed in what positions is in the
books online topic: Using Identifiers
In terms of how to delete the database now, try dropping the
database using query analyzer and putting brackets around
the database name.
drop database [CDR-Prod]
-Sue
On Mon, 14 Mar 2005 08:11:05 -0800, "Rod S"
<RodS@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi,
>Sorry Sue, I should have elaborated more:
>We have two problems:
>1. we areunable to restore the database properly using either the GUI based
>restore tool in the Enterprise Manager or usign the Query Analyzer with the
>script included.
>2. We some how managed to restore the database on the client's server and
>when we try to access any component of the "restored" database, we receive
>the SQL-DMO 21776 error. Which states the following
>"Error 21776: [SQL-DMO} The name 'CDR-Prod' was not found in the Databases
>colelction. If the name is a qualified name, use [ ] to separate various
>parts of the name and try again."
>So what i am looking for is what is the best mechanism to move our database
>from out SQL Server 2000 environment to the clients SQL Server 2000
>environment where we can preserve the table structure and data contained
>within the database.
>As well, how can we delete the database that we were able to create but now
>is not recognized by the Enterprise manager due to the 21776 error.
>I hope this provides a more detailed explanation of the situation we are
>facing.
>Thanks for the assistance,
>Rod
>"Sue Hoegemeier" wrote:

Move Database to client

Hi,
We have a database that we built for a client and we would like to make a
backup of the database and restore the database on our clients Sql Server
box. Both environments are running SQL Server 2000 SP3a.
We make a backup of the database on our server and when we go to the clients
site and run the restore it complains and gives an error message that states
SQL-DMO (ODBC SQLState: 42000) and states we should use the WITH MOVE. We
tried the WITH MOVE but aree not experienced DBA so we are not sure if we
configured it right.
RESTORE DATABASE TEST FROM DISK='C:\TEMP\CDR-Prod.BAK'
WITH MOVE 'TEST_Data' TO 'c:\program files\microsoft sql
server\mssql\data\CDR-Prod_Data.MDF',
MOVE 'TEST_Log' TO ' c:\program files\microsoft sql
server\mssql\data\CDR-Prod_Log.LDF'
We were able to restore the database some how and then it gives us an
SQL-DMO error 21776.
Any ideas on how we should best approach this situation so that we can get
the full database (structure and data)?
Thanks for the assistance.Please post the entire error message. Error 21776 is the
generic error used for an object not found in a collection.
The specifics of what object in what collection would be in
the entire error message.
-Sue
On Sun, 13 Mar 2005 18:55:02 -0800, "Rod S" <Rod
S@.discussions.microsoft.com> wrote:

>Hi,
>We have a database that we built for a client and we would like to make a
>backup of the database and restore the database on our clients Sql Server
>box. Both environments are running SQL Server 2000 SP3a.
>We make a backup of the database on our server and when we go to the client
s
>site and run the restore it complains and gives an error message that state
s
>SQL-DMO (ODBC SQLState: 42000) and states we should use the WITH MOVE. We
>tried the WITH MOVE but aree not experienced DBA so we are not sure if we
>configured it right.
>RESTORE DATABASE TEST FROM DISK='C:\TEMP\CDR-Prod.BAK'
>WITH MOVE 'TEST_Data' TO 'c:\program files\microsoft sql
>server\mssql\data\CDR-Prod_Data.MDF',
>MOVE 'TEST_Log' TO ' c:\program files\microsoft sql
>server\mssql\data\CDR-Prod_Log.LDF'
>
>We were able to restore the database some how and then it gives us an
>SQL-DMO error 21776.
>Any ideas on how we should best approach this situation so that we can get
>the full database (structure and data)?
>Thanks for the assistance.|||Hi,
Sorry Sue, I should have elaborated more:
We have two problems:
1. we areunable to restore the database properly using either the GUI based
restore tool in the Enterprise Manager or usign the Query Analyzer with the
script included.
2. We some how managed to restore the database on the client's server and
when we try to access any component of the "restored" database, we receive
the SQL-DMO 21776 error. Which states the following
"Error 21776: [SQL-DMO} The name 'CDR-Prod' was not found in the Databas
es
colelction. If the name is a qualified name, use [ ] to separate variou
s
parts of the name and try again."
So what i am looking for is what is the best mechanism to move our database
from out SQL Server 2000 environment to the clients SQL Server 2000
environment where we can preserve the table structure and data contained
within the database.
As well, how can we delete the database that we were able to create but now
is not recognized by the Enterprise manager due to the 21776 error.
I hope this provides a more detailed explanation of the situation we are
facing.
Thanks for the assistance,
Rod
"Sue Hoegemeier" wrote:

> Please post the entire error message. Error 21776 is the
> generic error used for an object not found in a collection.
> The specifics of what object in what collection would be in
> the entire error message.
> -Sue
> On Sun, 13 Mar 2005 18:55:02 -0800, "Rod S" <Rod
> S@.discussions.microsoft.com> wrote:
>
>|||The best mechanism is a backup and restore. You can also use
sp_detach_db, copy the data and log files and have the
client attach the files with sp_attach_db.
I would guess many of the problems are from having a
non-standard database name. The rules for identifier and
what characters are allowed in what positions is in the
books online topic: Using Identifiers
In terms of how to delete the database now, try dropping the
database using query analyzer and putting brackets around
the database name.
drop database [CDR-Prod]
-Sue
On Mon, 14 Mar 2005 08:11:05 -0800, "Rod S"
<RodS@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi,
>Sorry Sue, I should have elaborated more:
>We have two problems:
>1. we areunable to restore the database properly using either the GUI based
>restore tool in the Enterprise Manager or usign the Query Analyzer with the
>script included.
>2. We some how managed to restore the database on the client's server and
>when we try to access any component of the "restored" database, we receive
>the SQL-DMO 21776 error. Which states the following
>"Error 21776: [SQL-DMO} The name 'CDR-Prod' was not found in the Databa
ses
>colelction. If the name is a qualified name, use [ ] to separate vario
us
>parts of the name and try again."
>So what i am looking for is what is the best mechanism to move our database
>from out SQL Server 2000 environment to the clients SQL Server 2000
>environment where we can preserve the table structure and data contained
>within the database.
>As well, how can we delete the database that we were able to create but now
>is not recognized by the Enterprise manager due to the 21776 error.
>I hope this provides a more detailed explanation of the situation we are
>facing.
>Thanks for the assistance,
>Rod
>"Sue Hoegemeier" wrote:
>

Move Database and Relocate Transaction Logs

Hello,
We have just built a Windows 2000 Advance Server with SQL Server 2000
Enterprise Edition. We would like to move some databases off of an old SQL
2000 Server onto this new server.
Questions:
What is the proper procedure for moving these databases over?
Once the databases are transferred, how can we relocate all of the
transaction logs (master, model, tempdb and databases we have created) to
another drive?
Thanks,
JBaileyCheckout the Copy Database Wizard, you can specify where
the files get copied to. It doesn't copy system
databases, but should grab most relevant material from
them.
>--Original Message--
>Hello,
>We have just built a Windows 2000 Advance Server with SQL
Server 2000
>Enterprise Edition. We would like to move some databases
off of an old SQL
>2000 Server onto this new server.
>Questions:
>What is the proper procedure for moving these databases
over?
>Once the databases are transferred, how can we relocate
all of the
>transaction logs (master, model, tempdb and databases we
have created) to
>another drive?
>Thanks,
>JBailey
>
>.
>|||Best place to start is reading 224071. Also, CDW as recommended by .. is an option.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"JBailey" <abc@.123.com> wrote in message news:ucrE451kDHA.2424@.TK2MSFTNGP10.phx.gbl...
> Hello,
> We have just built a Windows 2000 Advance Server with SQL Server 2000
> Enterprise Edition. We would like to move some databases off of an old SQL
> 2000 Server onto this new server.
> Questions:
> What is the proper procedure for moving these databases over?
> Once the databases are transferred, how can we relocate all of the
> transaction logs (master, model, tempdb and databases we have created) to
> another drive?
> Thanks,
> JBailey
>|||Tibor,
224071 ? I cant seem to find that, have a link?
Thanks,
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:ehGA9E7kDHA.2012@.TK2MSFTNGP12.phx.gbl...
> Best place to start is reading 224071. Also, CDW as recommended by .. is
an option.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
> "JBailey" <abc@.123.com> wrote in message
news:ucrE451kDHA.2424@.TK2MSFTNGP10.phx.gbl...
> > Hello,
> >
> > We have just built a Windows 2000 Advance Server with SQL Server 2000
> > Enterprise Edition. We would like to move some databases off of an old
SQL
> > 2000 Server onto this new server.
> >
> > Questions:
> >
> > What is the proper procedure for moving these databases over?
> > Once the databases are transferred, how can we relocate all of the
> > transaction logs (master, model, tempdb and databases we have created)
to
> > another drive?
> >
> > Thanks,
> >
> > JBailey
> >
> >
>|||Found 224071.
Questions:
Is it necessary to move the master, model, and tempdb over? Or can I just
move the databases we created? Is there dependencies user created databases
have on the default SQL databases that I should be aware of?
Thanks,
JBailey
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:ehGA9E7kDHA.2012@.TK2MSFTNGP12.phx.gbl...
> Best place to start is reading 224071. Also, CDW as recommended by .. is
an option.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
> "JBailey" <abc@.123.com> wrote in message
news:ucrE451kDHA.2424@.TK2MSFTNGP10.phx.gbl...
> > Hello,
> >
> > We have just built a Windows 2000 Advance Server with SQL Server 2000
> > Enterprise Edition. We would like to move some databases off of an old
SQL
> > 2000 Server onto this new server.
> >
> > Questions:
> >
> > What is the proper procedure for moving these databases over?
> > Once the databases are transferred, how can we relocate all of the
> > transaction logs (master, model, tempdb and databases we have created)
to
> > another drive?
> >
> > Thanks,
> >
> > JBailey
> >
> >
>|||You can to consider what is stored in the system databases. In master, you have logins, linked
servers, sysmessages, sp_configure. In msdb, you have jobs, operators, alerts.
Only you can say whether above is a too huge job to do manually compared to try to get backup etc
over to the new server.
As for logins (which generally is the main issue), read in books online about sp_change_users_login
and you might want to use the GUI tool at www.dbmaint.com (free utilities).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"JBailey" <abc@.123.com> wrote in message news:OXwiR3%23kDHA.2364@.TK2MSFTNGP11.phx.gbl...
> Found 224071.
> Questions:
> Is it necessary to move the master, model, and tempdb over? Or can I just
> move the databases we created? Is there dependencies user created databases
> have on the default SQL databases that I should be aware of?
> Thanks,
> JBailey
>
> "Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
> wrote in message news:ehGA9E7kDHA.2012@.TK2MSFTNGP12.phx.gbl...
> > Best place to start is reading 224071. Also, CDW as recommended by .. is
> an option.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > Archive at: http://groups.google.com/groups?oi=djq&as
> ugroup=microsoft.public.sqlserver
> >
> >
> > "JBailey" <abc@.123.com> wrote in message
> news:ucrE451kDHA.2424@.TK2MSFTNGP10.phx.gbl...
> > > Hello,
> > >
> > > We have just built a Windows 2000 Advance Server with SQL Server 2000
> > > Enterprise Edition. We would like to move some databases off of an old
> SQL
> > > 2000 Server onto this new server.
> > >
> > > Questions:
> > >
> > > What is the proper procedure for moving these databases over?
> > > Once the databases are transferred, how can we relocate all of the
> > > transaction logs (master, model, tempdb and databases we have created)
> to
> > > another drive?
> > >
> > > Thanks,
> > >
> > > JBailey
> > >
> > >
> >
> >
>