Moving 5 databases to new server

In a few hours I am going to move 5 user databases from the existing product
ion server to a new one. I have a plan in place, but I would like to verify
that its the correct approach.
Here's my plan:
1. Stop SQL Server on production using Services Manager
2. Start SQL Server on production in Single User Mode
-using Services Manager, type "-m" in startup parameters
3. Perform a manual Full Backup of each user database to be migrated
4. Stop the SQL Server on production
5. Restore each database on the new server from the backup files
-check "force restore over existing database"
6. Link all orphaned logins on each database
7. Point the application to the new server
My main question is: Do I need to restore transaction logs also?
No users will be connected at the time of the full backup. I am currectly u
sing the Full recovery model on each database. I have already recreated all
the DTS jobs and Database Maintenance Plans on the new server. The new ser
ver is not yet in use, so I
was able to test the process by restoring each database from the production
backup files to the new server.
The production SQL Server is 2000 version 8.00.194(RTM). The new server is
2000 version 8.00.760(SP3).
Am I overlooking anything?
Thanks,
ScottI am placing the production database in single user mode to ensure there are
no other users.
I have actually performed the restores and they worked OK. I am not restori
ng the system databases only user databases.
The link you provided did not work.
"DeeJay Puar" wrote:

> Hi,
> Here are some comments:
> 1. Production server does have to in 'Single User Mode',
> since no one is going to be connected.
> 2. If you do a fullbackup and restore without further
> activity on the database, you do not have to restore any
> transaction log backups.
> 3. I do not think, restores will work with different
> service packs (production is different level than new
> server).
> 4. Here is an nice article to review:
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;314546&Product=sql
> hth
> DeeJay
> the existing production server to a new one. I have a
> plan in place, but I would like to verify that its the
> correct approach.
> parameters
> be migrated
> backup files
> logs also?
> backup. I am currectly using the Full recovery model on
> each database. I have already recreated all the DTS jobs
> and Database Maintenance Plans on the new server. The new
> server is not yet in use, so I was able to test the
> process by restoring each database from the production
> backup files to the new server.
> The new server is 2000 version 8.00.760(SP3).
>|||Some of below might help:
Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
How to Resolve Permission Issues When a Database Is Moved Between SQL Server
s
http://www.support.microsoft.com/?id=240872
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"scott" <scott@.discussions.microsoft.com> wrote in message
news:D4DB1784-FA39-4FD7-A9DC-F557759A333A@.microsoft.com...
> In a few hours I am going to move 5 user databases from the existing production se
rver to a new
one. I have a plan in place, but I would like to verify that its the correct approach.[vbco
l=seagreen]
> Here's my plan:
> 1. Stop SQL Server on production using Services Manager
> 2. Start SQL Server on production in Single User Mode
> -using Services Manager, type "-m" in startup parameters
> 3. Perform a manual Full Backup of each user database to be migrated
> 4. Stop the SQL Server on production
> 5. Restore each database on the new server from the backup files
> -check "force restore over existing database"
> 6. Link all orphaned logins on each database
> 7. Point the application to the new server
> My main question is: Do I need to restore transaction logs also?
> No users will be connected at the time of the full backup. I am currectly using t
he Full recovery[/vbcol]
model on each database. I have already recreated all the DTS jobs and Datab
ase Maintenance Plans on
the new server. The new server is not yet in use, so I was able to test the
process by restoring
each database from the production backup files to the new server.
> The production SQL Server is 2000 version 8.00.194(RTM). The new server is 2000 v
ersion
8.00.760(SP3).
> Am I overlooking anything?
> Thanks,
> Scott|||also,...
Restore or Detach\Reattach will not move\migrate SQL Agent Jobs, System
Messages, DTS Packages, etc.
Greg Jackson
PDX, Oregon

Moving 5 databases to new server

In a few hours I am going to move 5 user databases from the existing production server to a new one. I have a plan in place, but I would like to verify that its the correct approach.
Here's my plan:
1. Stop SQL Server on production using Services Manager
2. Start SQL Server on production in Single User Mode
-using Services Manager, type "-m" in startup parameters
3. Perform a manual Full Backup of each user database to be migrated
4. Stop the SQL Server on production
5. Restore each database on the new server from the backup files
-check "force restore over existing database"
6. Link all orphaned logins on each database
7. Point the application to the new server
My main question is: Do I need to restore transaction logs also?
No users will be connected at the time of the full backup. I am currectly using the Full recovery model on each database. I have already recreated all the DTS jobs and Database Maintenance Plans on the new server. The new server is not yet in use, so I
was able to test the process by restoring each database from the production backup files to the new server.
The production SQL Server is 2000 version 8.00.194(RTM). The new server is 2000 version 8.00.760(SP3).
Am I overlooking anything?
Thanks,
Scott
I am placing the production database in single user mode to ensure there are no other users.
I have actually performed the restores and they worked OK. I am not restoring the system databases only user databases.
The link you provided did not work.
"DeeJay Puar" wrote:

