Moving a Windows 2003 Cluster to a New Forest

I am looking to decomission an old AD forest and move all it's resources to a
new AD forest. Both forests exist today. I have a 2 node Windows 2003
cluster with 3 resource groups -- the cluster resource group and two (2) SQL
2000 server resource groups.
My questions are...
1) Is this sort of migration possible/support?
2) If so, how do I go about doing it (or finding out how to do it).
Thanks.
Bill
How to change domains for a SQL Server 2000 or SQL Server 2005 failover
cluster
http://support.microsoft.com/kb/319016/en-us
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Bill J." <Bill J.@.discussions.microsoft.com> wrote in message
news:77BA4242-BDBB-4A83-9A46-52F57A055F2F@.microsoft.com...
>I am looking to decomission an old AD forest and move all it's resources to
>a
> new AD forest. Both forests exist today. I have a 2 node Windows 2003
> cluster with 3 resource groups -- the cluster resource group and two (2)
> SQL
> 2000 server resource groups.
> My questions are...
> 1) Is this sort of migration possible/support?
> 2) If so, how do I go about doing it (or finding out how to do it).
> Thanks.
> Bill
sql

Moving a database to a new drive

I have a CRM 3.0 application running on a Windows server 2003 R2 and SQL
2005. I need to move the database and log file to a different drive from the
current location. It is currently on C: which is the system partion. I need
to move the log file and data file to H and I respectively.
The database has one filegroup, Primary. It has one datafile in the primary
filegroup, and one log file. I need to move these files to drives H and I
respectively.
Will someone be able to point me in the right direction on how to move this
files?
Thanks in advance.
ODINF: Moving SQL Server Databases to a New Location with Detach/Attach
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q224071
--
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"OD" <oludan@.hotmail.com> wrote in message
news:%238v5kKd0GHA.1252@.TK2MSFTNGP04.phx.gbl...
>I have a CRM 3.0 application running on a Windows server 2003 R2 and SQL
>2005. I need to move the database and log file to a different drive from
>the current location. It is currently on C: which is the system partion. I
>need to move the log file and data file to H and I respectively.
> The database has one filegroup, Primary. It has one datafile in the
> primary filegroup, and one log file. I need to move these files to drives
> H and I respectively.
> Will someone be able to point me in the right direction on how to move
> this files?
> Thanks in advance.
> OD
>|||See reply in sqlserver.tools
--
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"OD" <oludan@.hotmail.com> wrote in message
news:%238v5kKd0GHA.1252@.TK2MSFTNGP04.phx.gbl...
>I have a CRM 3.0 application running on a Windows server 2003 R2 and SQL
>2005. I need to move the database and log file to a different drive from
>the current location. It is currently on C: which is the system partion. I
>need to move the log file and data file to H and I respectively.
> The database has one filegroup, Primary. It has one datafile in the
> primary filegroup, and one log file. I need to move these files to drives
> H and I respectively.
> Will someone be able to point me in the right direction on how to move
> this files?
> Thanks in advance.
> OD
>|||Thanks Jasper. You have provided the exact information that I am searching.
For some reason I couldn't find it on microsoft's Web site.
Thanks again,
OD
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:e7LOZPd0GHA.720@.TK2MSFTNGP02.phx.gbl...
> See reply in sqlserver.tools
> --
> HTH,
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
>
> "OD" <oludan@.hotmail.com> wrote in message
> news:%238v5kKd0GHA.1252@.TK2MSFTNGP04.phx.gbl...
>>I have a CRM 3.0 application running on a Windows server 2003 R2 and SQL
>>2005. I need to move the database and log file to a different drive from
>>the current location. It is currently on C: which is the system partion. I
>>need to move the log file and data file to H and I respectively.
>> The database has one filegroup, Primary. It has one datafile in the
>> primary filegroup, and one log file. I need to move these files to drives
>> H and I respectively.
>> Will someone be able to point me in the right direction on how to move
>> this files?
>> Thanks in advance.
>> OD
>|||You could take a look at KBArticle
http://msdn2.microsoft.com/en-us/library/ms187858.aspx
--
Thanks
Sethu Srinivasan, Software Design Engineer, SQL Server Manageability
--
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.
"OD" <oludan@.hotmail.com> wrote in message
news:%238v5kKd0GHA.1252@.TK2MSFTNGP04.phx.gbl...
>I have a CRM 3.0 application running on a Windows server 2003 R2 and SQL
>2005. I need to move the database and log file to a different drive from
>the current location. It is currently on C: which is the system partion. I
>need to move the log file and data file to H and I respectively.
> The database has one filegroup, Primary. It has one datafile in the
> primary filegroup, and one log file. I need to move these files to drives
> H and I respectively.
> Will someone be able to point me in the right direction on how to move
> this files?
> Thanks in advance.
> OD
>

Moving a database to a new drive

