Hi, my requirement is to move a host of databases (including the systems
databases) to a new storage unit which will have new logical drives. Now I
followed the process of detach/attach as per article:
Moving SQL Server databases to a new location with Detach/Attach
http://support.microsoft.com/default.aspx?scid=kb;en-us;224071
I managed to move the databases in the order: model, msdb, temp (via ALTER
DATABASE). At this point SQL managed to start.
I then went to perform the master database relocation step via changing the
parameters in the startup parameters in EM, but my SQL would not start. So I
knew it was my master database which was the problem.
What I found was that I could not use the previous master db as it still had
references to model, msdb etc with the old drive letter. I could not simply
move the model and msdb files to this old drive letter as the drive letter
did not exist on the new storage unit.
My questions...
How do I modify my old master to reference the system databases based on the
new drive letters/location?
If i cannot do this, I am guessing I can use the new master db, however I
would need to change some of the system database files referencing in
sysdatabases, sysaltfiles and sysdevices? In addition I would need to script
out my logins as this obviously isnt attached with the new master, but with
the old master. After this process I should be set right?
Any help most appreciated.
Thanks.
JaneWhat I forgot to mention was the fact that these moved databases will not be
referenced by the old SQL server (serverA), but by a new instance of SQL on
another PC (serverB). So what I'm doing is the following:
Old configuration: serverA --> G:\myDatabaseFiles
New configuration: serverB --> Z:\myDatabaseFiles
ServerA cannot see Z: drive
ServerB cannot see G: drive
Any help most appreciated.
Kindest regards,
Jane
"Jane Richardson" <J.Richardson@.melgrave.com.au> wrote in message
news:e2Q$dge8FHA.500@.TK2MSFTNGP15.phx.gbl...
> Hi, my requirement is to move a host of databases (including the systems
> databases) to a new storage unit which will have new logical drives. Now I
> followed the process of detach/attach as per article:
> Moving SQL Server databases to a new location with Detach/Attach
> http://support.microsoft.com/default.aspx?scid=kb;en-us;224071
> I managed to move the databases in the order: model, msdb, temp (via ALTER
> DATABASE). At this point SQL managed to start.
> I then went to perform the master database relocation step via changing
> the parameters in the startup parameters in EM, but my SQL would not
> start. So I knew it was my master database which was the problem.
> What I found was that I could not use the previous master db as it still
> had references to model, msdb etc with the old drive letter. I could not
> simply move the model and msdb files to this old drive letter as the drive
> letter did not exist on the new storage unit.
> My questions...
> How do I modify my old master to reference the system databases based on
> the new drive letters/location?
> If i cannot do this, I am guessing I can use the new master db, however I
> would need to change some of the system database files referencing in
> sysdatabases, sysaltfiles and sysdevices? In addition I would need to
> script out my logins as this obviously isnt attached with the new master,
> but with the old master. After this process I should be set right?
> Any help most appreciated.
> Thanks.
> Jane
>
>
>
>
Showing posts with label storage. Show all posts
Showing posts with label storage. Show all posts
Friday, March 23, 2012
moving system db's to new location with different logical drive letters
Hi, my requirement is to move a host of databases (including the systems
databases) to a new storage unit which will have new logical drives. Now I
followed the process of detach/attach as per article:
Moving SQL Server databases to a new location with Detach/Attach
http://support.microsoft.com/default...b;en-us;224071
I managed to move the databases in the order: model, msdb, temp (via ALTER
DATABASE). At this point SQL managed to start.
I then went to perform the master database relocation step via changing the
parameters in the startup parameters in EM, but my SQL would not start. So I
knew it was my master database which was the problem.
What I found was that I could not use the previous master db as it still had
references to model, msdb etc with the old drive letter. I could not simply
move the model and msdb files to this old drive letter as the drive letter
did not exist on the new storage unit.
My questions...
How do I modify my old master to reference the system databases based on the
new drive letters/location?
If i cannot do this, I am guessing I can use the new master db, however I
would need to change some of the system database files referencing in
sysdatabases, sysaltfiles and sysdevices? In addition I would need to script
out my logins as this obviously isnt attached with the new master, but with
the old master. After this process I should be set right?
Any help most appreciated.
Thanks.
Jane
What I forgot to mention was the fact that these moved databases will not be
referenced by the old SQL server (serverA), but by a new instance of SQL on
another PC (serverB). So what I'm doing is the following:
Old configuration: serverA --> G:\myDatabaseFiles
New configuration: serverB --> Z:\myDatabaseFiles
ServerA cannot see Z: drive
ServerB cannot see G: drive
Any help most appreciated.
Kindest regards,
Jane
"Jane Richardson" <J.Richardson@.melgrave.com.au> wrote in message
news:e2Q$dge8FHA.500@.TK2MSFTNGP15.phx.gbl...
> Hi, my requirement is to move a host of databases (including the systems
> databases) to a new storage unit which will have new logical drives. Now I
> followed the process of detach/attach as per article:
> Moving SQL Server databases to a new location with Detach/Attach
> http://support.microsoft.com/default...b;en-us;224071
> I managed to move the databases in the order: model, msdb, temp (via ALTER
> DATABASE). At this point SQL managed to start.
> I then went to perform the master database relocation step via changing
> the parameters in the startup parameters in EM, but my SQL would not
> start. So I knew it was my master database which was the problem.
> What I found was that I could not use the previous master db as it still
> had references to model, msdb etc with the old drive letter. I could not
> simply move the model and msdb files to this old drive letter as the drive
> letter did not exist on the new storage unit.
> My questions...
> How do I modify my old master to reference the system databases based on
> the new drive letters/location?
> If i cannot do this, I am guessing I can use the new master db, however I
> would need to change some of the system database files referencing in
> sysdatabases, sysaltfiles and sysdevices? In addition I would need to
> script out my logins as this obviously isnt attached with the new master,
> but with the old master. After this process I should be set right?
> Any help most appreciated.
> Thanks.
> Jane
>
>
>
>
sql
databases) to a new storage unit which will have new logical drives. Now I
followed the process of detach/attach as per article:
Moving SQL Server databases to a new location with Detach/Attach
http://support.microsoft.com/default...b;en-us;224071
I managed to move the databases in the order: model, msdb, temp (via ALTER
DATABASE). At this point SQL managed to start.
I then went to perform the master database relocation step via changing the
parameters in the startup parameters in EM, but my SQL would not start. So I
knew it was my master database which was the problem.
What I found was that I could not use the previous master db as it still had
references to model, msdb etc with the old drive letter. I could not simply
move the model and msdb files to this old drive letter as the drive letter
did not exist on the new storage unit.
My questions...
How do I modify my old master to reference the system databases based on the
new drive letters/location?
If i cannot do this, I am guessing I can use the new master db, however I
would need to change some of the system database files referencing in
sysdatabases, sysaltfiles and sysdevices? In addition I would need to script
out my logins as this obviously isnt attached with the new master, but with
the old master. After this process I should be set right?
Any help most appreciated.
Thanks.
Jane
What I forgot to mention was the fact that these moved databases will not be
referenced by the old SQL server (serverA), but by a new instance of SQL on
another PC (serverB). So what I'm doing is the following:
Old configuration: serverA --> G:\myDatabaseFiles
New configuration: serverB --> Z:\myDatabaseFiles
ServerA cannot see Z: drive
ServerB cannot see G: drive
Any help most appreciated.
Kindest regards,
Jane
"Jane Richardson" <J.Richardson@.melgrave.com.au> wrote in message
news:e2Q$dge8FHA.500@.TK2MSFTNGP15.phx.gbl...
> Hi, my requirement is to move a host of databases (including the systems
> databases) to a new storage unit which will have new logical drives. Now I
> followed the process of detach/attach as per article:
> Moving SQL Server databases to a new location with Detach/Attach
> http://support.microsoft.com/default...b;en-us;224071
> I managed to move the databases in the order: model, msdb, temp (via ALTER
> DATABASE). At this point SQL managed to start.
> I then went to perform the master database relocation step via changing
> the parameters in the startup parameters in EM, but my SQL would not
> start. So I knew it was my master database which was the problem.
> What I found was that I could not use the previous master db as it still
> had references to model, msdb etc with the old drive letter. I could not
> simply move the model and msdb files to this old drive letter as the drive
> letter did not exist on the new storage unit.
> My questions...
> How do I modify my old master to reference the system databases based on
> the new drive letters/location?
> If i cannot do this, I am guessing I can use the new master db, however I
> would need to change some of the system database files referencing in
> sysdatabases, sysaltfiles and sysdevices? In addition I would need to
> script out my logins as this obviously isnt attached with the new master,
> but with the old master. After this process I should be set right?
> Any help most appreciated.
> Thanks.
> Jane
>
>
>
>
sql
moving system db's to new location with different logical drive letters
Hi, my requirement is to move a host of databases (including the systems
databases) to a new storage unit which will have new logical drives. Now I
followed the process of detach/attach as per article:
Moving SQL Server databases to a new location with Detach/Attach
http://support.microsoft.com/defaul...kb;en-us;224071
I managed to move the databases in the order: model, msdb, temp (via ALTER
DATABASE). At this point SQL managed to start.
I then went to perform the master database relocation step via changing the
parameters in the startup parameters in EM, but my SQL would not start. So I
knew it was my master database which was the problem.
What I found was that I could not use the previous master db as it still had
references to model, msdb etc with the old drive letter. I could not simply
move the model and msdb files to this old drive letter as the drive letter
did not exist on the new storage unit.
My questions...
How do I modify my old master to reference the system databases based on the
new drive letters/location?
If i cannot do this, I am guessing I can use the new master db, however I
would need to change some of the system database files referencing in
sysdatabases, sysaltfiles and sysdevices? In addition I would need to script
out my logins as this obviously isnt attached with the new master, but with
the old master. After this process I should be set right?
Any help most appreciated.
Thanks.
JaneWhat I forgot to mention was the fact that these moved databases will not be
referenced by the old SQL server (serverA), but by a new instance of SQL on
another PC (serverB). So what I'm doing is the following:
Old configuration: serverA --> G:\myDatabaseFiles
New configuration: serverB --> Z:\myDatabaseFiles
ServerA cannot see Z: drive
ServerB cannot see G: drive
Any help most appreciated.
Kindest regards,
Jane
"Jane Richardson" <J.Richardson@.melgrave.com.au> wrote in message
news:e2Q$dge8FHA.500@.TK2MSFTNGP15.phx.gbl...
> Hi, my requirement is to move a host of databases (including the systems
> databases) to a new storage unit which will have new logical drives. Now I
> followed the process of detach/attach as per article:
> Moving SQL Server databases to a new location with Detach/Attach
> http://support.microsoft.com/defaul...kb;en-us;224071
> I managed to move the databases in the order: model, msdb, temp (via ALTER
> DATABASE). At this point SQL managed to start.
> I then went to perform the master database relocation step via changing
> the parameters in the startup parameters in EM, but my SQL would not
> start. So I knew it was my master database which was the problem.
> What I found was that I could not use the previous master db as it still
> had references to model, msdb etc with the old drive letter. I could not
> simply move the model and msdb files to this old drive letter as the drive
> letter did not exist on the new storage unit.
> My questions...
> How do I modify my old master to reference the system databases based on
> the new drive letters/location?
> If i cannot do this, I am guessing I can use the new master db, however I
> would need to change some of the system database files referencing in
> sysdatabases, sysaltfiles and sysdevices? In addition I would need to
> script out my logins as this obviously isnt attached with the new master,
> but with the old master. After this process I should be set right?
> Any help most appreciated.
> Thanks.
> Jane
>
>
>
>
databases) to a new storage unit which will have new logical drives. Now I
followed the process of detach/attach as per article:
Moving SQL Server databases to a new location with Detach/Attach
http://support.microsoft.com/defaul...kb;en-us;224071
I managed to move the databases in the order: model, msdb, temp (via ALTER
DATABASE). At this point SQL managed to start.
I then went to perform the master database relocation step via changing the
parameters in the startup parameters in EM, but my SQL would not start. So I
knew it was my master database which was the problem.
What I found was that I could not use the previous master db as it still had
references to model, msdb etc with the old drive letter. I could not simply
move the model and msdb files to this old drive letter as the drive letter
did not exist on the new storage unit.
My questions...
How do I modify my old master to reference the system databases based on the
new drive letters/location?
If i cannot do this, I am guessing I can use the new master db, however I
would need to change some of the system database files referencing in
sysdatabases, sysaltfiles and sysdevices? In addition I would need to script
out my logins as this obviously isnt attached with the new master, but with
the old master. After this process I should be set right?
Any help most appreciated.
Thanks.
JaneWhat I forgot to mention was the fact that these moved databases will not be
referenced by the old SQL server (serverA), but by a new instance of SQL on
another PC (serverB). So what I'm doing is the following:
Old configuration: serverA --> G:\myDatabaseFiles
New configuration: serverB --> Z:\myDatabaseFiles
ServerA cannot see Z: drive
ServerB cannot see G: drive
Any help most appreciated.
Kindest regards,
Jane
"Jane Richardson" <J.Richardson@.melgrave.com.au> wrote in message
news:e2Q$dge8FHA.500@.TK2MSFTNGP15.phx.gbl...
> Hi, my requirement is to move a host of databases (including the systems
> databases) to a new storage unit which will have new logical drives. Now I
> followed the process of detach/attach as per article:
> Moving SQL Server databases to a new location with Detach/Attach
> http://support.microsoft.com/defaul...kb;en-us;224071
> I managed to move the databases in the order: model, msdb, temp (via ALTER
> DATABASE). At this point SQL managed to start.
> I then went to perform the master database relocation step via changing
> the parameters in the startup parameters in EM, but my SQL would not
> start. So I knew it was my master database which was the problem.
> What I found was that I could not use the previous master db as it still
> had references to model, msdb etc with the old drive letter. I could not
> simply move the model and msdb files to this old drive letter as the drive
> letter did not exist on the new storage unit.
> My questions...
> How do I modify my old master to reference the system databases based on
> the new drive letters/location?
> If i cannot do this, I am guessing I can use the new master db, however I
> would need to change some of the system database files referencing in
> sysdatabases, sysaltfiles and sysdevices? In addition I would need to
> script out my logins as this obviously isnt attached with the new master,
> but with the old master. After this process I should be set right?
> Any help most appreciated.
> Thanks.
> Jane
>
>
>
>
Friday, March 9, 2012
Moving resources to SATA storage temporarily
We are planning to move all resources to some SATA drives so we can
reconfigure the SAN. This includes the Quorum and all data resources.
Does anyone have any advice or can anyone think of any "gotchas" that we
should be watching for or preparing for?
This is unsupported and won't work. SCSI, SAN's, and iSCSI are supported. If
you SAN can handle SATA drives, go for it!
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Wayne" <watkinson@.sd43.bc.ca> wrote in message
news:eDrXTar$GHA.3308@.TK2MSFTNGP03.phx.gbl...
> We are planning to move all resources to some SATA drives so we can
> reconfigure the SAN. This includes the Quorum and all data resources.
> Does anyone have any advice or can anyone think of any "gotchas" that we
> should be watching for or preparing for?
>
|||"Wayne" <watkinson@.sd43.bc.ca> wrote in message
news:eDrXTar$GHA.3308@.TK2MSFTNGP03.phx.gbl...
> We are planning to move all resources to some SATA drives so we can
> reconfigure the SAN. This includes the Quorum and all data resources.
> Does anyone have any advice or can anyone think of any "gotchas" that we
> should be watching for or preparing for?
As Rodney said, SATA won't cut it.
Something you might consider would be to utilize a Majority Node Set quorum
so that way you can at least start with a reconfiguration of the quorum
disk.
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
reconfigure the SAN. This includes the Quorum and all data resources.
Does anyone have any advice or can anyone think of any "gotchas" that we
should be watching for or preparing for?
This is unsupported and won't work. SCSI, SAN's, and iSCSI are supported. If
you SAN can handle SATA drives, go for it!
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Wayne" <watkinson@.sd43.bc.ca> wrote in message
news:eDrXTar$GHA.3308@.TK2MSFTNGP03.phx.gbl...
> We are planning to move all resources to some SATA drives so we can
> reconfigure the SAN. This includes the Quorum and all data resources.
> Does anyone have any advice or can anyone think of any "gotchas" that we
> should be watching for or preparing for?
>
|||"Wayne" <watkinson@.sd43.bc.ca> wrote in message
news:eDrXTar$GHA.3308@.TK2MSFTNGP03.phx.gbl...
> We are planning to move all resources to some SATA drives so we can
> reconfigure the SAN. This includes the Quorum and all data resources.
> Does anyone have any advice or can anyone think of any "gotchas" that we
> should be watching for or preparing for?
As Rodney said, SATA won't cut it.
Something you might consider would be to utilize a Majority Node Set quorum
so that way you can at least start with a reconfiguration of the quorum
disk.
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
Subscribe to:
Posts (Atom)