> Hi,
> Here are some comments:
> 1. Production server does have to in 'Single User Mode',
> since no one is going to be connected.
> 2. If you do a fullbackup and restore without further
> activity on the database, you do not have to restore any
> transaction log backups.
> 3. I do not think, restores will work with different
> service packs (production is different level than new
> server).
> 4. Here is an nice article to review:
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;314546&Product=sql
> hth
> DeeJay
> the existing production server to a new one. I have a
> plan in place, but I would like to verify that its the
> correct approach.
> parameters
> be migrated
> backup files
> logs also?
> backup. I am currectly using the Full recovery model on
> each database. I have already recreated all the DTS jobs
> and Database Maintenance Plans on the new server. The new
> server is not yet in use, so I was able to test the
> process by restoring each database from the production
> backup files to the new server.
> The new server is 2000 version 8.00.760(SP3).
>
|||Some of below might help:
Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
How to Resolve Permission Issues When a Database Is Moved Between SQL Servers
http://www.support.microsoft.com/?id=240872
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"scott" <scott@.discussions.microsoft.com> wrote in message
news:D4DB1784-FA39-4FD7-A9DC-F557759A333A@.microsoft.com...
> In a few hours I am going to move 5 user databases from the existing production server to a new
one. I have a plan in place, but I would like to verify that its the correct approach.
> Here's my plan:
> 1. Stop SQL Server on production using Services Manager
> 2. Start SQL Server on production in Single User Mode
> -using Services Manager, type "-m" in startup parameters
> 3. Perform a manual Full Backup of each user database to be migrated
> 4. Stop the SQL Server on production
> 5. Restore each database on the new server from the backup files
> -check "force restore over existing database"
> 6. Link all orphaned logins on each database
> 7. Point the application to the new server
> My main question is: Do I need to restore transaction logs also?
> No users will be connected at the time of the full backup. I am currectly using the Full recovery
model on each database. I have already recreated all the DTS jobs and Database Maintenance Plans on
the new server. The new server is not yet in use, so I was able to test the process by restoring
each database from the production backup files to the new server.
> The production SQL Server is 2000 version 8.00.194(RTM). The new server is 2000 version
8.00.760(SP3).
> Am I overlooking anything?
> Thanks,
> Scott
|||also,...
Restore or Detach\Reattach will not move\migrate SQL Agent Jobs, System
Messages, DTS Packages, etc.
Greg Jackson
PDX, Oregon

Move SQL Server Express .mdf file to SQL Server 2000

Is this even possible? I tried to move an existing Sql Server Express .mdf file to SQL Server 2000 by copying the .mdf file to the server's folder and then tried to attach it. I get:

Error 602: Could not find row in sysindexes for database ID 9, object ID 1, index ID1. Run DBCC CHECKTABLE on sysindexes.

I realize that I'm moving back a version in SQL, however the structure of the database is very simple. Does anyone know?

Even if I can just script the thing to SQL 2000 would be helpful, however the .mdf is a file within my ASP.Net site, and does not show up in my Microsoft SQL Server Management Studio Express under the appropriate SERVERNAME\SQLEXPRESS either, so I can't figure out how to script it out?

I found this in another post that allowed me to script out the data and the database itself

Microsoft SQL Server Database Publishing Wizard 1.0

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=29B4FFD8-AC3A-4481-B352-9B185619A901

move SQL 2000 server to new AD domain

Hello,
We have aquired a new company and I need to migrate a SQL 2000 server from
thier existing domain to our AD domain. Other than changing the service
accounts and any SQL domain accounts is there anything else I should be aware
of?
old domain: nt4
new domain: 2000 native
SQL server: win 2k advanced, SQl 2000 std.
thanks!Hi
If you are renaming the server as well as moving domain (same name in the
new domain should be ok) you will need to drop the server and re-create it
using sp_dropserver and sp_addserver see
http://support.microsoft.com/kb/303774
If you have windows logins then you will need to migrate those see
http://support.microsoft.com/kb/246133/
John
"decipher" wrote:
> Hello,
> We have aquired a new company and I need to migrate a SQL 2000 server from
> thier existing domain to our AD domain. Other than changing the service
> accounts and any SQL domain accounts is there anything else I should be aware
> of?
> old domain: nt4
> new domain: 2000 native
> SQL server: win 2k advanced, SQl 2000 std.
> thanks!

Move large amounts of data across Data Centers for DR

As you set up disaster recovery(DR)of your existing production data say in
DataCenter 1 to your DR site that may on the other side of the continent,
how do you move all the data acorss the first time? It may be Terrabytes of
data or for that matter even 100s of GBs. It takes so long to move this
backup files for eg: on the network.
We intend to use Log shipping once the backups are restored, but moving
those initial full database backup files is a nightmare.
Can you share how you move your initial data set across ?
FedEx is your friend.
Removable USB disk drives and overnight shipping are still the fastest way
to get very large data sets initialized from one site to another.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Hassan" <hassan@.hotmail.com> wrote in message
news:OejIIuYwHHA.4916@.TK2MSFTNGP04.phx.gbl...
> As you set up disaster recovery(DR)of your existing production data say in
> DataCenter 1 to your DR site that may on the other side of the continent,
> how do you move all the data acorss the first time? It may be Terrabytes
> of data or for that matter even 100s of GBs. It takes so long to move this
> backup files for eg: on the network.
> We intend to use Log shipping once the backups are restored, but moving
> those initial full database backup files is a nightmare.
> Can you share how you move your initial data set across ?
>
|||Can I say DHL ;-)
What I do if the database files are quite big is run a full and transaction
log backup and store it in a backup device. Compress the backup before
sending it over the network using ROBOCOPY. When you configure log
shipping, restore the full and transaction log backups on the DR site and
use an existing database in your option. When it's bigger than 5GB over a
4MBps network, then I would recommend courier
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OlPBX4YwHHA.4640@.TK2MSFTNGP03.phx.gbl...
> FedEx is your friend.
> Removable USB disk drives and overnight shipping are still the fastest way
> to get very large data sets initialized from one site to another.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:OejIIuYwHHA.4916@.TK2MSFTNGP04.phx.gbl...
>
|||Overnighting an external drive is indeed best way to go, imho.
BE SURE TO ENCRYPT THE DATA!!! I would hate to read about yet another
company losing sensitive data! :-0
TheSQLGuru
President
Indicium Resources, Inc.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OlPBX4YwHHA.4640@.TK2MSFTNGP03.phx.gbl...
> FedEx is your friend.
> Removable USB disk drives and overnight shipping are still the fastest way
> to get very large data sets initialized from one site to another.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:OejIIuYwHHA.4916@.TK2MSFTNGP04.phx.gbl...
>