I have a CRM 3.0 application running on a Windows server 2003 R2 and SQL
2005. I need to move the database and log file to a different drive from the
current location. It is currently on C: which is the system partion. I need
to move the log file and data file to H and I respectively.
The database has one filegroup, Primary. It has one datafile in the primary
filegroup, and one log file. I need to move these files to drives H and I
respectively.
Will someone be able to point me in the right direction on how to move this
files?
Thanks in advance.
ODINF: Moving SQL Server Databases to a New Location with Detach/Attach
http://support.microsoft.com/defaul...b;EN-US;q224071
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"OD" <oludan@.hotmail.com> wrote in message
news:%238v5kKd0GHA.1252@.TK2MSFTNGP04.phx.gbl...
>I have a CRM 3.0 application running on a Windows server 2003 R2 and SQL
>2005. I need to move the database and log file to a different drive from
>the current location. It is currently on C: which is the system partion. I
>need to move the log file and data file to H and I respectively.
> The database has one filegroup, Primary. It has one datafile in the
> primary filegroup, and one log file. I need to move these files to drives
> H and I respectively.
> Will someone be able to point me in the right direction on how to move
> this files?
> Thanks in advance.
> OD
>|||See reply in sqlserver.tools
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"OD" <oludan@.hotmail.com> wrote in message
news:%238v5kKd0GHA.1252@.TK2MSFTNGP04.phx.gbl...
>I have a CRM 3.0 application running on a Windows server 2003 R2 and SQL
>2005. I need to move the database and log file to a different drive from
>the current location. It is currently on C: which is the system partion. I
>need to move the log file and data file to H and I respectively.
> The database has one filegroup, Primary. It has one datafile in the
> primary filegroup, and one log file. I need to move these files to drives
> H and I respectively.
> Will someone be able to point me in the right direction on how to move
> this files?
> Thanks in advance.
> OD
>|||Thanks Jasper. You have provided the exact information that I am searching.
For some reason I couldn't find it on microsoft's Web site.
Thanks again,
OD
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:e7LOZPd0GHA.720@.TK2MSFTNGP02.phx.gbl...
> See reply in sqlserver.tools
> --
> HTH,
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
>
> "OD" <oludan@.hotmail.com> wrote in message
> news:%238v5kKd0GHA.1252@.TK2MSFTNGP04.phx.gbl...
>|||You could take a look at KBArticle
http://msdn2.microsoft.com/en-us/library/ms187858.aspx
Thanks
Sethu Srinivasan, Software Design Engineer, SQL Server Manageability
--
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.
"OD" <oludan@.hotmail.com> wrote in message
news:%238v5kKd0GHA.1252@.TK2MSFTNGP04.phx.gbl...
>I have a CRM 3.0 application running on a Windows server 2003 R2 and SQL
>2005. I need to move the database and log file to a different drive from
>the current location. It is currently on C: which is the system partion. I
>need to move the log file and data file to H and I respectively.
> The database has one filegroup, Primary. It has one datafile in the
> primary filegroup, and one log file. I need to move these files to drives
> H and I respectively.
> Will someone be able to point me in the right direction on how to move
> this files?
> Thanks in advance.
> OD
>

Move TempDB Database off of the SAN

I have a system configured with Windows 2000 and SQL Server 2000
Clustering (active/passive). Both SQL Servers have a local E:\ drive
with the same directory structure. I would like to move the tempdb
off of the shared SAN and on to the E:\ drive. I don't foresee any
issues with this but wanted to know if anyone else has encountered
problems with this.
Conceivable it should work but would not be a supported configuration.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||If you would like to put tempdb on a different disk (for performance reasons)
you'd be better to create a new disk on a different disk pool on your SAN.
That way, you'd keep your support options open.
|||> I have a system configured with Windows 2000 and SQL Server 2000
> Clustering (active/passive). Both SQL Servers have a local E:\ drive
> with the same directory structure. I would like to move the tempdb
> off of the shared SAN and on to the E:\ drive. I don't foresee any
> issues with this but wanted to know if anyone else has encountered
> problems with this.
I am vaguely trying to do the same. But how do you plan to make your local
disk visible as a resource of the cluster ? If you cannot make it a
resource of the cluster, you cannot make it recognized...
I am trying to add it as a disk share resource, but it is not accepted by
SQL Server in cluster, even with trace flag 1807.
Did someone manage do do it ?
thanks in advance,
rudi

Move TempDB Database off of the SAN

I have a system configured with Windows 2000 and SQL Server 2000
Clustering (active/passive). Both SQL Servers have a local E:\ drive
with the same directory structure. I would like to move the tempdb
off of the shared SAN and on to the E:\ drive. I don't foresee any
issues with this but wanted to know if anyone else has encountered
problems with this."Douglara" <renee.douglas@.ps.net> wrote in message
news:afc82404.0408231344.1f60247d@.posting.google.c om...
> I have a system configured with Windows 2000 and SQL Server 2000
> Clustering (active/passive). Both SQL Servers have a local E:\ drive
> with the same directory structure. I would like to move the tempdb
> off of the shared SAN and on to the E:\ drive. I don't foresee any
> issues with this but wanted to know if anyone else has encountered
> problems with this.

In theory it should work since the tempdb is recreated at startup.

But I'd ask why? I'm assuming you're looking for a performance improvement?

And suggest asking over in the microsoft.public.sqlserver.clustering group
to be sure.

Move TempDB data/trans From C: to E:

I have a SQL Server 2000 database server on Windows 2000 Advanced Server.
What is the best way to move the TempDB data and transaction log files from
the C: to E: drive?
Thank You,I'm very interested in this as well. We were planning on doing this first
thing Saturday morning.
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:D7969E35-E4D2-4D22-A9BB-DD7B52EA6E2D@.microsoft.com...
> I have a SQL Server 2000 database server on Windows 2000 Advanced Server.
> What is the best way to move the TempDB data and transaction log files
> from
> the C: to E: drive?
> Thank You,|||Here ya go....BOL...just tried it and it worked great.
1. stop sql server
2. copy to your desired location
3. start sql server
4. run the alter statements below
5. restart sql server
USE master;
GO
ALTER DATABASE tempdb
MODIFY FILE (NAME = tempdev, FILENAME = 'E:\SQLData\tempdb.mdf');
GO
ALTER DATABASE tempdb
MODIFY FILE (NAME = templog, FILENAME = 'E:\SQLData\templog.ldf');
GO
"Tim Greenwood" <tim_greenwood A-T yahoo D-O-T com> wrote in message
news:uPtIzWxaGHA.2124@.TK2MSFTNGP03.phx.gbl...
> I'm very interested in this as well. We were planning on doing this first
> thing Saturday morning.
>
> "Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
> news:D7969E35-E4D2-4D22-A9BB-DD7B52EA6E2D@.microsoft.com...
>> I have a SQL Server 2000 database server on Windows 2000 Advanced Server.
>> What is the best way to move the TempDB data and transaction log files
>> from
>> the C: to E: drive?
>> Thank You,
>|||Hi Tim
What exactly are you doing in step 2? You shouldn't have to move anything,
since the tempdb files are recreated upon system startup. To move tempdb you
just need to run ALTER DATABASE and then restart your SQL Server.
--
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Tim Greenwood" <tim_greenwood A-T yahoo D-O-T com> wrote in message
news:uRzZ4dxaGHA.3408@.TK2MSFTNGP04.phx.gbl...
> Here ya go....BOL...just tried it and it worked great.
> 1. stop sql server
> 2. copy to your desired location
> 3. start sql server
> 4. run the alter statements below
> 5. restart sql server
> USE master;
> GO
> ALTER DATABASE tempdb
> MODIFY FILE (NAME = tempdev, FILENAME = 'E:\SQLData\tempdb.mdf');
> GO
> ALTER DATABASE tempdb
> MODIFY FILE (NAME = templog, FILENAME = 'E:\SQLData\templog.ldf');
> GO
> "Tim Greenwood" <tim_greenwood A-T yahoo D-O-T com> wrote in message
> news:uPtIzWxaGHA.2124@.TK2MSFTNGP03.phx.gbl...
>> I'm very interested in this as well. We were planning on doing this
>> first thing Saturday morning.
>>
>> "Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
>> news:D7969E35-E4D2-4D22-A9BB-DD7B52EA6E2D@.microsoft.com...
>> I have a SQL Server 2000 database server on Windows 2000 Advanced
>> Server.
>> What is the best way to move the TempDB data and transaction log files
>> from
>> the C: to E: drive?
>> Thank You,
>>
>|||I was doing the steps as outlined in BOL...and I quote from BOL
G. Moving tempdb to a new location
The following example moves tempdb from its current location on disk to
another disk location.
1.. Determine the logical file names of the tempdb database and their
current location on disk.
SELECT name, physical_name
FROM sys.master_files
WHERE database_id = DB_ID('tempdb');
GO
2.. Physically move these files to the new location E:\SQLData.
In this example the new location specified for the tempdb files is
E:\SQLData. If you move the files to different location, modify the example
to point to that location.
3.. Change the location of each file by using ALTER DATABASE.
4.. Stop and restart the instance of SQL Server.
5.. Verify the file change.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:uG0CSzxaGHA.1192@.TK2MSFTNGP03.phx.gbl...
> Hi Tim
> What exactly are you doing in step 2? You shouldn't have to move anything,
> since the tempdb files are recreated upon system startup. To move tempdb
> you just need to run ALTER DATABASE and then restart your SQL Server.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.solidqualitylearning.com
>
> "Tim Greenwood" <tim_greenwood A-T yahoo D-O-T com> wrote in message
> news:uRzZ4dxaGHA.3408@.TK2MSFTNGP04.phx.gbl...
>> Here ya go....BOL...just tried it and it worked great.
>> 1. stop sql server
>> 2. copy to your desired location
>> 3. start sql server
>> 4. run the alter statements below
>> 5. restart sql server
>> USE master;
>> GO
>> ALTER DATABASE tempdb
>> MODIFY FILE (NAME = tempdev, FILENAME = 'E:\SQLData\tempdb.mdf');
>> GO
>> ALTER DATABASE tempdb
>> MODIFY FILE (NAME = templog, FILENAME = 'E:\SQLData\templog.ldf');
>> GO
>> "Tim Greenwood" <tim_greenwood A-T yahoo D-O-T com> wrote in message
>> news:uPtIzWxaGHA.2124@.TK2MSFTNGP03.phx.gbl...
>> I'm very interested in this as well. We were planning on doing this
>> first thing Saturday morning.
>>
>> "Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
>> news:D7969E35-E4D2-4D22-A9BB-DD7B52EA6E2D@.microsoft.com...
>> I have a SQL Server 2000 database server on Windows 2000 Advanced
>> Server.
>> What is the best way to move the TempDB data and transaction log files
>> from
>> the C: to E: drive?
>> Thank You,
>>
>>
>|||This is a multi-part message in MIME format.
--=_NextPart_000_0368_01C66B08.B9F88460
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi Tim
Just FYI, you do not have to move any files to move tempdb, because =tempdb is rebuilt every time SQL Server starts.
Do you have the latest BOL? There was a refresh just a week ago.
G. Moving tempdb to a new location
The following example moves tempdb from its current location on the disk =to another disk location. Because tempdb is re-created each time the =MSSQLSERVER service is started, you do not have to physically move the =data and log files. The files are created when the service is restarted =in step 3. Until the service is restarted, tempdb continues to function =in its existing location.
1.. Determine the logical file names of the tempdb database and their =current location on disk.
SELECT name, physical_name
FROM sys.master_files
WHERE database_id =3D DB_ID('tempdb');
GO
2.. Change the location of each file by using ALTER DATABASE.
USE master;
GO
ALTER DATABASE tempdb MODIFY FILE (NAME =3D tempdev, FILENAME =3D 'E:\SQLData\tempdb.mdf');
GO
ALTER DATABASE tempdb MODIFY FILE (NAME =3D templog, FILENAME =3D 'E:\SQLData\templog.ldf');
GO
3.. Stop and restart the instance of SQL Server.
4.. Verify the file change.
SELECT name, physical_name
FROM sys.master_files
WHERE database_id =3D DB_ID('tempdb');
5.. Delete the tempdb.mdf and templog.ldf files from their original =location.
-- HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Tim Greenwood" <tim_greenwood A-T yahoo D-O-T com> wrote in message =news:%23TTfa5zaGHA.1196@.TK2MSFTNGP03.phx.gbl...
>I was doing the steps as outlined in BOL...and I quote from BOL
> > G. Moving tempdb to a new location
> The following example moves tempdb from its current location on disk =to > another disk location.
> > 1.. Determine the logical file names of the tempdb database and their =
> current location on disk.
> > > > SELECT name, physical_name
> FROM sys.master_files
> WHERE database_id =3D DB_ID('tempdb');
> GO
> > 2.. Physically move these files to the new location E:\SQLData.
> > > > In this example the new location specified for the tempdb files =is > E:\SQLData. If you move the files to different location, modify the =example > to point to that location.
> > > > 3.. Change the location of each file by using ALTER DATABASE.
> > 4.. Stop and restart the instance of SQL Server.
> > > 5.. Verify the file change.
> > > > > "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message > news:uG0CSzxaGHA.1192@.TK2MSFTNGP03.phx.gbl...
>> Hi Tim
>> What exactly are you doing in step 2? You shouldn't have to move =anything, >> since the tempdb files are recreated upon system startup. To move =tempdb >> you just need to run ALTER DATABASE and then restart your SQL Server.
>> -- >> HTH
>> Kalen Delaney, SQL Server MVP
>> www.solidqualitylearning.com
>>
>> "Tim Greenwood" <tim_greenwood A-T yahoo D-O-T com> wrote in message >> news:uRzZ4dxaGHA.3408@.TK2MSFTNGP04.phx.gbl...
>> Here ya go....BOL...just tried it and it worked great.
>> 1. stop sql server
>> 2. copy to your desired location
>> 3. start sql server
>> 4. run the alter statements below
>> 5. restart sql server
>> USE master;
>> GO
>> ALTER DATABASE tempdb
>> MODIFY FILE (NAME =3D tempdev, FILENAME =3D ='E:\SQLData\tempdb.mdf');
>> GO
>> ALTER DATABASE tempdb
>> MODIFY FILE (NAME =3D templog, FILENAME =3D ='E:\SQLData\templog.ldf');
>> GO
>> "Tim Greenwood" <tim_greenwood A-T yahoo D-O-T com> wrote in message =
>> news:uPtIzWxaGHA.2124@.TK2MSFTNGP03.phx.gbl...
>> I'm very interested in this as well. We were planning on doing =this >> first thing Saturday morning.
>>
>> "Joe K." <Joe K.@.discussions.microsoft.com> wrote in message >> news:D7969E35-E4D2-4D22-A9BB-DD7B52EA6E2D@.microsoft.com...
>> I have a SQL Server 2000 database server on Windows 2000 Advanced >> Server.
>> What is the best way to move the TempDB data and transaction log =files >> from
>> the C: to E: drive?
>> Thank You,
>>
>>
>> > >
--=_NextPart_000_0368_01C66B08.B9F88460
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