Move large amounts of data across Data Centers for DR

As you set up disaster recovery(DR)of your existing production data say in
DataCenter 1 to your DR site that may on the other side of the continent,
how do you move all the data acorss the first time? It may be Terrabytes of
data or for that matter even 100s of GBs. It takes so long to move this
backup files for eg: on the network.
We intend to use Log shipping once the backups are restored, but moving
those initial full database backup files is a nightmare.
Can you share how you move your initial data set across ?FedEx is your friend.
Removable USB disk drives and overnight shipping are still the fastest way
to get very large data sets initialized from one site to another.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Hassan" <hassan@.hotmail.com> wrote in message
news:OejIIuYwHHA.4916@.TK2MSFTNGP04.phx.gbl...
> As you set up disaster recovery(DR)of your existing production data say in
> DataCenter 1 to your DR site that may on the other side of the continent,
> how do you move all the data acorss the first time? It may be Terrabytes
> of data or for that matter even 100s of GBs. It takes so long to move this
> backup files for eg: on the network.
> We intend to use Log shipping once the backups are restored, but moving
> those initial full database backup files is a nightmare.
> Can you share how you move your initial data set across ?
>|||Can I say DHL ;-)
What I do if the database files are quite big is run a full and transaction
log backup and store it in a backup device. Compress the backup before
sending it over the network using ROBOCOPY. When you configure log
shipping, restore the full and transaction log backups on the DR site and
use an existing database in your option. When it's bigger than 5GB over a
4MBps network, then I would recommend courier :)
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OlPBX4YwHHA.4640@.TK2MSFTNGP03.phx.gbl...
> FedEx is your friend.
> Removable USB disk drives and overnight shipping are still the fastest way
> to get very large data sets initialized from one site to another.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:OejIIuYwHHA.4916@.TK2MSFTNGP04.phx.gbl...
>> As you set up disaster recovery(DR)of your existing production data say
>> in DataCenter 1 to your DR site that may on the other side of the
>> continent, how do you move all the data acorss the first time? It may be
>> Terrabytes of data or for that matter even 100s of GBs. It takes so long
>> to move this backup files for eg: on the network.
>> We intend to use Log shipping once the backups are restored, but moving
>> those initial full database backup files is a nightmare.
>> Can you share how you move your initial data set across ?
>|||Overnighting an external drive is indeed best way to go, imho.
BE SURE TO ENCRYPT THE DATA!!! I would hate to read about yet another
company losing sensitive data! :-0
--
TheSQLGuru
President
Indicium Resources, Inc.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OlPBX4YwHHA.4640@.TK2MSFTNGP03.phx.gbl...
> FedEx is your friend.
> Removable USB disk drives and overnight shipping are still the fastest way
> to get very large data sets initialized from one site to another.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:OejIIuYwHHA.4916@.TK2MSFTNGP04.phx.gbl...
>> As you set up disaster recovery(DR)of your existing production data say
>> in DataCenter 1 to your DR site that may on the other side of the
>> continent, how do you move all the data acorss the first time? It may be
>> Terrabytes of data or for that matter even 100s of GBs. It takes so long
>> to move this backup files for eg: on the network.
>> We intend to use Log shipping once the backups are restored, but moving
>> those initial full database backup files is a nightmare.
>> Can you share how you move your initial data set across ?
>

Move large amounts of data across Data Centers for DR

As you set up disaster recovery(DR)of your existing production data say in
DataCenter 1 to your DR site that may on the other side of the continent,
how do you move all the data acorss the first time? It may be Terrabytes of
data or for that matter even 100s of GBs. It takes so long to move this
backup files for eg: on the network.
We intend to use Log shipping once the backups are restored, but moving
those initial full database backup files is a nightmare.
Can you share how you move your initial data set across ?
FedEx is your friend.
Removable USB disk drives and overnight shipping are still the fastest way
to get very large data sets initialized from one site to another.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Hassan" <hassan@.hotmail.com> wrote in message
news:OejIIuYwHHA.4916@.TK2MSFTNGP04.phx.gbl...
> As you set up disaster recovery(DR)of your existing production data say in
> DataCenter 1 to your DR site that may on the other side of the continent,
> how do you move all the data acorss the first time? It may be Terrabytes
> of data or for that matter even 100s of GBs. It takes so long to move this
> backup files for eg: on the network.
> We intend to use Log shipping once the backups are restored, but moving
> those initial full database backup files is a nightmare.
> Can you share how you move your initial data set across ?
>
|||Can I say DHL ;-)
What I do if the database files are quite big is run a full and transaction
log backup and store it in a backup device. Compress the backup before
sending it over the network using ROBOCOPY. When you configure log
shipping, restore the full and transaction log backups on the DR site and
use an existing database in your option. When it's bigger than 5GB over a
4MBps network, then I would recommend courier
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OlPBX4YwHHA.4640@.TK2MSFTNGP03.phx.gbl...
> FedEx is your friend.
> Removable USB disk drives and overnight shipping are still the fastest way
> to get very large data sets initialized from one site to another.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:OejIIuYwHHA.4916@.TK2MSFTNGP04.phx.gbl...
>
|||Overnighting an external drive is indeed best way to go, imho.
BE SURE TO ENCRYPT THE DATA!!! I would hate to read about yet another
company losing sensitive data! :-0
TheSQLGuru
President
Indicium Resources, Inc.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OlPBX4YwHHA.4640@.TK2MSFTNGP03.phx.gbl...
> FedEx is your friend.
> Removable USB disk drives and overnight shipping are still the fastest way
> to get very large data sets initialized from one site to another.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:OejIIuYwHHA.4916@.TK2MSFTNGP04.phx.gbl...
>