Hi Tim
Just FYI, you do not have to move any =files to move tempdb, because tempdb is rebuilt every time SQL Server =starts.
Do you have the latest BOL? There was a =refresh just a week ago.
G. Moving =tempdb to a new location
http://ddue.schemas.microsoft.com/authoring/2003/5">
The following example moves =tempdb from its current location on the disk to another disk location. Because tempdb is re-created each time the MSSQLSERVER =service is started, you do not have to physically move the data and log =files. The files are created when the service is restarted in step 3. Until the =service is restarted, tempdb continues to function in its existing =location.
Determine the logical file names of =the tempdb database and their current location on disk.
SELECT name, =physical_name
FROM sys.master_files
WHERE database_id =3D DB_ID('tempdb');
GO
Change the location of each file by =using ALTER DATABASE.
USE master;
GO
ALTER DATABASE tempdb MODIFY FILE (NAME =3D tempdev, FILENAME =3D 'E:\SQLData\tempdb.mdf');
GO
ALTER DATABASE tempdb MODIFY FILE (NAME =3D templog, FILENAME =3D 'E:\SQLData\templog.ldf');
GO
Stop and restart the instance of SQL =Server.
Verify the file change.
SELECT name, =physical_name
FROM sys.master_files
WHERE database_id =3D =DB_ID('tempdb');
Delete the tempdb.mdf and templog.ldf =files from their original location.
-- HTHKalen Delaney, SQL =Server MVPwww.solidqualitylearning.com
"Tim Greenwood" wrote in message news:%23TTfa5zaGHA.1196@.TK2MSFTNGP03.phx.gbl...>I was doing the =steps as outlined in BOL...and I quote from BOL> > G. Moving =tempdb to a new location> The following example moves tempdb from its current =location on disk to > another disk location.> => 1.. Determine the logical file names of the tempdb database and their => current location on disk.> > > > SELECT =name, physical_name> FROM sys.master_files> WHERE database_id ==3D DB_ID('tempdb');> GO> > 2.. Physically move =these files to the new location E:\SQLData.> > > > In this example the =new location specified for the tempdb files is > E:\SQLData. If you =move the files to different location, modify the example > to point to =that location.> > > > 3.. Change the =location of each file by using ALTER DATABASE.> > 4.. Stop and =restart the instance of SQL Server.> > > 5.. Verify =the file change.> > > > > "Kalen Delaney" wrote in message > news:uG0CSzxaGHA.1192@.TK2MSFTNGP03.phx.gbl...> Hi Tim>> What exactly are =you doing in step 2? You shouldn't have to move anything, > since the =tempdb files are recreated upon system startup. To move tempdb > you =just need to run ALTER DATABASE and then restart your SQL Server.>> -- > HTH> Kalen =Delaney, SQL Server MVP>www.solidqualitylearning.com>>> "Tim Greenwood" = wrote in message > news:uRzZ4dxaGHA.3408@.TK2MSFTNGP04.phx.gbl...> Here ya go....BOL...just tried it and it =worked great.> 1. stop sql server> 2. copy to =your desired location> 3. start sql server> 4. =run the alter statements below> 5. restart sql server>> USE master;> GO> ALTER DATABASE tempdb> MODIFY FILE =(NAME =3D tempdev, FILENAME =3D 'E:\SQLData\tempdb.mdf');> =GO> ALTER DATABASE tempdb> MODIFY FILE (NAME =3D =templog, FILENAME =3D 'E:\SQLData\templog.ldf');> GO>> "Tim Greenwood" wrote in message > news:uPtIzWxaGHA.2124@.TK2MSFTNGP03.phx.gbl...> I'm very interested in this as =well. We were planning on doing this > first thing Saturday morning.>>>&=gt;>> "Joe K." wrote in message > news:D7969E35-E4D2-4D22-A9BB-DD7B52EA6E2D@.microsoft.com...>> I have a SQL Server 2000 database server on Windows 2000 Advanced > =Server.>> What is the best way to move the TempDB data and transaction log files > from> the C: to E: drive?>> Thank You,>>>>&=gt;>> > >

---

--=_NextPart_000_0368_01C66B08.B9F88460--sql

Move TempDB data/trans From C: to E:

I have a SQL Server 2000 database server on Windows 2000 Advanced Server.
What is the best way to move the TempDB data and transaction log files from
the C: to E: drive?
Thank You,I'm very interested in this as well. We were planning on doing this first
thing Saturday morning.
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:D7969E35-E4D2-4D22-A9BB-DD7B52EA6E2D@.microsoft.com...
> I have a SQL Server 2000 database server on Windows 2000 Advanced Server.
> What is the best way to move the TempDB data and transaction log files
> from
> the C: to E: drive?
> Thank You,|||Here ya go....BOL...just tried it and it worked great.
1. stop sql server
2. copy to your desired location
3. start sql server
4. run the alter statements below
5. restart sql server
USE master;
GO
ALTER DATABASE tempdb
MODIFY FILE (NAME = tempdev, FILENAME = 'E:\SQLData\tempdb.mdf');
GO
ALTER DATABASE tempdb
MODIFY FILE (NAME = templog, FILENAME = 'E:\SQLData\templog.ldf');
GO
"Tim Greenwood" <tim_greenwood A-T yahoo D-O-T com> wrote in message
news:uPtIzWxaGHA.2124@.TK2MSFTNGP03.phx.gbl...
> I'm very interested in this as well. We were planning on doing this first
> thing Saturday morning.
>
> "Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
> news:D7969E35-E4D2-4D22-A9BB-DD7B52EA6E2D@.microsoft.com...
>|||Hi Tim
What exactly are you doing in step 2? You shouldn't have to move anything,
since the tempdb files are recreated upon system startup. To move tempdb you
just need to run ALTER DATABASE and then restart your SQL Server.
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Tim Greenwood" <tim_greenwood A-T yahoo D-O-T com> wrote in message
news:uRzZ4dxaGHA.3408@.TK2MSFTNGP04.phx.gbl...
> Here ya go....BOL...just tried it and it worked great.
> 1. stop sql server
> 2. copy to your desired location
> 3. start sql server
> 4. run the alter statements below
> 5. restart sql server
> USE master;
> GO
> ALTER DATABASE tempdb
> MODIFY FILE (NAME = tempdev, FILENAME = 'E:\SQLData\tempdb.mdf');
> GO
> ALTER DATABASE tempdb
> MODIFY FILE (NAME = templog, FILENAME = 'E:\SQLData\templog.ldf');
> GO
> "Tim Greenwood" <tim_greenwood A-T yahoo D-O-T com> wrote in message
> news:uPtIzWxaGHA.2124@.TK2MSFTNGP03.phx.gbl...
>|||I was doing the steps as outlined in BOL...and I quote from BOL
G. Moving tempdb to a new location
The following example moves tempdb from its current location on disk to
another disk location.
1.. Determine the logical file names of the tempdb database and their
current location on disk.
SELECT name, physical_name
FROM sys.master_files
WHERE database_id = DB_ID('tempdb');
GO
2.. Physically move these files to the new location E:\SQLData.
In this example the new location specified for the tempdb files is
E:\SQLData. If you move the files to different location, modify the example
to point to that location.
3.. Change the location of each file by using ALTER DATABASE.
4.. Stop and restart the instance of SQL Server.
5.. Verify the file change.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:uG0CSzxaGHA.1192@.TK2MSFTNGP03.phx.gbl...
> Hi Tim
> What exactly are you doing in step 2? You shouldn't have to move anything,
> since the tempdb files are recreated upon system startup. To move tempdb
> you just need to run ALTER DATABASE and then restart your SQL Server.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.solidqualitylearning.com
>
> "Tim Greenwood" <tim_greenwood A-T yahoo D-O-T com> wrote in message
> news:uRzZ4dxaGHA.3408@.TK2MSFTNGP04.phx.gbl...
>|||Hi Tim
Just FYI, you do not have to move any files to move tempdb, because tempdb i
s rebuilt every time SQL Server starts.
Do you have the latest BOL? There was a refresh just a week ago.
G. Moving tempdb to a new location
The following example moves tempdb from its current location on the disk to
another disk location. Because tempdb is re-created each time the MSSQLSERVE
R service is started, you do not have to physically move the data and log fi
les. The files are created when the service is restarted in step 3. Until th
e service is restarted, tempdb continues to function in its existing locatio
n.
1.. Determine the logical file names of the tempdb database and their curren
t location on disk.
SELECT name, physical_name
FROM sys.master_files
WHERE database_id = DB_ID('tempdb');
GO
2.. Change the location of each file by using ALTER DATABASE.
USE master;
GO
ALTER DATABASE tempdb
MODIFY FILE (NAME = tempdev, FILENAME = 'E:\SQLData\tempdb.mdf');
GO
ALTER DATABASE tempdb
MODIFY FILE (NAME = templog, FILENAME = 'E:\SQLData\templog.ldf');
GO
3.. Stop and restart the instance of SQL Server.
4.. Verify the file change.
SELECT name, physical_name
FROM sys.master_files
WHERE database_id = DB_ID('tempdb');
5.. Delete the tempdb.mdf and templog.ldf files from their original location
.
--
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Tim Greenwood" <tim_greenwood A-T yahoo D-O-T com> wrote in message news:%23TTfa5zaGHA.1196
@.TK2MSFTNGP03.phx.gbl...
>I was doing the steps as outlined in BOL...and I quote from BOL
>
> G. Moving tempdb to a new location
> The following example moves tempdb from its current location on disk to
> another disk location.
>
> 1.. Determine the logical file names of the tempdb database and their
> current location on disk.
>
>
>
> SELECT name, physical_name
> FROM sys.master_files
> WHERE database_id = DB_ID('tempdb');
> GO
>
> 2.. Physically move these files to the new location E:\SQLData.
>
>
>
> In this example the new location specified for the tempdb files is
> E:\SQLData. If you move the files to different location, modify the exampl
e
> to point to that location.
>
>
>
> 3.. Change the location of each file by using ALTER DATABASE.
>
> 4.. Stop and restart the instance of SQL Server.
>
>
> 5.. Verify the file change.
>
>
>
>
> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> news:uG0CSzxaGHA.1192@.TK2MSFTNGP03.phx.gbl...
>
>

Move MS SQL 2005 Express Edition Data Path

Hi!
I just installed Web Developer express edition on my Windows 2000 server
machine. I just wanted to know how may I change the default data path of MS
SQL Server 2005 express edition.
MeIf you already installed it, look in this registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.1\Setup\SQLDataRoot
Changing this will require a restart of the SQL Server service.
HTH, jens Suessmeyer.|||If you already installed it, look in this registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Mi crosoft\Microsoft SQL
Server\MSSQL.1\Setup\SQLDataRo ot
Changing this will require a restart of the SQL Server service.
HTH, jens Suessmeyer.