Move large amounts of data across Data Centers for DR

As you set up disaster recovery(DR)of your existing production data say in
DataCenter 1 to your DR site that may on the other side of the continent,
how do you move all the data acorss the first time? It may be Terrabytes of
data or for that matter even 100s of GBs. It takes so long to move this
backup files for eg: on the network.
We intend to use Log shipping once the backups are restored, but moving
those initial full database backup files is a nightmare.
Can you share how you move your initial data set across ?FedEx is your friend.
Removable USB disk drives and overnight shipping are still the fastest way
to get very large data sets initialized from one site to another.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Hassan" <hassan@.hotmail.com> wrote in message
news:OejIIuYwHHA.4916@.TK2MSFTNGP04.phx.gbl...
> As you set up disaster recovery(DR)of your existing production data say in
> DataCenter 1 to your DR site that may on the other side of the continent,
> how do you move all the data acorss the first time? It may be Terrabytes
> of data or for that matter even 100s of GBs. It takes so long to move this
> backup files for eg: on the network.
> We intend to use Log shipping once the backups are restored, but moving
> those initial full database backup files is a nightmare.
> Can you share how you move your initial data set across ?
>|||Can I say DHL ;-)
What I do if the database files are quite big is run a full and transaction
log backup and store it in a backup device. Compress the backup before
sending it over the network using ROBOCOPY. When you configure log
shipping, restore the full and transaction log backups on the DR site and
use an existing database in your option. When it's bigger than 5GB over a
4MBps network, then I would recommend courier
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OlPBX4YwHHA.4640@.TK2MSFTNGP03.phx.gbl...
> FedEx is your friend.
> Removable USB disk drives and overnight shipping are still the fastest way
> to get very large data sets initialized from one site to another.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:OejIIuYwHHA.4916@.TK2MSFTNGP04.phx.gbl...
>|||Overnighting an external drive is indeed best way to go, imho.
BE SURE TO ENCRYPT THE DATA!!! I would hate to read about yet another
company losing sensitive data! :-0
TheSQLGuru
President
Indicium Resources, Inc.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OlPBX4YwHHA.4640@.TK2MSFTNGP03.phx.gbl...
> FedEx is your friend.
> Removable USB disk drives and overnight shipping are still the fastest way
> to get very large data sets initialized from one site to another.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:OejIIuYwHHA.4916@.TK2MSFTNGP04.phx.gbl...
>

Move existing tables to a new Filegroup!

Hi All,
Is there any tools that I can use OR is there any way
that I can move existing tables in PRIMARY group to a new
filegroup programmingly. I have about 500 tables with
data on them that need to be moved to a new filegroup.
Thanks,
tom
If the tables have a clustered index (and most should) you can drop the CI
and recreate it specifying the other Filegroup and it will move the data
over. If you want to move the non-clustered indexes you will have to drop
and recreate them as well. This can all be done programmatically. But be
prepared for it to take a while if there is a lot of data and make sure your
log file can handle the load.
Andrew J. Kelly SQL MVP
"tt" <anonymous@.discussions.microsoft.com> wrote in message
news:480001c47363$df1294f0$a301280a@.phx.gbl...
> Hi All,
> Is there any tools that I can use OR is there any way
> that I can move existing tables in PRIMARY group to a new
> filegroup programmingly. I have about 500 tables with
> data on them that need to be moved to a new filegroup.
> Thanks,
> tom

Move existing table to another file or filegroup

Hi,
is it possible to move existing table to another file or filegroup?
Thanks AlesRe-create the clustered index on that filegroup. If you don't have a cluster
ed index and don't want
to have one, create one on the file group and then drop it.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ales vojacek" <ales vojacek@.discussions.microsoft.com> wrote in message
news:F6788339-43BB-480E-A164-16E313CD32C6@.microsoft.com...
> Hi,
> is it possible to move existing table to another file or filegroup?
> Thanks Ales|||It moves data from whole table to new file group?
Ales
"Tibor Karaszi" wrote:

> Re-create the clustered index on that filegroup. If you don't have a clust
ered index and don't want
> to have one, create one on the file group and then drop it.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ales vojacek" <ales vojacek@.discussions.microsoft.com> wrote in message
> news:F6788339-43BB-480E-A164-16E313CD32C6@.microsoft.com...
>
>|||Yes. A clustered index is the same as the table (or, more formally: the leaf
pages of the clustered
index are the data pages).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ales vojacek" <alesvojacek@.discussions.microsoft.com> wrote in message
news:295FDF4A-623F-42A6-AA3F-0C0623894240@.microsoft.com...[vbcol=seagreen]
> It moves data from whole table to new file group?
> Ales
> "Tibor Karaszi" wrote:
>|||I wrote a script that moves a table to another filegroup, and you can
download it from
http://education.sqlfarms.com/ShowPost.aspx?PostID=59
Note that you can specify whether only data pages, and/or other indexes and
constraints should be moved automatically by the script. It's fairly long,
however it was very well-tested.
Omri Bahat
SQL Farms Solutions
www.sqlfarms.com

Move existing table to another file or filegroup

Hi,
is it possible to move existing table to another file or filegroup?
Thanks Ales
Re-create the clustered index on that filegroup. If you don't have a clustered index and don't want
to have one, create one on the file group and then drop it.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ales vojacek" <ales vojacek@.discussions.microsoft.com> wrote in message
news:F6788339-43BB-480E-A164-16E313CD32C6@.microsoft.com...
> Hi,
> is it possible to move existing table to another file or filegroup?
> Thanks Ales
|||It moves data from whole table to new file group?
Ales
"Tibor Karaszi" wrote:

> Re-create the clustered index on that filegroup. If you don't have a clustered index and don't want
> to have one, create one on the file group and then drop it.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ales vojacek" <ales vojacek@.discussions.microsoft.com> wrote in message
> news:F6788339-43BB-480E-A164-16E313CD32C6@.microsoft.com...
>
>
|||Yes. A clustered index is the same as the table (or, more formally: the leaf pages of the clustered
index are the data pages).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ales vojacek" <alesvojacek@.discussions.microsoft.com> wrote in message
news:295FDF4A-623F-42A6-AA3F-0C0623894240@.microsoft.com...[vbcol=seagreen]
> It moves data from whole table to new file group?
> Ales
> "Tibor Karaszi" wrote:
|||I wrote a script that moves a table to another filegroup, and you can
download it from
http://education.sqlfarms.com/ShowPost.aspx?PostID=59
Note that you can specify whether only data pages, and/or other indexes and
constraints should be moved automatically by the script. It's fairly long,
however it was very well-tested.
Omri Bahat
SQL Farms Solutions
www.sqlfarms.com

Move existing table to another file or filegroup

Hi,
is it possible to move existing table to another file or filegroup?
Thanks AlesRe-create the clustered index on that filegroup. If you don't have a clustered index and don't want
to have one, create one on the file group and then drop it.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ales vojacek" <ales vojacek@.discussions.microsoft.com> wrote in message
news:F6788339-43BB-480E-A164-16E313CD32C6@.microsoft.com...
> Hi,
> is it possible to move existing table to another file or filegroup?
> Thanks Ales|||It moves data from whole table to new file group?
Ales
"Tibor Karaszi" wrote:
> Re-create the clustered index on that filegroup. If you don't have a clustered index and don't want
> to have one, create one on the file group and then drop it.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ales vojacek" <ales vojacek@.discussions.microsoft.com> wrote in message
> news:F6788339-43BB-480E-A164-16E313CD32C6@.microsoft.com...
> > Hi,
> > is it possible to move existing table to another file or filegroup?
> > Thanks Ales
>
>|||Yes. A clustered index is the same as the table (or, more formally: the leaf pages of the clustered
index are the data pages).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ales vojacek" <alesvojacek@.discussions.microsoft.com> wrote in message
news:295FDF4A-623F-42A6-AA3F-0C0623894240@.microsoft.com...
> It moves data from whole table to new file group?
> Ales
> "Tibor Karaszi" wrote:
>> Re-create the clustered index on that filegroup. If you don't have a clustered index and don't
>> want
>> to have one, create one on the file group and then drop it.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "ales vojacek" <ales vojacek@.discussions.microsoft.com> wrote in message
>> news:F6788339-43BB-480E-A164-16E313CD32C6@.microsoft.com...
>> > Hi,
>> > is it possible to move existing table to another file or filegroup?
>> > Thanks Ales
>>|||I wrote a script that moves a table to another filegroup, and you can
download it from
http://education.sqlfarms.com/ShowPost.aspx?PostID=59
Note that you can specify whether only data pages, and/or other indexes and
constraints should be moved automatically by the script. It's fairly long,
however it was very well-tested.
--
Omri Bahat
SQL Farms Solutions
www.sqlfarms.com

Move DTS packages from SQL 2000 to SQL 2005

We have purchased a new Development SQL Server that is running SQL Server 2005. Our existing Development SQL Server is running SQL 2000.

How can I move the DTS packages from the SQL 2000 server to the new SQL 2005 server? I will be upgrading them to SSIS at some point, but don't have the time now.

thanks

sql server 2005 has a package migration wizard that might work for you.

Move DB users