Move MS SQL 2005 Express Edition Data Path

Hi!
I just installed Web Developer express edition on my Windows 2000 server
machine. I just wanted to know how may I change the default data path of MS
SQL Server 2005 express edition.
Me
If you already installed it, look in this registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.1\Setup\SQLDataRoot
Changing this will require a restart of the SQL Server service.
HTH, jens Suessmeyer.
|||If you already installed it, look in this registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Mi crosoft\Microsoft SQL
Server\MSSQL.1\Setup\SQLDataRo ot
Changing this will require a restart of the SQL Server service.
HTH, jens Suessmeyer.

Move MS SQL 2005 Express Edition Data Path

Hi!
I just installed Web Developer express edition on my Windows 2000 server
machine. I just wanted to know how may I change the default data path of MS
SQL Server 2005 express edition.
MeIf you already installed it, look in this registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Mi
crosoft SQL
Server\MSSQL.1\Setup\SQLDataRoot
Changing this will require a restart of the SQL Server service.
HTH, jens Suessmeyer.|||If you already installed it, look in this registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Mi crosoft\Microsoft SQL
Server\MSSQL.1\Setup\SQLDataRo ot
Changing this will require a restart of the SQL Server service.
HTH, jens Suessmeyer.

Move from active/passive cluster to active/active

Hi,
sorry for my lack of knowledge on this issue..
I've installed a Windows 2003 Cluster with SQL 2005. Works like a charm
when i do a failover.
Now i want to make this cluster active/active (multi instance) so no
connection is lost when a node goes down, but can't find any info on
how this need to be done. Can anyone help me out here..?!
Thanx in advance!
Hiddo,
"to make this cluster active/active (multi instance) so no connection is
lost when a node goes down"
When a cluster-group, or instance, moves from one node to another you do
loose your connection, as it offlines the group completely when moving.
Having a multi-instance, doesn't help, multi-instance is just another word
for having multiple virtual servers, they are still seperate in regards to
databases and connections. (e.g. if you have 2 instances, you can consider
them as being 2 different servers)
I do not think that your problem can be solved by server clustering.
HTH,
_Edwin.
<hiddo.vanloon@.gmail.com> wrote in message
news:1166449613.633338.27770@.t46g2000cwa.googlegro ups.com...
> Hi,
> sorry for my lack of knowledge on this issue..
> I've installed a Windows 2003 Cluster with SQL 2005. Works like a charm
> when i do a failover.
> Now i want to make this cluster active/active (multi instance) so no
> connection is lost when a node goes down, but can't find any info on
> how this need to be done. Can anyone help me out here..?!
> Thanx in advance!
>
|||a Network Load balanced cluster is something then a multi instance
cluster right?!
hiddo.vanloon@.gmail.com schreef:

> Hi,
> sorry for my lack of knowledge on this issue..
> I've installed a Windows 2003 Cluster with SQL 2005. Works like a charm
> when i do a failover.
> Now i want to make this cluster active/active (multi instance) so no
> connection is lost when a node goes down, but can't find any info on
> how this need to be done. Can anyone help me out here..?!
> Thanx in advance!
|||NLB is indeed different then failover clustering, however not really usable
with databases such as SQL.
You need to think of your requirements, and then match it to the right
technology option for SQL
Here are some links for reference:
(some are SQL2000, but still applicable for most part)
Failover Clustering
http://msdn2.microsoft.com/en-gb/library/ms189134.aspx
SQL Server 2000 Failover Clustering
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx
Scaling Out SQL Server with Data Dependent Routing
http://www.microsoft.com/technet/prodtechnol/sql/2005/scddrtng.mspx
Federated SQL Server 2000 Servers
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_cs_4fw3.asp
Federated Database Servers
http://msdn2.microsoft.com/en-us/library/ms190381.aspx
Scaling out SQL 2005
http://msdn2.microsoft.com/en-us/library/aa479364.aspx
HTH,
Rgds,
Edwin.
<hiddo.vanloon@.gmail.com> wrote in message
news:1166450266.512747.218020@.l12g2000cwl.googlegr oups.com...
> a Network Load balanced cluster is something then a multi instance
> cluster right?!
> hiddo.vanloon@.gmail.com schreef:
>
|||Edwin,
Thanx for your support! It's become more clear to me now...
Nog 1 vraag ... : )
Hoe verwijder ik een Windows 2003 cluster in z'n geheel. Ik draai (voor
test) een 2-node W2k3/SQL2k5 cluster en deze wil ik dus in z'n geheel
verwijderen.
Wanneer ik op de eerst node 'take offline' kies en vervolgens Evict
Node gaat dit goed, alleen bij de 2de node krijg ik RPC errors
(waarschijnlijk omdat hierop het virtuele cluster ip nog draait..)
Gr,
Hiddo
Edwin vMierlo schreef:
[vbcol=seagreen]
> NLB is indeed different then failover clustering, however not really usable
> with databases such as SQL.
> You need to think of your requirements, and then match it to the right
> technology option for SQL
> Here are some links for reference:
> (some are SQL2000, but still applicable for most part)
> Failover Clustering
> http://msdn2.microsoft.com/en-gb/library/ms189134.aspx
> SQL Server 2000 Failover Clustering
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx
> Scaling Out SQL Server with Data Dependent Routing
> http://www.microsoft.com/technet/prodtechnol/sql/2005/scddrtng.mspx
> Federated SQL Server 2000 Servers
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_cs_4fw3.asp
> Federated Database Servers
> http://msdn2.microsoft.com/en-us/library/ms190381.aspx
> Scaling out SQL 2005
> http://msdn2.microsoft.com/en-us/library/aa479364.aspx
>
> HTH,
> Rgds,
> Edwin.
>
> <hiddo.vanloon@.gmail.com> wrote in message
> news:1166450266.512747.218020@.l12g2000cwl.googlegr oups.com...
|||Hiddo,
Good practice is to keep posts in these newsgroups in english. This so
others can read the posts and possibly help themselves solving problems.
There are however some newsgroups for some topics in your native language,
they have the microsoft.public.nl.... prefix.
In regards to your question of fully removing a W2K3/SQL2K5 cluster,
first, remove SQL instances:
http://msdn2.microsoft.com/en-us/library/ms190438.aspx
then, remove the cluster:
http://support.microsoft.com/kb/282227
Good Luck !
Rgds,
Edwin.
<hiddo.vanloon@.gmail.com> wrote in message
news:1166452564.987411.275060@.n67g2000cwd.googlegr oups.com...[vbcol=seagreen]
> Edwin,
> Thanx for your support! It's become more clear to me now...
> Nog 1 vraag ... : )
> Hoe verwijder ik een Windows 2003 cluster in z'n geheel. Ik draai (voor
> test) een 2-node W2k3/SQL2k5 cluster en deze wil ik dus in z'n geheel
> verwijderen.
> Wanneer ik op de eerst node 'take offline' kies en vervolgens Evict
> Node gaat dit goed, alleen bij de 2de node krijg ik RPC errors
> (waarschijnlijk omdat hierop het virtuele cluster ip nog draait..)
> Gr,
> Hiddo
>
> Edwin vMierlo schreef:
usable[vbcol=seagreen]
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx[vbcol=seagreen]
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_cs_4fw3.asp[vbcol=seagreen]
charm
>