Hi,
I have an already existing DB A, and I created new one B under the same SQL
Server registration. I want to transfer DB "Users" from a to B. How can I
do that? To make myself clear, I am not talking about "Logins"I assume that you are talking about moving logins from one server to
another. I have used this method many times and it works well.
HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
http://www.support.microsoft.com/?id=246133
--
Keith
"SQLServerNewbee" <SQLServerNewbee@.discussions.microsoft.com> wrote in
message news:A4F45400-3FF6-4717-A9DE-D9E0266E20B2@.microsoft.com...
> Hi,
> I have an already existing DB A, and I created new one B under the same
SQL
> Server registration. I want to transfer DB "Users" from a to B. How can
I
> do that? To make myself clear, I am not talking about "Logins"|||No, Keith...I am trying to move Users from dB 'A' to dB 'B'. I know that we
can transfer logins...but how about Users
"Keith Kratochvil" wrote:
> I assume that you are talking about moving logins from one server to
> another. I have used this method many times and it works well.
> HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
> http://www.support.microsoft.com/?id=246133
> --
> Keith
>
> "SQLServerNewbee" <SQLServerNewbee@.discussions.microsoft.com> wrote in
> message news:A4F45400-3FF6-4717-A9DE-D9E0266E20B2@.microsoft.com...
> > Hi,
> > I have an already existing DB A, and I created new one B under the same
> SQL
> > Server registration. I want to transfer DB "Users" from a to B. How can
> I
> > do that? To make myself clear, I am not talking about "Logins"
>|||This should serve as a start:
SELECT 'EXEC sp_grantdbaccess "' + name + '"'
FROM sysusers
WHERE isntname = 1
SELECT 'EXEC sp_adduser "' + name + '"'
FROM sysusers
WHERE issqluser = 1
Run above in source db and execute result in destination db. Above assumes same user name as login
name. If that isn't the case, join sysusers to master..syslogins and pick the login name and use as
second parameter for the sp_ call. Also, this was a quickie, run tests etc and make sure that is
work as expected.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"SQLServerNewbee" <SQLServerNewbee@.discussions.microsoft.com> wrote in message
news:51D4315F-93CE-429C-A13B-5B450E33BEA6@.microsoft.com...
> No, Keith...I am trying to move Users from dB 'A' to dB 'B'. I know that we
> can transfer logins...but how about Users
> "Keith Kratochvil" wrote:
>> I assume that you are talking about moving logins from one server to
>> another. I have used this method many times and it works well.
>> HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
>> http://www.support.microsoft.com/?id=246133
>> --
>> Keith
>>
>> "SQLServerNewbee" <SQLServerNewbee@.discussions.microsoft.com> wrote in
>> message news:A4F45400-3FF6-4717-A9DE-D9E0266E20B2@.microsoft.com...
>> > Hi,
>> > I have an already existing DB A, and I created new one B under the same
>> SQL
>> > Server registration. I want to transfer DB "Users" from a to B. How can
>> I
>> > do that? To make myself clear, I am not talking about "Logins"
>>|||You aren't moving users -- they already exist. You have to grant database
access. Tibor's script should work for you.
--
Keith
"SQLServerNewbee" <SQLServerNewbee@.discussions.microsoft.com> wrote in
message news:51D4315F-93CE-429C-A13B-5B450E33BEA6@.microsoft.com...
> No, Keith...I am trying to move Users from dB 'A' to dB 'B'. I know that
we
> can transfer logins...but how about Users
> "Keith Kratochvil" wrote:
> > I assume that you are talking about moving logins from one server to
> > another. I have used this method many times and it works well.
> >
> > HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
> > http://www.support.microsoft.com/?id=246133
> >
> > --
> > Keith
> >
> >
> > "SQLServerNewbee" <SQLServerNewbee@.discussions.microsoft.com> wrote in
> > message news:A4F45400-3FF6-4717-A9DE-D9E0266E20B2@.microsoft.com...
> > > Hi,
> > > I have an already existing DB A, and I created new one B under the
same
> > SQL
> > > Server registration. I want to transfer DB "Users" from a to B. How
can
> > I
> > > do that? To make myself clear, I am not talking about "Logins"
> >
> >|||Hi Keith, Tibor,
I do not think permissions will be proper after this.. we need to reapply
permissions script... pls confirm
regards,
bharath
"Keith Kratochvil" wrote:
> You aren't moving users -- they already exist. You have to grant database
> access. Tibor's script should work for you.
> --
> Keith
>
> "SQLServerNewbee" <SQLServerNewbee@.discussions.microsoft.com> wrote in
> message news:51D4315F-93CE-429C-A13B-5B450E33BEA6@.microsoft.com...
> > No, Keith...I am trying to move Users from dB 'A' to dB 'B'. I know that
> we
> > can transfer logins...but how about Users
> >
> > "Keith Kratochvil" wrote:
> >
> > > I assume that you are talking about moving logins from one server to
> > > another. I have used this method many times and it works well.
> > >
> > > HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
> > > http://www.support.microsoft.com/?id=246133
> > >
> > > --
> > > Keith
> > >
> > >
> > > "SQLServerNewbee" <SQLServerNewbee@.discussions.microsoft.com> wrote in
> > > message news:A4F45400-3FF6-4717-A9DE-D9E0266E20B2@.microsoft.com...
> > > > Hi,
> > > > I have an already existing DB A, and I created new one B under the
> same
> > > SQL
> > > > Server registration. I want to transfer DB "Users" from a to B. How
> can
> > > I
> > > > do that? To make myself clear, I am not talking about "Logins"
> > >
> > >
>|||Correct. You need to bring over permissions as well. Perhaps it is better to let EM generate scripts
for this and extract the sp_adduser and GRANT commands from the generated scripts...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:669D8883-F7FB-44CE-979B-9487FEEDCFCF@.microsoft.com...
> Hi Keith, Tibor,
> I do not think permissions will be proper after this.. we need to reapply
> permissions script... pls confirm
> regards,
> bharath
> "Keith Kratochvil" wrote:
>> You aren't moving users -- they already exist. You have to grant database
>> access. Tibor's script should work for you.
>> --
>> Keith
>>
>> "SQLServerNewbee" <SQLServerNewbee@.discussions.microsoft.com> wrote in
>> message news:51D4315F-93CE-429C-A13B-5B450E33BEA6@.microsoft.com...
>> > No, Keith...I am trying to move Users from dB 'A' to dB 'B'. I know that
>> we
>> > can transfer logins...but how about Users
>> >
>> > "Keith Kratochvil" wrote:
>> >
>> > > I assume that you are talking about moving logins from one server to
>> > > another. I have used this method many times and it works well.
>> > >
>> > > HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
>> > > http://www.support.microsoft.com/?id=246133
>> > >
>> > > --
>> > > Keith
>> > >
>> > >
>> > > "SQLServerNewbee" <SQLServerNewbee@.discussions.microsoft.com> wrote in
>> > > message news:A4F45400-3FF6-4717-A9DE-D9E0266E20B2@.microsoft.com...
>> > > > Hi,
>> > > > I have an already existing DB A, and I created new one B under the
>> same
>> > > SQL
>> > > > Server registration. I want to transfer DB "Users" from a to B. How
>> can
>> > > I
>> > > > do that? To make myself clear, I am not talking about "Logins"
>> > >
>> > >
>>

Move DB users