Move DBs to new server?

Hi,
I have 12 databases running on SQL Server 2000 on Windows 2000, and would
like to move them all to new hardware comprising Windows Server 2003 running
SQL Server 2000. I already have SQL Server installed on the new box. In
theory it's simple, but I have some questions:
1. Database security, logins, ownership etc; I hope to give the new server
the same name as the old server but it will have a different SID and I don't
know if there are any issues with that?
2. Merely restoring "user" databases to the new server means I will lose all
kinds of useful configuration data such as my record of backups? Do I also
have to restore Master, Model, MSDB, tempDB?
3. Is it best to detach/attach, or use backup/restore? If I use
backup/restore I'm confused about the tLog restore. I used to think if you
made a "full" backup you didn't need a tLog, but now I'm not sure, and the
SQL Server Books on-line example of using tLog backup and restore seems far
from clear. They imply the tLog can span events that happened BEFORE the
previous full backup! Basically I jsut want to kick out all users and do the
most simple type of backup that can easily be restored.
I tried to find docs related to this on Microsoft, but when I used the word
"migration" it came up with migrating from other Vendors, as opposed to
migrating to new hardware.
Gerry Hickman
SSRU SysAdmin
Gerry
1) Search on internet for two stored procedures ('sp_help_revlogin')provided
by MS to move logins with their original SID
2) If you have jobs on the old server ,so script them as a later you will be
ran it the new one.
3) BACKUP all user databases and RESTORE them on the new ONE.Make sure that
you have the same path for the .mdf,.ldf files otherwise you will use
WITH MOVE option
http://vyaskn.tripod.com/moving_sql_server.htm
"Gerry Hickman" <gerry1uk@.netscape.net> wrote in message
news:u7dZfpVMGHA.3856@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I have 12 databases running on SQL Server 2000 on Windows 2000, and would
> like to move them all to new hardware comprising Windows Server 2003
> running
> SQL Server 2000. I already have SQL Server installed on the new box. In
> theory it's simple, but I have some questions:
> 1. Database security, logins, ownership etc; I hope to give the new server
> the same name as the old server but it will have a different SID and I
> don't
> know if there are any issues with that?
> 2. Merely restoring "user" databases to the new server means I will lose
> all
> kinds of useful configuration data such as my record of backups? Do I also
> have to restore Master, Model, MSDB, tempDB?
> 3. Is it best to detach/attach, or use backup/restore? If I use
> backup/restore I'm confused about the tLog restore. I used to think if you
> made a "full" backup you didn't need a tLog, but now I'm not sure, and the
> SQL Server Books on-line example of using tLog backup and restore seems
> far
> from clear. They imply the tLog can span events that happened BEFORE the
> previous full backup! Basically I jsut want to kick out all users and do
> the
> most simple type of backup that can easily be restored.
> I tried to find docs related to this on Microsoft, but when I used the
> word
> "migration" it came up with migrating from other Vendors, as opposed to
> migrating to new hardware.
> --
> Gerry Hickman
> SSRU SysAdmin
>

Move DBs to new server?

Hi,
I have 12 databases running on SQL Server 2000 on Windows 2000, and would
like to move them all to new hardware comprising Windows Server 2003 running
SQL Server 2000. I already have SQL Server installed on the new box. In
theory it's simple, but I have some questions:
1. Database security, logins, ownership etc; I hope to give the new server
the same name as the old server but it will have a different SID and I don't
know if there are any issues with that?
2. Merely restoring "user" databases to the new server means I will lose all
kinds of useful configuration data such as my record of backups? Do I also
have to restore Master, Model, MSDB, tempDB?
3. Is it best to detach/attach, or use backup/restore? If I use
backup/restore I'm confused about the tLog restore. I used to think if you
made a "full" backup you didn't need a tLog, but now I'm not sure, and the
SQL Server Books on-line example of using tLog backup and restore seems far
from clear. They imply the tLog can span events that happened BEFORE the
previous full backup! Basically I jsut want to kick out all users and do the
most simple type of backup that can easily be restored.
I tried to find docs related to this on Microsoft, but when I used the word
"migration" it came up with migrating from other Vendors, as opposed to
migrating to new hardware.
--
Gerry Hickman
SSRU SysAdminGerry
1) Search on internet for two stored procedures ('sp_help_revlogin')provided
by MS to move logins with their original SID
2) If you have jobs on the old server ,so script them as a later you will be
ran it the new one.
3) BACKUP all user databases and RESTORE them on the new ONE.Make sure that
you have the same path for the .mdf,.ldf files otherwise you will use
WITH MOVE option
http://vyaskn.tripod.com/moving_sql_server.htm
"Gerry Hickman" <gerry1uk@.netscape.net> wrote in message
news:u7dZfpVMGHA.3856@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I have 12 databases running on SQL Server 2000 on Windows 2000, and would
> like to move them all to new hardware comprising Windows Server 2003
> running
> SQL Server 2000. I already have SQL Server installed on the new box. In
> theory it's simple, but I have some questions:
> 1. Database security, logins, ownership etc; I hope to give the new server
> the same name as the old server but it will have a different SID and I
> don't
> know if there are any issues with that?
> 2. Merely restoring "user" databases to the new server means I will lose
> all
> kinds of useful configuration data such as my record of backups? Do I also
> have to restore Master, Model, MSDB, tempDB?
> 3. Is it best to detach/attach, or use backup/restore? If I use
> backup/restore I'm confused about the tLog restore. I used to think if you
> made a "full" backup you didn't need a tLog, but now I'm not sure, and the
> SQL Server Books on-line example of using tLog backup and restore seems
> far
> from clear. They imply the tLog can span events that happened BEFORE the
> previous full backup! Basically I jsut want to kick out all users and do
> the
> most simple type of backup that can easily be restored.
> I tried to find docs related to this on Microsoft, but when I used the
> word
> "migration" it came up with migrating from other Vendors, as opposed to
> migrating to new hardware.
> --
> Gerry Hickman
> SSRU SysAdmin
>

Move DBs to new server?

Hi,
I have 12 databases running on SQL Server 2000 on Windows 2000, and would
like to move them all to new hardware comprising Windows Server 2003 running
SQL Server 2000. I already have SQL Server installed on the new box. In
theory it's simple, but I have some questions:
1. Database security, logins, ownership etc; I hope to give the new server
the same name as the old server but it will have a different SID and I don't
know if there are any issues with that?
2. Merely restoring "user" databases to the new server means I will lose all
kinds of useful configuration data such as my record of backups? Do I also
have to restore Master, Model, MSDB, tempDB?
3. Is it best to detach/attach, or use backup/restore? If I use
backup/restore I'm confused about the tLog restore. I used to think if you
made a "full" backup you didn't need a tLog, but now I'm not sure, and the
SQL Server Books on-line example of using tLog backup and restore seems far
from clear. They imply the tLog can span events that happened BEFORE the
previous full backup! Basically I jsut want to kick out all users and do the
most simple type of backup that can easily be restored.
I tried to find docs related to this on Microsoft, but when I used the word
"migration" it came up with migrating from other Vendors, as opposed to
migrating to new hardware.
Gerry Hickman
SSRU SysAdminGerry
1) Search on internet for two stored procedures ('sp_help_revlogin')provided
by MS to move logins with their original SID
2) If you have jobs on the old server ,so script them as a later you will be
ran it the new one.
3) BACKUP all user databases and RESTORE them on the new ONE.Make sure that
you have the same path for the .mdf,.ldf files otherwise you will use
WITH MOVE option
http://vyaskn.tripod.com/moving_sql_server.htm
"Gerry Hickman" <gerry1uk@.netscape.net> wrote in message
news:u7dZfpVMGHA.3856@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I have 12 databases running on SQL Server 2000 on Windows 2000, and would
> like to move them all to new hardware comprising Windows Server 2003
> running
> SQL Server 2000. I already have SQL Server installed on the new box. In
> theory it's simple, but I have some questions:
> 1. Database security, logins, ownership etc; I hope to give the new server
> the same name as the old server but it will have a different SID and I
> don't
> know if there are any issues with that?
> 2. Merely restoring "user" databases to the new server means I will lose
> all
> kinds of useful configuration data such as my record of backups? Do I also
> have to restore Master, Model, MSDB, tempDB?
> 3. Is it best to detach/attach, or use backup/restore? If I use
> backup/restore I'm confused about the tLog restore. I used to think if you
> made a "full" backup you didn't need a tLog, but now I'm not sure, and the
> SQL Server Books on-line example of using tLog backup and restore seems
> far
> from clear. They imply the tLog can span events that happened BEFORE the
> previous full backup! Basically I jsut want to kick out all users and do
> the
> most simple type of backup that can easily be restored.
> I tried to find docs related to this on Microsoft, but when I used the
> word
> "migration" it came up with migrating from other Vendors, as opposed to
> migrating to new hardware.
> --
> Gerry Hickman
> SSRU SysAdmin
>

Move DBs from One Instance to Another

SQL Server 2000
Windows Server 2003 SP1
We have 54 databases on this SQL Server and plan to move them all,
maintaining permissions and everything.
What is the best way to do this?
Thanks,
JimHere is a post from Andrew Kelly:
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=274463 Copy DB
Wizard issues
"Jim" <please.reply@.group> wrote in message
news:uYbmH6$EHHA.536@.TK2MSFTNGP02.phx.gbl...
> SQL Server 2000
> Windows Server 2003 SP1
> We have 54 databases on this SQL Server and plan to move them all,
> maintaining permissions and everything.
> What is the best way to do this?
> Thanks,
> Jim
>|||IMHO, easiest if you can have them offline is detach/copy/attach
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Jim" <please.reply@.group> wrote in message
news:uYbmH6$EHHA.536@.TK2MSFTNGP02.phx.gbl...
> SQL Server 2000
> Windows Server 2003 SP1
> We have 54 databases on this SQL Server and plan to move them all,
> maintaining permissions and everything.
> What is the best way to do this?
> Thanks,
> Jim
>|||You should also backup a master database and restore it to the
destination server. This way you should keep your logins in the
destination server.|||> You should also backup a master database and restore it to the
> destination server. This way you should keep your logins in the
> destination server.
Be cautious that @.@.version matches exactly on the two instances.|||Hi,
Ensure that you have the same SQL Server service pack level in both old as
well as new server. If both SP are same you can restore the Master db from
source
to new server.
Thanks
Hari
<sajberek@.gmail.com> wrote in message
news:1164839740.220233.125570@.n67g2000cwd.googlegroups.com...
> You should also backup a master database and restore it to the
> destination server. This way you should keep your logins in the
> destination server.
>|||Thanks for your input, everyone! I will be looking into all of this.
--Jim
"Jim" <please.reply@.group> wrote in message
news:uYbmH6$EHHA.536@.TK2MSFTNGP02.phx.gbl...
> SQL Server 2000
> Windows Server 2003 SP1
> We have 54 databases on this SQL Server and plan to move them all,
> maintaining permissions and everything.
> What is the best way to do this?
> Thanks,
> Jim
>

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