Hi,
I have an already existing DB A, and I created new one B under the same SQL
Server registration. I want to transfer DB "Users" from a to B. How can I
do that? To make myself clear, I am not talking about "Logins"
I assume that you are talking about moving logins from one server to
another. I have used this method many times and it works well.
HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
http://www.support.microsoft.com/?id=246133
Keith
"SQLServerNewbee" <SQLServerNewbee@.discussions.microsoft.com> wrote in
message news:A4F45400-3FF6-4717-A9DE-D9E0266E20B2@.microsoft.com...
> Hi,
> I have an already existing DB A, and I created new one B under the same
SQL
> Server registration. I want to transfer DB "Users" from a to B. How can
I
> do that? To make myself clear, I am not talking about "Logins"
|||No, Keith...I am trying to move Users from dB 'A' to dB 'B'. I know that we
can transfer logins...but how about Users
"Keith Kratochvil" wrote:

> I assume that you are talking about moving logins from one server to
> another. I have used this method many times and it works well.
> HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
> http://www.support.microsoft.com/?id=246133
> --
> Keith
>
> "SQLServerNewbee" <SQLServerNewbee@.discussions.microsoft.com> wrote in
> message news:A4F45400-3FF6-4717-A9DE-D9E0266E20B2@.microsoft.com...
> SQL
> I
>
|||This should serve as a start:
SELECT 'EXEC sp_grantdbaccess "' + name + '"'
FROM sysusers
WHERE isntname = 1
SELECT 'EXEC sp_adduser "' + name + '"'
FROM sysusers
WHERE issqluser = 1
Run above in source db and execute result in destination db. Above assumes same user name as login
name. If that isn't the case, join sysusers to master..syslogins and pick the login name and use as
second parameter for the sp_ call. Also, this was a quickie, run tests etc and make sure that is
work as expected.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"SQLServerNewbee" <SQLServerNewbee@.discussions.microsoft.com> wrote in message
news:51D4315F-93CE-429C-A13B-5B450E33BEA6@.microsoft.com...[vbcol=seagreen]
> No, Keith...I am trying to move Users from dB 'A' to dB 'B'. I know that we
> can transfer logins...but how about Users
> "Keith Kratochvil" wrote:
|||You aren't moving users -- they already exist. You have to grant database
access. Tibor's script should work for you.
Keith
"SQLServerNewbee" <SQLServerNewbee@.discussions.microsoft.com> wrote in
message news:51D4315F-93CE-429C-A13B-5B450E33BEA6@.microsoft.com...
> No, Keith...I am trying to move Users from dB 'A' to dB 'B'. I know that
we[vbcol=seagreen]
> can transfer logins...but how about Users
> "Keith Kratochvil" wrote:
same[vbcol=seagreen]
can[vbcol=seagreen]
|||Hi Keith, Tibor,
I do not think permissions will be proper after this.. we need to reapply
permissions script... pls confirm
regards,
bharath
"Keith Kratochvil" wrote:

> You aren't moving users -- they already exist. You have to grant database
> access. Tibor's script should work for you.
> --
> Keith
>
> "SQLServerNewbee" <SQLServerNewbee@.discussions.microsoft.com> wrote in
> message news:51D4315F-93CE-429C-A13B-5B450E33BEA6@.microsoft.com...
> we
> same
> can
>
|||Correct. You need to bring over permissions as well. Perhaps it is better to let EM generate scripts
for this and extract the sp_adduser and GRANT commands from the generated scripts...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:669D8883-F7FB-44CE-979B-9487FEEDCFCF@.microsoft.com...[vbcol=seagreen]
> Hi Keith, Tibor,
> I do not think permissions will be proper after this.. we need to reapply
> permissions script... pls confirm
> regards,
> bharath
> "Keith Kratochvil" wrote:

Move DB users

Hi,
I have an already existing DB A, and I created new one B under the same SQL
Server registration. I want to transfer DB "Users" from a to B. How can I
do that? To make myself clear, I am not talking about "Logins"I assume that you are talking about moving logins from one server to
another. I have used this method many times and it works well.
HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
http://www.support.microsoft.com/?id=246133
Keith
"SQLServerNewbee" <SQLServerNewbee@.discussions.microsoft.com> wrote in
message news:A4F45400-3FF6-4717-A9DE-D9E0266E20B2@.microsoft.com...
> Hi,
> I have an already existing DB A, and I created new one B under the same
SQL
> Server registration. I want to transfer DB "Users" from a to B. How can
I
> do that? To make myself clear, I am not talking about "Logins"|||No, Keith...I am trying to move Users from dB 'A' to dB 'B'. I know that we
can transfer logins...but how about Users
"Keith Kratochvil" wrote:

> I assume that you are talking about moving logins from one server to
> another. I have used this method many times and it works well.
> HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
> http://www.support.microsoft.com/?id=246133
> --
> Keith
>
> "SQLServerNewbee" <SQLServerNewbee@.discussions.microsoft.com> wrote in
> message news:A4F45400-3FF6-4717-A9DE-D9E0266E20B2@.microsoft.com...
> SQL
> I
>|||This should serve as a start:
SELECT 'EXEC sp_grantdbaccess "' + name + '"'
FROM sysusers
WHERE isntname = 1
SELECT 'EXEC sp_adduser "' + name + '"'
FROM sysusers
WHERE issqluser = 1
Run above in source db and execute result in destination db. Above assumes s
ame user name as login
name. If that isn't the case, join sysusers to master..syslogins and pick th
e login name and use as
second parameter for the sp_ call. Also, this was a quickie, run tests etc a
nd make sure that is
work as expected.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"SQLServerNewbee" <SQLServerNewbee@.discussions.microsoft.com> wrote in messa
ge
news:51D4315F-93CE-429C-A13B-5B450E33BEA6@.microsoft.com...[vbcol=seagreen]
> No, Keith...I am trying to move Users from dB 'A' to dB 'B'. I know that
we
> can transfer logins...but how about Users
> "Keith Kratochvil" wrote:
>|||You aren't moving users -- they already exist. You have to grant database
access. Tibor's script should work for you.
Keith
"SQLServerNewbee" <SQLServerNewbee@.discussions.microsoft.com> wrote in
message news:51D4315F-93CE-429C-A13B-5B450E33BEA6@.microsoft.com...
> No, Keith...I am trying to move Users from dB 'A' to dB 'B'. I know that
we[vbcol=seagreen]
> can transfer logins...but how about Users
> "Keith Kratochvil" wrote:
>
same[vbcol=seagreen]
can[vbcol=seagreen]|||Hi Keith, Tibor,
I do not think permissions will be proper after this.. we need to reapply
permissions script... pls confirm
regards,
bharath
"Keith Kratochvil" wrote:

> You aren't moving users -- they already exist. You have to grant database
> access. Tibor's script should work for you.
> --
> Keith
>
> "SQLServerNewbee" <SQLServerNewbee@.discussions.microsoft.com> wrote in
> message news:51D4315F-93CE-429C-A13B-5B450E33BEA6@.microsoft.com...
> we
> same
> can
>|||Correct. You need to bring over permissions as well. Perhaps it is better to
let EM generate scripts
for this and extract the sp_adduser and GRANT commands from the generated sc
ripts...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:669D8883-F7FB-44CE-979B-9487FEEDCFCF@.microsoft.com...[vbcol=seagreen]
> Hi Keith, Tibor,
> I do not think permissions will be proper after this.. we need to reapply
> permissions script... pls confirm
> regards,
> bharath
> "Keith Kratochvil" wrote:
>

Move database to new drive w/ same drive letter

Hi all,
I want to move several database files from a small drive to a new one and replace the existing (small) drive with the bigger one.
The drive letter would not change.
Can I just go ahead and boot the server w/o the SQL service running, copy the folders to the new drive, pull out the old drive and replace it with the new one or do I have to go through the whole attach/detach schema as described in http://support.microso
ft.com/default.aspx?scid=KB;EN-US;q224071&ID=KB;EN-US;q224071 ?
Thanks!
Andreas
You don't have to detach/attach... As long as the drive letter and path is
the same, there shouldn't be any problems as long as SQL is shutdown
cleanly.
"Andi" <anonymous@.discussions.microsoft.com> wrote in message
news:A3410D22-0CFC-469E-8BC0-515D3B1A83AF@.microsoft.com...
> Hi all,
> I want to move several database files from a small drive to a new one and
replace the existing (small) drive with the bigger one.
> The drive letter would not change.
> Can I just go ahead and boot the server w/o the SQL service running, copy
the folders to the new drive, pull out the old drive and replace it with the
new one or do I have to go through the whole attach/detach schema as
described in
http://support.microsoft.com/default...;EN-US;q224071 ?
> Thanks!
> Andreas

Move database to new drive w/ same drive letter

Hi all,
I want to move several database files from a small drive to a new one and re
place the existing (small) drive with the bigger one.
The drive letter would not change.
Can I just go ahead and boot the server w/o the SQL service running, copy the folders t
o the new drive, pull out the old drive and replace it with the new one or do I have to
go through the whole attach/detach schema as described in [url]http://support.microso[
/url]
ft.com/default.aspx?scid=KB;EN-US;q224071&ID=KB;EN-US;q224071 ?
Thanks!
AndreasYou don't have to detach/attach... As long as the drive letter and path is
the same, there shouldn't be any problems as long as SQL is shutdown
cleanly.
"Andi" <anonymous@.discussions.microsoft.com> wrote in message
news:A3410D22-0CFC-469E-8BC0-515D3B1A83AF@.microsoft.com...
> Hi all,
> I want to move several database files from a small drive to a new one and
replace the existing (small) drive with the bigger one.
> The drive letter would not change.
> Can I just go ahead and boot the server w/o the SQL service running, copy
the folders to the new drive, pull out the old drive and replace it with the
new one or do I have to go through the whole attach/detach schema as
described in
http://support.microsoft.com/defaul...B;EN-US;q224071 ?seagreen">
> Thanks!
> Andreas

Move database to new drive w/ same drive letter

Hi all
I want to move several database files from a small drive to a new one and replace the existing (small) drive with the bigger one
The drive letter would not change
Can I just go ahead and boot the server w/o the SQL service running, copy the folders to the new drive, pull out the old drive and replace it with the new one or do I have to go through the whole attach/detach schema as described in http://support.microsoft.com/default.aspx?scid=KB;EN-US;q224071&ID=KB;EN-US;q224071
Thanks
AndreasYou don't have to detach/attach... As long as the drive letter and path is
the same, there shouldn't be any problems as long as SQL is shutdown
cleanly.
"Andi" <anonymous@.discussions.microsoft.com> wrote in message
news:A3410D22-0CFC-469E-8BC0-515D3B1A83AF@.microsoft.com...
> Hi all,
> I want to move several database files from a small drive to a new one and
replace the existing (small) drive with the bigger one.
> The drive letter would not change.
> Can I just go ahead and boot the server w/o the SQL service running, copy
the folders to the new drive, pull out the old drive and replace it with the
new one or do I have to go through the whole attach/detach schema as
described in
http://support.microsoft.com/default.aspx?scid=KB;EN-US;q224071&ID=KB;EN-US;q224071 ?
> Thanks!
> Andreas