How much work is it to add spindals to a drive on a
Windows 2000 Advanced Server clustered on a SAN?
Thank You,
Dave
You will need Veritas volume manager to expand the logical drive at the OS
level under Windows 2000. What happens at the SAN level depends on your SAN
vendor.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Dave" <anonymous@.discussions.microsoft.com> wrote in message
news:59bf01c42d50$5c2ec8a0$a301280a@.phx.gbl...
> How much work is it to add spindals to a drive on a
> Windows 2000 Advanced Server clustered on a SAN?
> Thank You,
> Dave
|||Dave -
Because we don't use Veritas we generally just add another drive to the
cluster, and make sure that the new drive does not share any spindals with
the old drive on the SAN. Then we just balance our data files.
Craig
ccarl@.mcafee.com
"Dave" <anonymous@.discussions.microsoft.com> wrote in message
news:59bf01c42d50$5c2ec8a0$a301280a@.phx.gbl...
> How much work is it to add spindals to a drive on a
> Windows 2000 Advanced Server clustered on a SAN?
> Thank You,
> Dave
|||If you wish to add physical disks to the same volume presented to your nodes in the cluster, assuming your SAN vendor supports it:
1. Add the new disks to the disk pool
2. Use diskpart (from the W2K resource kit - it comes with the o/s in W2K3) to "list volume" then "select volume" x and then "extend" the partition.
Note1: You must use diskpart 5.1 or newer (some of the earlier versions are dodgy)
Note2: This is an on-line operation and causes no disruption to current SQL operations.
Showing posts with label drive. Show all posts
Showing posts with label drive. Show all posts
Monday, March 19, 2012
Thursday, March 8, 2012
adding new volume and swapping drive letters....
Hello - I have a SQL 2000 server which has a D: drive that contains all of my databases (system and user). I am running out of space on this volume and need to migrate the contents of this volume to a larger one. My initial plan was to introduce a new volume to the server (say a K: drive). Backup all databases (of course), and then stop all SQL services. Copy all data from D: to K:. Once data is copied, swap drive letter names (D: to I: and then K: to D
. Then restart SQL services. SQL should not know any better since everything was on the D: drive when it went down, and everythiing is still on the D: drive when it came back up, correct?
. Then restart SQL services. SQL should not know any better since everything was on the D: drive when it went down, and everythiing is still on the D: drive when it came back up, correct?The other option mentioned is to detatch the databases, copy the data and then reattach them in their new locations. I understand this method, but it seems more involved (and riskier) than just renaming the drives. Does anyone have an opinion regarding these two migration methods? Thanks for your help.
Chris
I would use the attach / detach method, would be the best solution for me in this case.
Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||As you indicated, the drive rename method may be less effort. As long as you are using the Disk Management applet -and not just mapping drives, it should work just fine.
Tuesday, March 6, 2012
Adding New Drive
SQL 2000 installed on C drive filling up added D drive is
there anything I need to do to the D drive before I attach
a database *.ldf and *.mdf to the D drive - Do I need
another instance or any files or folders from C or do I
need to change anything on the setup. I can't find this
info anywhere.
Thank You!There is nothing you need to do unless this is a clustered instance of SQL
Server. Just create the appropriate directories, move the files into them,
and then attach the database.
If you are running a clustered server it gets a bit more involved.
"Jennifer" <jennifer.chmiel@.elder-beerman.com> wrote in message
news:030901c36d8d$256a5dd0$a101280a@.phx.gbl...
> SQL 2000 installed on C drive filling up added D drive is
> there anything I need to do to the D drive before I attach
> a database *.ldf and *.mdf to the D drive - Do I need
> another instance or any files or folders from C or do I
> need to change anything on the setup. I can't find this
> info anywhere.
> Thank You!
there anything I need to do to the D drive before I attach
a database *.ldf and *.mdf to the D drive - Do I need
another instance or any files or folders from C or do I
need to change anything on the setup. I can't find this
info anywhere.
Thank You!There is nothing you need to do unless this is a clustered instance of SQL
Server. Just create the appropriate directories, move the files into them,
and then attach the database.
If you are running a clustered server it gets a bit more involved.
"Jennifer" <jennifer.chmiel@.elder-beerman.com> wrote in message
news:030901c36d8d$256a5dd0$a101280a@.phx.gbl...
> SQL 2000 installed on C drive filling up added D drive is
> there anything I need to do to the D drive before I attach
> a database *.ldf and *.mdf to the D drive - Do I need
> another instance or any files or folders from C or do I
> need to change anything on the setup. I can't find this
> info anywhere.
> Thank You!
Sunday, February 19, 2012
Adding drive dependencies to WIN2k/SQL2k cluster resource
I need to add two additional SAN attached volumes to be dependencies
for my SQL Server Cluster resource. Do I have to restart the cluster
service for this to take affect? Is there another way for the cluster
resource to re initialize it's dependencies without restarting?
If you want to create databases on these drives, you need to add them to the
SQL Server resource dependency list. To do that, you don't need to restart
the cluster service. But you do need to take the SQL Server resource offline,
add the drives as the dependencies, and then bring the SQL Server resource
online.
Linchi
"zoneranger@.gmail.com" wrote:
> I need to add two additional SAN attached volumes to be dependencies
> for my SQL Server Cluster resource. Do I have to restart the cluster
> service for this to take affect? Is there another way for the cluster
> resource to re initialize it's dependencies without restarting?
>
for my SQL Server Cluster resource. Do I have to restart the cluster
service for this to take affect? Is there another way for the cluster
resource to re initialize it's dependencies without restarting?
If you want to create databases on these drives, you need to add them to the
SQL Server resource dependency list. To do that, you don't need to restart
the cluster service. But you do need to take the SQL Server resource offline,
add the drives as the dependencies, and then bring the SQL Server resource
online.
Linchi
"zoneranger@.gmail.com" wrote:
> I need to add two additional SAN attached volumes to be dependencies
> for my SQL Server Cluster resource. Do I have to restart the cluster
> service for this to take affect? Is there another way for the cluster
> resource to re initialize it's dependencies without restarting?
>
Sunday, February 12, 2012
Adding another server instance to another hard drive?
A disaster recovery plan will help you minimize data loss. You need to
plan for various recovery scenarios according to the amount of data loss
that is acceptable to you.
The worst case is that you lose your computer completely due to a disaster
such as for or theft. Your only recourse in this situation is to reinstall
SQL Server on a working machine and restore from backups you've kept in a
safe location.
If your computer crashes and/or you lose your SQL Server drive, you might
get lucky with a successful attach of the database files if your database
files are intact. However, you should not rely on this and plan on
restoring your database from backup because you might not be able to attach
databases which were not detached properly.
The bottom line is that you need to backup your databases periodically and
archive the backup files to a safe location.
Hope this helps.
Dan Guzman
SQL Server MVP
"Niels" <nkistrup@.comcast.net> wrote in message
news:NeudnYnNW-kXTiTdRVn2tQ@.giganews.com...
> Peter,
> So much for my mastery of English. I don't think I'm explaining the
> situation correctly, sorry.
> I'm running Win 2000 Pro, with the developer's edition of MS SQL Server,
but
> I have 4 hard drives ... and it's all on my home computer (I'm the
'network
> guy'). Maybe another server instance is not the correct terminology?
> Currently my data is on D:, but I would like to use one of the other hard
> drives to actively store data.
> If the computer crashes, I'm screwed, but I can always move the hard drive
> to another machine. Heck the drive where the data is 6 1/2 yrs old, and
has
> migrated across machines in the past. (The hard drive.)
> Niels
>Dan,
Lets talk 'preemptive correction'. My data drive is 6 1/2 yrs old & have
the replacement drive ready for swapping. How do you copy the server
instance onto a new drive. From what I can see, it is not as easy as
copying the SQL data folder to another drive, then onto the new one. (Or is
it?)
I am still curious about creating other server instances on other hard
drives. That way, I could spread the data across hard drives. Yes, I need
to transfer my data to a new drive, which will have the same drive. But
just because I cannot figure how out how to create new server instances,
makes me curious about the procedure. I work as a T-SQL developer, but my
DBA skills are minimal, which is why I'm being such a persistent pest about
this.
Hard drive crashes remain my #1 disaster threat. Failure of the computer is
also possible, but like you said, regular backups minimize problems from
that.
Niels
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:OPBjaKmREHA.2848@.TK2MSFTNGP10.phx.gbl...
> A disaster recovery plan will help you minimize data loss. You need to
> plan for various recovery scenarios according to the amount of data loss
> that is acceptable to you.
> The worst case is that you lose your computer completely due to a disaster
> such as for or theft. Your only recourse in this situation is to
reinstall
> SQL Server on a working machine and restore from backups you've kept in a
> safe location.
> If your computer crashes and/or you lose your SQL Server drive, you might
> get lucky with a successful attach of the database files if your database
> files are intact. However, you should not rely on this and plan on
> restoring your database from backup because you might not be able to
attach
> databases which were not detached properly.
> The bottom line is that you need to backup your databases periodically and
> archive the backup files to a safe location.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Niels" <nkistrup@.comcast.net> wrote in message
> news:NeudnYnNW-kXTiTdRVn2tQ@.giganews.com...
> but
> 'network
hard[vbcol=seagreen]
drive[vbcol=seagreen]
> has
>|||I am not sure if you really mean another instance or just moving the data
files. If you want to install a second instance of sql server (binaries)
then you need to rerun the setup and point it to the other drive for the
install. If you just want to move the data files you can find what you need
here:
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.databasejournal.com/feat...cle.php/2228611
Transferring Logins
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/scr...sp?scriptid=599
Restoring a .mdf
This still does not mean you should not have valid backups. See BACKUP and
RESTORE in BooksOnLine for more info.
Andrew J. Kelly
SQL Server MVP
"Niels" <nkistrup@.comcast.net> wrote in message
news:GY6dneIma9N3zSfdRVn2tA@.giganews.com...
> Dan,
> Lets talk 'preemptive correction'. My data drive is 6 1/2 yrs old & have
> the replacement drive ready for swapping. How do you copy the server
> instance onto a new drive. From what I can see, it is not as easy as
> copying the SQL data folder to another drive, then onto the new one. (Or
is
> it?)
> I am still curious about creating other server instances on other hard
> drives. That way, I could spread the data across hard drives. Yes, I
need
> to transfer my data to a new drive, which will have the same drive. But
> just because I cannot figure how out how to create new server instances,
> makes me curious about the procedure. I work as a T-SQL developer, but my
> DBA skills are minimal, which is why I'm being such a persistent pest
about
> this.
> Hard drive crashes remain my #1 disaster threat. Failure of the computer
is
> also possible, but like you said, regular backups minimize problems from
> that.
> Niels
> "Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
> news:OPBjaKmREHA.2848@.TK2MSFTNGP10.phx.gbl...
disaster[vbcol=seagreen]
> reinstall
a[vbcol=seagreen]
might[vbcol=seagreen]
database[vbcol=seagreen]
> attach
and[vbcol=seagreen]
Server,[vbcol=seagreen]
> hard
> drive
and[vbcol=seagreen]
>
plan for various recovery scenarios according to the amount of data loss
that is acceptable to you.
The worst case is that you lose your computer completely due to a disaster
such as for or theft. Your only recourse in this situation is to reinstall
SQL Server on a working machine and restore from backups you've kept in a
safe location.
If your computer crashes and/or you lose your SQL Server drive, you might
get lucky with a successful attach of the database files if your database
files are intact. However, you should not rely on this and plan on
restoring your database from backup because you might not be able to attach
databases which were not detached properly.
The bottom line is that you need to backup your databases periodically and
archive the backup files to a safe location.
Hope this helps.
Dan Guzman
SQL Server MVP
"Niels" <nkistrup@.comcast.net> wrote in message
news:NeudnYnNW-kXTiTdRVn2tQ@.giganews.com...
> Peter,
> So much for my mastery of English. I don't think I'm explaining the
> situation correctly, sorry.
> I'm running Win 2000 Pro, with the developer's edition of MS SQL Server,
but
> I have 4 hard drives ... and it's all on my home computer (I'm the
'network
> guy'). Maybe another server instance is not the correct terminology?
> Currently my data is on D:, but I would like to use one of the other hard
> drives to actively store data.
> If the computer crashes, I'm screwed, but I can always move the hard drive
> to another machine. Heck the drive where the data is 6 1/2 yrs old, and
has
> migrated across machines in the past. (The hard drive.)
> Niels
>Dan,
Lets talk 'preemptive correction'. My data drive is 6 1/2 yrs old & have
the replacement drive ready for swapping. How do you copy the server
instance onto a new drive. From what I can see, it is not as easy as
copying the SQL data folder to another drive, then onto the new one. (Or is
it?)
I am still curious about creating other server instances on other hard
drives. That way, I could spread the data across hard drives. Yes, I need
to transfer my data to a new drive, which will have the same drive. But
just because I cannot figure how out how to create new server instances,
makes me curious about the procedure. I work as a T-SQL developer, but my
DBA skills are minimal, which is why I'm being such a persistent pest about
this.
Hard drive crashes remain my #1 disaster threat. Failure of the computer is
also possible, but like you said, regular backups minimize problems from
that.
Niels
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:OPBjaKmREHA.2848@.TK2MSFTNGP10.phx.gbl...
> A disaster recovery plan will help you minimize data loss. You need to
> plan for various recovery scenarios according to the amount of data loss
> that is acceptable to you.
> The worst case is that you lose your computer completely due to a disaster
> such as for or theft. Your only recourse in this situation is to
reinstall
> SQL Server on a working machine and restore from backups you've kept in a
> safe location.
> If your computer crashes and/or you lose your SQL Server drive, you might
> get lucky with a successful attach of the database files if your database
> files are intact. However, you should not rely on this and plan on
> restoring your database from backup because you might not be able to
attach
> databases which were not detached properly.
> The bottom line is that you need to backup your databases periodically and
> archive the backup files to a safe location.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Niels" <nkistrup@.comcast.net> wrote in message
> news:NeudnYnNW-kXTiTdRVn2tQ@.giganews.com...
> but
> 'network
hard[vbcol=seagreen]
drive[vbcol=seagreen]
> has
>|||I am not sure if you really mean another instance or just moving the data
files. If you want to install a second instance of sql server (binaries)
then you need to rerun the setup and point it to the other drive for the
install. If you just want to move the data files you can find what you need
here:
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.databasejournal.com/feat...cle.php/2228611
Transferring Logins
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/scr...sp?scriptid=599
Restoring a .mdf
This still does not mean you should not have valid backups. See BACKUP and
RESTORE in BooksOnLine for more info.
Andrew J. Kelly
SQL Server MVP
"Niels" <nkistrup@.comcast.net> wrote in message
news:GY6dneIma9N3zSfdRVn2tA@.giganews.com...
> Dan,
> Lets talk 'preemptive correction'. My data drive is 6 1/2 yrs old & have
> the replacement drive ready for swapping. How do you copy the server
> instance onto a new drive. From what I can see, it is not as easy as
> copying the SQL data folder to another drive, then onto the new one. (Or
is
> it?)
> I am still curious about creating other server instances on other hard
> drives. That way, I could spread the data across hard drives. Yes, I
need
> to transfer my data to a new drive, which will have the same drive. But
> just because I cannot figure how out how to create new server instances,
> makes me curious about the procedure. I work as a T-SQL developer, but my
> DBA skills are minimal, which is why I'm being such a persistent pest
about
> this.
> Hard drive crashes remain my #1 disaster threat. Failure of the computer
is
> also possible, but like you said, regular backups minimize problems from
> that.
> Niels
> "Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
> news:OPBjaKmREHA.2848@.TK2MSFTNGP10.phx.gbl...
disaster[vbcol=seagreen]
> reinstall
a[vbcol=seagreen]
might[vbcol=seagreen]
database[vbcol=seagreen]
> attach
and[vbcol=seagreen]
Server,[vbcol=seagreen]
> hard
> drive
and[vbcol=seagreen]
>
Adding another server instance to another hard drive?
Problem: For safety reasons, I want an exact copy of all SQL databases on
another hard drive. I'm trying to guard against a hard drive crash.
Currently, I detach, file copy to another drive, then reattach each
individual database. Since SQL Server is running on different hard drive
from the data, I know that I wouldn't have to reinstall it.
1) Is there a way to do what I am asking?
2) Is this the correct the newsgroup to post these questions?
3) Is there a book that covers this?
Tried various keywords, but couldn't find anything in Books Online. I'm
running MS SQL Server Developer's ed. under Windows 2000 Pro.
Niels
That is what backups are for. It's much easier to simply do a backup of
each database (including Master & MSDB) and store those in a different
location. Preferably on a different machine or medium altogether, You don't
have to take the databases off line for a backup like you do with detach.
You might want to take a look at this:
http://www.microsoft.com/technet/pro...n/sqlops0.mspx
Andrew J. Kelly
SQL Server MVP
"Niels" <nkistrup@.comcast.net> wrote in message
news:6v-dnY1yOZGJGCXdRVn2sQ@.giganews.com...
> Problem: For safety reasons, I want an exact copy of all SQL databases on
> another hard drive. I'm trying to guard against a hard drive crash.
> Currently, I detach, file copy to another drive, then reattach each
> individual database. Since SQL Server is running on different hard drive
> from the data, I know that I wouldn't have to reinstall it.
> 1) Is there a way to do what I am asking?
> 2) Is this the correct the newsgroup to post these questions?
> 3) Is there a book that covers this?
> Tried various keywords, but couldn't find anything in Books Online. I'm
> running MS SQL Server Developer's ed. under Windows 2000 Pro.
> Niels
>
|||Thanks Andrew,
But I will still like to create another server. Where I can find the steps
to add additional server instances?
Niels
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:ev$827XREHA.568@.TK2MSFTNGP12.phx.gbl...
> That is what backups are for. It's much easier to simply do a backup of
> each database (including Master & MSDB) and store those in a different
> location. Preferably on a different machine or medium altogether, You
don't
> have to take the databases off line for a backup like you do with detach.
> You might want to take a look at this:
>
http://www.microsoft.com/technet/pro...n/sqlops0.mspx[vbcol=seagreen]
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "Niels" <nkistrup@.comcast.net> wrote in message
> news:6v-dnY1yOZGJGCXdRVn2sQ@.giganews.com...
on[vbcol=seagreen]
drive
>
|||There a couple of options that you might want to consider.
Firstly if your running NT 4, 2000 or 2003, then ask your network guys to
raid the disks, I wouldn't do into it in too much detail but there are
plenty of examples. What a raid does in automatically (non SQL Server) copy
stuff from one hard drive to another.
If you wish to create another instance on your current machine then that
will not really help as if the machine goes then both instances go.
If you want to create another server then you will need another machine to
do it then you just install SQL Server the normal way, that will create a
default instance on that machine.
If you want to keep your database running in case of server crashes then
create a new server and backup your databases on the other server.(using the
backup database command).
If you want a server to kick in automatically when your existing server dies
then look on Microsoft for Replication, and High Availabity Server.
"Niels" <nkistrup@.comcast.net> wrote in message
news:8fKdnfr3UYxtyCTdRVn2sw@.giganews.com...
> Thanks Andrew,
> But I will still like to create another server. Where I can find the
steps[vbcol=seagreen]
> to add additional server instances?
> Niels
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:ev$827XREHA.568@.TK2MSFTNGP12.phx.gbl...
> don't
detach.
>
http://www.microsoft.com/technet/pro...n/sqlops0.mspx[vbcol=seagreen]
[vbcol=seagreen]
> on
> drive
I'm
>
|||Peter,
So much for my mastery of English. I don't think I'm explaining the
situation correctly, sorry.
I'm running Win 2000 Pro, with the developer's edition of MS SQL Server, but
I have 4 hard drives ... and it's all on my home computer (I'm the 'network
guy'). Maybe another server instance is not the correct terminology?
Currently my data is on D:, but I would like to use one of the other hard
drives to actively store data.
If the computer crashes, I'm screwed, but I can always move the hard drive
to another machine. Heck the drive where the data is 6 1/2 yrs old, and has
migrated across machines in the past. (The hard drive.)
Niels
"Peter Nolan" <peter.nolan90@.ntlworld.com> wrote in message
news:x4luc.65$PA4.57@.newsfe1-gui.server.ntli.net...
> There a couple of options that you might want to consider.
> Firstly if your running NT 4, 2000 or 2003, then ask your network guys to
> raid the disks, I wouldn't do into it in too much detail but there are
> plenty of examples. What a raid does in automatically (non SQL Server)
copy
> stuff from one hard drive to another.
> If you wish to create another instance on your current machine then that
> will not really help as if the machine goes then both instances go.
> If you want to create another server then you will need another machine to
> do it then you just install SQL Server the normal way, that will create a
> default instance on that machine.
> If you want to keep your database running in case of server crashes then
> create a new server and backup your databases on the other server.(using
the
> backup database command).
> If you want a server to kick in automatically when your existing server
dies[vbcol=seagreen]
> then look on Microsoft for Replication, and High Availabity Server.
>
> "Niels" <nkistrup@.comcast.net> wrote in message
> news:8fKdnfr3UYxtyCTdRVn2sw@.giganews.com...
> steps
of
> detach.
>
http://www.microsoft.com/technet/pro...n/sqlops0.mspx[vbcol=seagreen]
databases
> I'm
>
|||A disaster recovery plan will help you minimize data loss. You need to
plan for various recovery scenarios according to the amount of data loss
that is acceptable to you.
The worst case is that you lose your computer completely due to a disaster
such as for or theft. Your only recourse in this situation is to reinstall
SQL Server on a working machine and restore from backups you've kept in a
safe location.
If your computer crashes and/or you lose your SQL Server drive, you might
get lucky with a successful attach of the database files if your database
files are intact. However, you should not rely on this and plan on
restoring your database from backup because you might not be able to attach
databases which were not detached properly.
The bottom line is that you need to backup your databases periodically and
archive the backup files to a safe location.
Hope this helps.
Dan Guzman
SQL Server MVP
"Niels" <nkistrup@.comcast.net> wrote in message
news:NeudnYnNW-kXTiTdRVn2tQ@.giganews.com...
> Peter,
> So much for my mastery of English. I don't think I'm explaining the
> situation correctly, sorry.
> I'm running Win 2000 Pro, with the developer's edition of MS SQL Server,
but
> I have 4 hard drives ... and it's all on my home computer (I'm the
'network
> guy'). Maybe another server instance is not the correct terminology?
> Currently my data is on D:, but I would like to use one of the other hard
> drives to actively store data.
> If the computer crashes, I'm screwed, but I can always move the hard drive
> to another machine. Heck the drive where the data is 6 1/2 yrs old, and
has
> migrated across machines in the past. (The hard drive.)
> Niels
>
|||Dan,
Lets talk 'preemptive correction'. My data drive is 6 1/2 yrs old & have
the replacement drive ready for swapping. How do you copy the server
instance onto a new drive. From what I can see, it is not as easy as
copying the SQL data folder to another drive, then onto the new one. (Or is
it?)
I am still curious about creating other server instances on other hard
drives. That way, I could spread the data across hard drives. Yes, I need
to transfer my data to a new drive, which will have the same drive. But
just because I cannot figure how out how to create new server instances,
makes me curious about the procedure. I work as a T-SQL developer, but my
DBA skills are minimal, which is why I'm being such a persistent pest about
this.
Hard drive crashes remain my #1 disaster threat. Failure of the computer is
also possible, but like you said, regular backups minimize problems from
that.
Niels
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:OPBjaKmREHA.2848@.TK2MSFTNGP10.phx.gbl...
> A disaster recovery plan will help you minimize data loss. You need to
> plan for various recovery scenarios according to the amount of data loss
> that is acceptable to you.
> The worst case is that you lose your computer completely due to a disaster
> such as for or theft. Your only recourse in this situation is to
reinstall
> SQL Server on a working machine and restore from backups you've kept in a
> safe location.
> If your computer crashes and/or you lose your SQL Server drive, you might
> get lucky with a successful attach of the database files if your database
> files are intact. However, you should not rely on this and plan on
> restoring your database from backup because you might not be able to
attach[vbcol=seagreen]
> databases which were not detached properly.
> The bottom line is that you need to backup your databases periodically and
> archive the backup files to a safe location.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Niels" <nkistrup@.comcast.net> wrote in message
> news:NeudnYnNW-kXTiTdRVn2tQ@.giganews.com...
> but
> 'network
hard[vbcol=seagreen]
drive
> has
>
|||I am not sure if you really mean another instance or just moving the data
files. If you want to install a second instance of sql server (binaries)
then you need to rerun the setup and point it to the other drive for the
install. If you just want to move the data files you can find what you need
here:
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.databasejournal.com/featu...le.php/2228611
Transferring Logins
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/scri...p?scriptid=599
Restoring a .mdf
This still does not mean you should not have valid backups. See BACKUP and
RESTORE in BooksOnLine for more info.
Andrew J. Kelly
SQL Server MVP
"Niels" <nkistrup@.comcast.net> wrote in message
news:GY6dneIma9N3zSfdRVn2tA@.giganews.com...
> Dan,
> Lets talk 'preemptive correction'. My data drive is 6 1/2 yrs old & have
> the replacement drive ready for swapping. How do you copy the server
> instance onto a new drive. From what I can see, it is not as easy as
> copying the SQL data folder to another drive, then onto the new one. (Or
is
> it?)
> I am still curious about creating other server instances on other hard
> drives. That way, I could spread the data across hard drives. Yes, I
need
> to transfer my data to a new drive, which will have the same drive. But
> just because I cannot figure how out how to create new server instances,
> makes me curious about the procedure. I work as a T-SQL developer, but my
> DBA skills are minimal, which is why I'm being such a persistent pest
about
> this.
> Hard drive crashes remain my #1 disaster threat. Failure of the computer
is[vbcol=seagreen]
> also possible, but like you said, regular backups minimize problems from
> that.
> Niels
> "Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
> news:OPBjaKmREHA.2848@.TK2MSFTNGP10.phx.gbl...
disaster[vbcol=seagreen]
> reinstall
a[vbcol=seagreen]
might[vbcol=seagreen]
database[vbcol=seagreen]
> attach
and[vbcol=seagreen]
Server,[vbcol=seagreen]
> hard
> drive
and
>
another hard drive. I'm trying to guard against a hard drive crash.
Currently, I detach, file copy to another drive, then reattach each
individual database. Since SQL Server is running on different hard drive
from the data, I know that I wouldn't have to reinstall it.
1) Is there a way to do what I am asking?
2) Is this the correct the newsgroup to post these questions?
3) Is there a book that covers this?
Tried various keywords, but couldn't find anything in Books Online. I'm
running MS SQL Server Developer's ed. under Windows 2000 Pro.
Niels
That is what backups are for. It's much easier to simply do a backup of
each database (including Master & MSDB) and store those in a different
location. Preferably on a different machine or medium altogether, You don't
have to take the databases off line for a backup like you do with detach.
You might want to take a look at this:
http://www.microsoft.com/technet/pro...n/sqlops0.mspx
Andrew J. Kelly
SQL Server MVP
"Niels" <nkistrup@.comcast.net> wrote in message
news:6v-dnY1yOZGJGCXdRVn2sQ@.giganews.com...
> Problem: For safety reasons, I want an exact copy of all SQL databases on
> another hard drive. I'm trying to guard against a hard drive crash.
> Currently, I detach, file copy to another drive, then reattach each
> individual database. Since SQL Server is running on different hard drive
> from the data, I know that I wouldn't have to reinstall it.
> 1) Is there a way to do what I am asking?
> 2) Is this the correct the newsgroup to post these questions?
> 3) Is there a book that covers this?
> Tried various keywords, but couldn't find anything in Books Online. I'm
> running MS SQL Server Developer's ed. under Windows 2000 Pro.
> Niels
>
|||Thanks Andrew,
But I will still like to create another server. Where I can find the steps
to add additional server instances?
Niels
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:ev$827XREHA.568@.TK2MSFTNGP12.phx.gbl...
> That is what backups are for. It's much easier to simply do a backup of
> each database (including Master & MSDB) and store those in a different
> location. Preferably on a different machine or medium altogether, You
don't
> have to take the databases off line for a backup like you do with detach.
> You might want to take a look at this:
>
http://www.microsoft.com/technet/pro...n/sqlops0.mspx[vbcol=seagreen]
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "Niels" <nkistrup@.comcast.net> wrote in message
> news:6v-dnY1yOZGJGCXdRVn2sQ@.giganews.com...
on[vbcol=seagreen]
drive
>
|||There a couple of options that you might want to consider.
Firstly if your running NT 4, 2000 or 2003, then ask your network guys to
raid the disks, I wouldn't do into it in too much detail but there are
plenty of examples. What a raid does in automatically (non SQL Server) copy
stuff from one hard drive to another.
If you wish to create another instance on your current machine then that
will not really help as if the machine goes then both instances go.
If you want to create another server then you will need another machine to
do it then you just install SQL Server the normal way, that will create a
default instance on that machine.
If you want to keep your database running in case of server crashes then
create a new server and backup your databases on the other server.(using the
backup database command).
If you want a server to kick in automatically when your existing server dies
then look on Microsoft for Replication, and High Availabity Server.
"Niels" <nkistrup@.comcast.net> wrote in message
news:8fKdnfr3UYxtyCTdRVn2sw@.giganews.com...
> Thanks Andrew,
> But I will still like to create another server. Where I can find the
steps[vbcol=seagreen]
> to add additional server instances?
> Niels
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:ev$827XREHA.568@.TK2MSFTNGP12.phx.gbl...
> don't
detach.
>
http://www.microsoft.com/technet/pro...n/sqlops0.mspx[vbcol=seagreen]
[vbcol=seagreen]
> on
> drive
I'm
>
|||Peter,
So much for my mastery of English. I don't think I'm explaining the
situation correctly, sorry.
I'm running Win 2000 Pro, with the developer's edition of MS SQL Server, but
I have 4 hard drives ... and it's all on my home computer (I'm the 'network
guy'). Maybe another server instance is not the correct terminology?
Currently my data is on D:, but I would like to use one of the other hard
drives to actively store data.
If the computer crashes, I'm screwed, but I can always move the hard drive
to another machine. Heck the drive where the data is 6 1/2 yrs old, and has
migrated across machines in the past. (The hard drive.)
Niels
"Peter Nolan" <peter.nolan90@.ntlworld.com> wrote in message
news:x4luc.65$PA4.57@.newsfe1-gui.server.ntli.net...
> There a couple of options that you might want to consider.
> Firstly if your running NT 4, 2000 or 2003, then ask your network guys to
> raid the disks, I wouldn't do into it in too much detail but there are
> plenty of examples. What a raid does in automatically (non SQL Server)
copy
> stuff from one hard drive to another.
> If you wish to create another instance on your current machine then that
> will not really help as if the machine goes then both instances go.
> If you want to create another server then you will need another machine to
> do it then you just install SQL Server the normal way, that will create a
> default instance on that machine.
> If you want to keep your database running in case of server crashes then
> create a new server and backup your databases on the other server.(using
the
> backup database command).
> If you want a server to kick in automatically when your existing server
dies[vbcol=seagreen]
> then look on Microsoft for Replication, and High Availabity Server.
>
> "Niels" <nkistrup@.comcast.net> wrote in message
> news:8fKdnfr3UYxtyCTdRVn2sw@.giganews.com...
> steps
of
> detach.
>
http://www.microsoft.com/technet/pro...n/sqlops0.mspx[vbcol=seagreen]
databases
> I'm
>
|||A disaster recovery plan will help you minimize data loss. You need to
plan for various recovery scenarios according to the amount of data loss
that is acceptable to you.
The worst case is that you lose your computer completely due to a disaster
such as for or theft. Your only recourse in this situation is to reinstall
SQL Server on a working machine and restore from backups you've kept in a
safe location.
If your computer crashes and/or you lose your SQL Server drive, you might
get lucky with a successful attach of the database files if your database
files are intact. However, you should not rely on this and plan on
restoring your database from backup because you might not be able to attach
databases which were not detached properly.
The bottom line is that you need to backup your databases periodically and
archive the backup files to a safe location.
Hope this helps.
Dan Guzman
SQL Server MVP
"Niels" <nkistrup@.comcast.net> wrote in message
news:NeudnYnNW-kXTiTdRVn2tQ@.giganews.com...
> Peter,
> So much for my mastery of English. I don't think I'm explaining the
> situation correctly, sorry.
> I'm running Win 2000 Pro, with the developer's edition of MS SQL Server,
but
> I have 4 hard drives ... and it's all on my home computer (I'm the
'network
> guy'). Maybe another server instance is not the correct terminology?
> Currently my data is on D:, but I would like to use one of the other hard
> drives to actively store data.
> If the computer crashes, I'm screwed, but I can always move the hard drive
> to another machine. Heck the drive where the data is 6 1/2 yrs old, and
has
> migrated across machines in the past. (The hard drive.)
> Niels
>
|||Dan,
Lets talk 'preemptive correction'. My data drive is 6 1/2 yrs old & have
the replacement drive ready for swapping. How do you copy the server
instance onto a new drive. From what I can see, it is not as easy as
copying the SQL data folder to another drive, then onto the new one. (Or is
it?)
I am still curious about creating other server instances on other hard
drives. That way, I could spread the data across hard drives. Yes, I need
to transfer my data to a new drive, which will have the same drive. But
just because I cannot figure how out how to create new server instances,
makes me curious about the procedure. I work as a T-SQL developer, but my
DBA skills are minimal, which is why I'm being such a persistent pest about
this.
Hard drive crashes remain my #1 disaster threat. Failure of the computer is
also possible, but like you said, regular backups minimize problems from
that.
Niels
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:OPBjaKmREHA.2848@.TK2MSFTNGP10.phx.gbl...
> A disaster recovery plan will help you minimize data loss. You need to
> plan for various recovery scenarios according to the amount of data loss
> that is acceptable to you.
> The worst case is that you lose your computer completely due to a disaster
> such as for or theft. Your only recourse in this situation is to
reinstall
> SQL Server on a working machine and restore from backups you've kept in a
> safe location.
> If your computer crashes and/or you lose your SQL Server drive, you might
> get lucky with a successful attach of the database files if your database
> files are intact. However, you should not rely on this and plan on
> restoring your database from backup because you might not be able to
attach[vbcol=seagreen]
> databases which were not detached properly.
> The bottom line is that you need to backup your databases periodically and
> archive the backup files to a safe location.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Niels" <nkistrup@.comcast.net> wrote in message
> news:NeudnYnNW-kXTiTdRVn2tQ@.giganews.com...
> but
> 'network
hard[vbcol=seagreen]
drive
> has
>
|||I am not sure if you really mean another instance or just moving the data
files. If you want to install a second instance of sql server (binaries)
then you need to rerun the setup and point it to the other drive for the
install. If you just want to move the data files you can find what you need
here:
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.databasejournal.com/featu...le.php/2228611
Transferring Logins
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/scri...p?scriptid=599
Restoring a .mdf
This still does not mean you should not have valid backups. See BACKUP and
RESTORE in BooksOnLine for more info.
Andrew J. Kelly
SQL Server MVP
"Niels" <nkistrup@.comcast.net> wrote in message
news:GY6dneIma9N3zSfdRVn2tA@.giganews.com...
> Dan,
> Lets talk 'preemptive correction'. My data drive is 6 1/2 yrs old & have
> the replacement drive ready for swapping. How do you copy the server
> instance onto a new drive. From what I can see, it is not as easy as
> copying the SQL data folder to another drive, then onto the new one. (Or
is
> it?)
> I am still curious about creating other server instances on other hard
> drives. That way, I could spread the data across hard drives. Yes, I
need
> to transfer my data to a new drive, which will have the same drive. But
> just because I cannot figure how out how to create new server instances,
> makes me curious about the procedure. I work as a T-SQL developer, but my
> DBA skills are minimal, which is why I'm being such a persistent pest
about
> this.
> Hard drive crashes remain my #1 disaster threat. Failure of the computer
is[vbcol=seagreen]
> also possible, but like you said, regular backups minimize problems from
> that.
> Niels
> "Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
> news:OPBjaKmREHA.2848@.TK2MSFTNGP10.phx.gbl...
disaster[vbcol=seagreen]
> reinstall
a[vbcol=seagreen]
might[vbcol=seagreen]
database[vbcol=seagreen]
> attach
and[vbcol=seagreen]
Server,[vbcol=seagreen]
> hard
> drive
and
>
Adding another server instance to another hard drive?
Problem: For safety reasons, I want an exact copy of all SQL databases on
another hard drive. I'm trying to guard against a hard drive crash.
Currently, I detach, file copy to another drive, then reattach each
individual database. Since SQL Server is running on different hard drive
from the data, I know that I wouldn't have to reinstall it.
1) Is there a way to do what I am asking?
2) Is this the correct the newsgroup to post these questions?
3) Is there a book that covers this?
Tried various keywords, but couldn't find anything in Books Online. I'm
running MS SQL Server Developer's ed. under Windows 2000 Pro.
NielsThat is what backups are for. It's much easier to simply do a backup of
each database (including Master & MSDB) and store those in a different
location. Preferably on a different machine or medium altogether, You don't
have to take the databases off line for a backup like you do with detach.
You might want to take a look at this:
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
--
Andrew J. Kelly
SQL Server MVP
"Niels" <nkistrup@.comcast.net> wrote in message
news:6v-dnY1yOZGJGCXdRVn2sQ@.giganews.com...
> Problem: For safety reasons, I want an exact copy of all SQL databases on
> another hard drive. I'm trying to guard against a hard drive crash.
> Currently, I detach, file copy to another drive, then reattach each
> individual database. Since SQL Server is running on different hard drive
> from the data, I know that I wouldn't have to reinstall it.
> 1) Is there a way to do what I am asking?
> 2) Is this the correct the newsgroup to post these questions?
> 3) Is there a book that covers this?
> Tried various keywords, but couldn't find anything in Books Online. I'm
> running MS SQL Server Developer's ed. under Windows 2000 Pro.
> Niels
>|||Thanks Andrew,
But I will still like to create another server. Where I can find the steps
to add additional server instances?
Niels
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:ev$827XREHA.568@.TK2MSFTNGP12.phx.gbl...
> That is what backups are for. It's much easier to simply do a backup of
> each database (including Master & MSDB) and store those in a different
> location. Preferably on a different machine or medium altogether, You
don't
> have to take the databases off line for a backup like you do with detach.
> You might want to take a look at this:
>
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "Niels" <nkistrup@.comcast.net> wrote in message
> news:6v-dnY1yOZGJGCXdRVn2sQ@.giganews.com...
> > Problem: For safety reasons, I want an exact copy of all SQL databases
on
> > another hard drive. I'm trying to guard against a hard drive crash.
> > Currently, I detach, file copy to another drive, then reattach each
> > individual database. Since SQL Server is running on different hard
drive
> > from the data, I know that I wouldn't have to reinstall it.
> >
> > 1) Is there a way to do what I am asking?
> > 2) Is this the correct the newsgroup to post these questions?
> > 3) Is there a book that covers this?
> >
> > Tried various keywords, but couldn't find anything in Books Online. I'm
> > running MS SQL Server Developer's ed. under Windows 2000 Pro.
> >
> > Niels
> >
> >
>|||There a couple of options that you might want to consider.
Firstly if your running NT 4, 2000 or 2003, then ask your network guys to
raid the disks, I wouldn't do into it in too much detail but there are
plenty of examples. What a raid does in automatically (non SQL Server) copy
stuff from one hard drive to another.
If you wish to create another instance on your current machine then that
will not really help as if the machine goes then both instances go.
If you want to create another server then you will need another machine to
do it then you just install SQL Server the normal way, that will create a
default instance on that machine.
If you want to keep your database running in case of server crashes then
create a new server and backup your databases on the other server.(using the
backup database command).
If you want a server to kick in automatically when your existing server dies
then look on Microsoft for Replication, and High Availabity Server.
"Niels" <nkistrup@.comcast.net> wrote in message
news:8fKdnfr3UYxtyCTdRVn2sw@.giganews.com...
> Thanks Andrew,
> But I will still like to create another server. Where I can find the
steps
> to add additional server instances?
> Niels
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:ev$827XREHA.568@.TK2MSFTNGP12.phx.gbl...
> > That is what backups are for. It's much easier to simply do a backup of
> > each database (including Master & MSDB) and store those in a different
> > location. Preferably on a different machine or medium altogether, You
> don't
> > have to take the databases off line for a backup like you do with
detach.
> > You might want to take a look at this:
> >
> >
>
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
> >
> > --
> >
> > Andrew J. Kelly
> > SQL Server MVP
> >
> >
> > "Niels" <nkistrup@.comcast.net> wrote in message
> > news:6v-dnY1yOZGJGCXdRVn2sQ@.giganews.com...
> > > Problem: For safety reasons, I want an exact copy of all SQL databases
> on
> > > another hard drive. I'm trying to guard against a hard drive crash.
> > > Currently, I detach, file copy to another drive, then reattach each
> > > individual database. Since SQL Server is running on different hard
> drive
> > > from the data, I know that I wouldn't have to reinstall it.
> > >
> > > 1) Is there a way to do what I am asking?
> > > 2) Is this the correct the newsgroup to post these questions?
> > > 3) Is there a book that covers this?
> > >
> > > Tried various keywords, but couldn't find anything in Books Online.
I'm
> > > running MS SQL Server Developer's ed. under Windows 2000 Pro.
> > >
> > > Niels
> > >
> > >
> >
> >
>|||Peter,
So much for my mastery of English. I don't think I'm explaining the
situation correctly, sorry.
I'm running Win 2000 Pro, with the developer's edition of MS SQL Server, but
I have 4 hard drives ... and it's all on my home computer (I'm the 'network
guy'). Maybe another server instance is not the correct terminology?
Currently my data is on D:, but I would like to use one of the other hard
drives to actively store data.
If the computer crashes, I'm screwed, but I can always move the hard drive
to another machine. Heck the drive where the data is 6 1/2 yrs old, and has
migrated across machines in the past. (The hard drive.)
Niels
"Peter Nolan" <peter.nolan90@.ntlworld.com> wrote in message
news:x4luc.65$PA4.57@.newsfe1-gui.server.ntli.net...
> There a couple of options that you might want to consider.
> Firstly if your running NT 4, 2000 or 2003, then ask your network guys to
> raid the disks, I wouldn't do into it in too much detail but there are
> plenty of examples. What a raid does in automatically (non SQL Server)
copy
> stuff from one hard drive to another.
> If you wish to create another instance on your current machine then that
> will not really help as if the machine goes then both instances go.
> If you want to create another server then you will need another machine to
> do it then you just install SQL Server the normal way, that will create a
> default instance on that machine.
> If you want to keep your database running in case of server crashes then
> create a new server and backup your databases on the other server.(using
the
> backup database command).
> If you want a server to kick in automatically when your existing server
dies
> then look on Microsoft for Replication, and High Availabity Server.
>
> "Niels" <nkistrup@.comcast.net> wrote in message
> news:8fKdnfr3UYxtyCTdRVn2sw@.giganews.com...
> > Thanks Andrew,
> >
> > But I will still like to create another server. Where I can find the
> steps
> > to add additional server instances?
> >
> > Niels
> >
> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> > news:ev$827XREHA.568@.TK2MSFTNGP12.phx.gbl...
> > > That is what backups are for. It's much easier to simply do a backup
of
> > > each database (including Master & MSDB) and store those in a different
> > > location. Preferably on a different machine or medium altogether, You
> > don't
> > > have to take the databases off line for a backup like you do with
> detach.
> > > You might want to take a look at this:
> > >
> > >
> >
>
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
> > >
> > > --
> > >
> > > Andrew J. Kelly
> > > SQL Server MVP
> > >
> > >
> > > "Niels" <nkistrup@.comcast.net> wrote in message
> > > news:6v-dnY1yOZGJGCXdRVn2sQ@.giganews.com...
> > > > Problem: For safety reasons, I want an exact copy of all SQL
databases
> > on
> > > > another hard drive. I'm trying to guard against a hard drive crash.
> > > > Currently, I detach, file copy to another drive, then reattach each
> > > > individual database. Since SQL Server is running on different hard
> > drive
> > > > from the data, I know that I wouldn't have to reinstall it.
> > > >
> > > > 1) Is there a way to do what I am asking?
> > > > 2) Is this the correct the newsgroup to post these questions?
> > > > 3) Is there a book that covers this?
> > > >
> > > > Tried various keywords, but couldn't find anything in Books Online.
> I'm
> > > > running MS SQL Server Developer's ed. under Windows 2000 Pro.
> > > >
> > > > Niels
> > > >
> > > >
> > >
> > >
> >
> >
>|||A disaster recovery plan will help you minimize data loss. You need to
plan for various recovery scenarios according to the amount of data loss
that is acceptable to you.
The worst case is that you lose your computer completely due to a disaster
such as for or theft. Your only recourse in this situation is to reinstall
SQL Server on a working machine and restore from backups you've kept in a
safe location.
If your computer crashes and/or you lose your SQL Server drive, you might
get lucky with a successful attach of the database files if your database
files are intact. However, you should not rely on this and plan on
restoring your database from backup because you might not be able to attach
databases which were not detached properly.
The bottom line is that you need to backup your databases periodically and
archive the backup files to a safe location.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Niels" <nkistrup@.comcast.net> wrote in message
news:NeudnYnNW-kXTiTdRVn2tQ@.giganews.com...
> Peter,
> So much for my mastery of English. I don't think I'm explaining the
> situation correctly, sorry.
> I'm running Win 2000 Pro, with the developer's edition of MS SQL Server,
but
> I have 4 hard drives ... and it's all on my home computer (I'm the
'network
> guy'). Maybe another server instance is not the correct terminology?
> Currently my data is on D:, but I would like to use one of the other hard
> drives to actively store data.
> If the computer crashes, I'm screwed, but I can always move the hard drive
> to another machine. Heck the drive where the data is 6 1/2 yrs old, and
has
> migrated across machines in the past. (The hard drive.)
> Niels
>|||Dan,
Lets talk 'preemptive correction'. My data drive is 6 1/2 yrs old & have
the replacement drive ready for swapping. How do you copy the server
instance onto a new drive. From what I can see, it is not as easy as
copying the SQL data folder to another drive, then onto the new one. (Or is
it?)
I am still curious about creating other server instances on other hard
drives. That way, I could spread the data across hard drives. Yes, I need
to transfer my data to a new drive, which will have the same drive. But
just because I cannot figure how out how to create new server instances,
makes me curious about the procedure. I work as a T-SQL developer, but my
DBA skills are minimal, which is why I'm being such a persistent pest about
this.
Hard drive crashes remain my #1 disaster threat. Failure of the computer is
also possible, but like you said, regular backups minimize problems from
that.
Niels
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:OPBjaKmREHA.2848@.TK2MSFTNGP10.phx.gbl...
> A disaster recovery plan will help you minimize data loss. You need to
> plan for various recovery scenarios according to the amount of data loss
> that is acceptable to you.
> The worst case is that you lose your computer completely due to a disaster
> such as for or theft. Your only recourse in this situation is to
reinstall
> SQL Server on a working machine and restore from backups you've kept in a
> safe location.
> If your computer crashes and/or you lose your SQL Server drive, you might
> get lucky with a successful attach of the database files if your database
> files are intact. However, you should not rely on this and plan on
> restoring your database from backup because you might not be able to
attach
> databases which were not detached properly.
> The bottom line is that you need to backup your databases periodically and
> archive the backup files to a safe location.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Niels" <nkistrup@.comcast.net> wrote in message
> news:NeudnYnNW-kXTiTdRVn2tQ@.giganews.com...
> > Peter,
> >
> > So much for my mastery of English. I don't think I'm explaining the
> > situation correctly, sorry.
> >
> > I'm running Win 2000 Pro, with the developer's edition of MS SQL Server,
> but
> > I have 4 hard drives ... and it's all on my home computer (I'm the
> 'network
> > guy'). Maybe another server instance is not the correct terminology?
> > Currently my data is on D:, but I would like to use one of the other
hard
> > drives to actively store data.
> >
> > If the computer crashes, I'm screwed, but I can always move the hard
drive
> > to another machine. Heck the drive where the data is 6 1/2 yrs old, and
> has
> > migrated across machines in the past. (The hard drive.)
> >
> > Niels
> >
>|||I am not sure if you really mean another instance or just moving the data
files. If you want to install a second instance of sql server (binaries)
then you need to rerun the setup and point it to the other drive for the
install. If you just want to move the data files you can find what you need
here:
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.databasejournal.com/features/mssql/article.php/2228611
Transferring Logins
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
This still does not mean you should not have valid backups. See BACKUP and
RESTORE in BooksOnLine for more info.
Andrew J. Kelly
SQL Server MVP
"Niels" <nkistrup@.comcast.net> wrote in message
news:GY6dneIma9N3zSfdRVn2tA@.giganews.com...
> Dan,
> Lets talk 'preemptive correction'. My data drive is 6 1/2 yrs old & have
> the replacement drive ready for swapping. How do you copy the server
> instance onto a new drive. From what I can see, it is not as easy as
> copying the SQL data folder to another drive, then onto the new one. (Or
is
> it?)
> I am still curious about creating other server instances on other hard
> drives. That way, I could spread the data across hard drives. Yes, I
need
> to transfer my data to a new drive, which will have the same drive. But
> just because I cannot figure how out how to create new server instances,
> makes me curious about the procedure. I work as a T-SQL developer, but my
> DBA skills are minimal, which is why I'm being such a persistent pest
about
> this.
> Hard drive crashes remain my #1 disaster threat. Failure of the computer
is
> also possible, but like you said, regular backups minimize problems from
> that.
> Niels
> "Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
> news:OPBjaKmREHA.2848@.TK2MSFTNGP10.phx.gbl...
> > A disaster recovery plan will help you minimize data loss. You need to
> > plan for various recovery scenarios according to the amount of data loss
> > that is acceptable to you.
> >
> > The worst case is that you lose your computer completely due to a
disaster
> > such as for or theft. Your only recourse in this situation is to
> reinstall
> > SQL Server on a working machine and restore from backups you've kept in
a
> > safe location.
> >
> > If your computer crashes and/or you lose your SQL Server drive, you
might
> > get lucky with a successful attach of the database files if your
database
> > files are intact. However, you should not rely on this and plan on
> > restoring your database from backup because you might not be able to
> attach
> > databases which were not detached properly.
> >
> > The bottom line is that you need to backup your databases periodically
and
> > archive the backup files to a safe location.
> >
> > --
> > Hope this helps.
> >
> > Dan Guzman
> > SQL Server MVP
> >
> > "Niels" <nkistrup@.comcast.net> wrote in message
> > news:NeudnYnNW-kXTiTdRVn2tQ@.giganews.com...
> > > Peter,
> > >
> > > So much for my mastery of English. I don't think I'm explaining the
> > > situation correctly, sorry.
> > >
> > > I'm running Win 2000 Pro, with the developer's edition of MS SQL
Server,
> > but
> > > I have 4 hard drives ... and it's all on my home computer (I'm the
> > 'network
> > > guy'). Maybe another server instance is not the correct terminology?
> > > Currently my data is on D:, but I would like to use one of the other
> hard
> > > drives to actively store data.
> > >
> > > If the computer crashes, I'm screwed, but I can always move the hard
> drive
> > > to another machine. Heck the drive where the data is 6 1/2 yrs old,
and
> > has
> > > migrated across machines in the past. (The hard drive.)
> > >
> > > Niels
> > >
> >
> >
>
another hard drive. I'm trying to guard against a hard drive crash.
Currently, I detach, file copy to another drive, then reattach each
individual database. Since SQL Server is running on different hard drive
from the data, I know that I wouldn't have to reinstall it.
1) Is there a way to do what I am asking?
2) Is this the correct the newsgroup to post these questions?
3) Is there a book that covers this?
Tried various keywords, but couldn't find anything in Books Online. I'm
running MS SQL Server Developer's ed. under Windows 2000 Pro.
NielsThat is what backups are for. It's much easier to simply do a backup of
each database (including Master & MSDB) and store those in a different
location. Preferably on a different machine or medium altogether, You don't
have to take the databases off line for a backup like you do with detach.
You might want to take a look at this:
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
--
Andrew J. Kelly
SQL Server MVP
"Niels" <nkistrup@.comcast.net> wrote in message
news:6v-dnY1yOZGJGCXdRVn2sQ@.giganews.com...
> Problem: For safety reasons, I want an exact copy of all SQL databases on
> another hard drive. I'm trying to guard against a hard drive crash.
> Currently, I detach, file copy to another drive, then reattach each
> individual database. Since SQL Server is running on different hard drive
> from the data, I know that I wouldn't have to reinstall it.
> 1) Is there a way to do what I am asking?
> 2) Is this the correct the newsgroup to post these questions?
> 3) Is there a book that covers this?
> Tried various keywords, but couldn't find anything in Books Online. I'm
> running MS SQL Server Developer's ed. under Windows 2000 Pro.
> Niels
>|||Thanks Andrew,
But I will still like to create another server. Where I can find the steps
to add additional server instances?
Niels
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:ev$827XREHA.568@.TK2MSFTNGP12.phx.gbl...
> That is what backups are for. It's much easier to simply do a backup of
> each database (including Master & MSDB) and store those in a different
> location. Preferably on a different machine or medium altogether, You
don't
> have to take the databases off line for a backup like you do with detach.
> You might want to take a look at this:
>
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "Niels" <nkistrup@.comcast.net> wrote in message
> news:6v-dnY1yOZGJGCXdRVn2sQ@.giganews.com...
> > Problem: For safety reasons, I want an exact copy of all SQL databases
on
> > another hard drive. I'm trying to guard against a hard drive crash.
> > Currently, I detach, file copy to another drive, then reattach each
> > individual database. Since SQL Server is running on different hard
drive
> > from the data, I know that I wouldn't have to reinstall it.
> >
> > 1) Is there a way to do what I am asking?
> > 2) Is this the correct the newsgroup to post these questions?
> > 3) Is there a book that covers this?
> >
> > Tried various keywords, but couldn't find anything in Books Online. I'm
> > running MS SQL Server Developer's ed. under Windows 2000 Pro.
> >
> > Niels
> >
> >
>|||There a couple of options that you might want to consider.
Firstly if your running NT 4, 2000 or 2003, then ask your network guys to
raid the disks, I wouldn't do into it in too much detail but there are
plenty of examples. What a raid does in automatically (non SQL Server) copy
stuff from one hard drive to another.
If you wish to create another instance on your current machine then that
will not really help as if the machine goes then both instances go.
If you want to create another server then you will need another machine to
do it then you just install SQL Server the normal way, that will create a
default instance on that machine.
If you want to keep your database running in case of server crashes then
create a new server and backup your databases on the other server.(using the
backup database command).
If you want a server to kick in automatically when your existing server dies
then look on Microsoft for Replication, and High Availabity Server.
"Niels" <nkistrup@.comcast.net> wrote in message
news:8fKdnfr3UYxtyCTdRVn2sw@.giganews.com...
> Thanks Andrew,
> But I will still like to create another server. Where I can find the
steps
> to add additional server instances?
> Niels
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:ev$827XREHA.568@.TK2MSFTNGP12.phx.gbl...
> > That is what backups are for. It's much easier to simply do a backup of
> > each database (including Master & MSDB) and store those in a different
> > location. Preferably on a different machine or medium altogether, You
> don't
> > have to take the databases off line for a backup like you do with
detach.
> > You might want to take a look at this:
> >
> >
>
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
> >
> > --
> >
> > Andrew J. Kelly
> > SQL Server MVP
> >
> >
> > "Niels" <nkistrup@.comcast.net> wrote in message
> > news:6v-dnY1yOZGJGCXdRVn2sQ@.giganews.com...
> > > Problem: For safety reasons, I want an exact copy of all SQL databases
> on
> > > another hard drive. I'm trying to guard against a hard drive crash.
> > > Currently, I detach, file copy to another drive, then reattach each
> > > individual database. Since SQL Server is running on different hard
> drive
> > > from the data, I know that I wouldn't have to reinstall it.
> > >
> > > 1) Is there a way to do what I am asking?
> > > 2) Is this the correct the newsgroup to post these questions?
> > > 3) Is there a book that covers this?
> > >
> > > Tried various keywords, but couldn't find anything in Books Online.
I'm
> > > running MS SQL Server Developer's ed. under Windows 2000 Pro.
> > >
> > > Niels
> > >
> > >
> >
> >
>|||Peter,
So much for my mastery of English. I don't think I'm explaining the
situation correctly, sorry.
I'm running Win 2000 Pro, with the developer's edition of MS SQL Server, but
I have 4 hard drives ... and it's all on my home computer (I'm the 'network
guy'). Maybe another server instance is not the correct terminology?
Currently my data is on D:, but I would like to use one of the other hard
drives to actively store data.
If the computer crashes, I'm screwed, but I can always move the hard drive
to another machine. Heck the drive where the data is 6 1/2 yrs old, and has
migrated across machines in the past. (The hard drive.)
Niels
"Peter Nolan" <peter.nolan90@.ntlworld.com> wrote in message
news:x4luc.65$PA4.57@.newsfe1-gui.server.ntli.net...
> There a couple of options that you might want to consider.
> Firstly if your running NT 4, 2000 or 2003, then ask your network guys to
> raid the disks, I wouldn't do into it in too much detail but there are
> plenty of examples. What a raid does in automatically (non SQL Server)
copy
> stuff from one hard drive to another.
> If you wish to create another instance on your current machine then that
> will not really help as if the machine goes then both instances go.
> If you want to create another server then you will need another machine to
> do it then you just install SQL Server the normal way, that will create a
> default instance on that machine.
> If you want to keep your database running in case of server crashes then
> create a new server and backup your databases on the other server.(using
the
> backup database command).
> If you want a server to kick in automatically when your existing server
dies
> then look on Microsoft for Replication, and High Availabity Server.
>
> "Niels" <nkistrup@.comcast.net> wrote in message
> news:8fKdnfr3UYxtyCTdRVn2sw@.giganews.com...
> > Thanks Andrew,
> >
> > But I will still like to create another server. Where I can find the
> steps
> > to add additional server instances?
> >
> > Niels
> >
> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> > news:ev$827XREHA.568@.TK2MSFTNGP12.phx.gbl...
> > > That is what backups are for. It's much easier to simply do a backup
of
> > > each database (including Master & MSDB) and store those in a different
> > > location. Preferably on a different machine or medium altogether, You
> > don't
> > > have to take the databases off line for a backup like you do with
> detach.
> > > You might want to take a look at this:
> > >
> > >
> >
>
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
> > >
> > > --
> > >
> > > Andrew J. Kelly
> > > SQL Server MVP
> > >
> > >
> > > "Niels" <nkistrup@.comcast.net> wrote in message
> > > news:6v-dnY1yOZGJGCXdRVn2sQ@.giganews.com...
> > > > Problem: For safety reasons, I want an exact copy of all SQL
databases
> > on
> > > > another hard drive. I'm trying to guard against a hard drive crash.
> > > > Currently, I detach, file copy to another drive, then reattach each
> > > > individual database. Since SQL Server is running on different hard
> > drive
> > > > from the data, I know that I wouldn't have to reinstall it.
> > > >
> > > > 1) Is there a way to do what I am asking?
> > > > 2) Is this the correct the newsgroup to post these questions?
> > > > 3) Is there a book that covers this?
> > > >
> > > > Tried various keywords, but couldn't find anything in Books Online.
> I'm
> > > > running MS SQL Server Developer's ed. under Windows 2000 Pro.
> > > >
> > > > Niels
> > > >
> > > >
> > >
> > >
> >
> >
>|||A disaster recovery plan will help you minimize data loss. You need to
plan for various recovery scenarios according to the amount of data loss
that is acceptable to you.
The worst case is that you lose your computer completely due to a disaster
such as for or theft. Your only recourse in this situation is to reinstall
SQL Server on a working machine and restore from backups you've kept in a
safe location.
If your computer crashes and/or you lose your SQL Server drive, you might
get lucky with a successful attach of the database files if your database
files are intact. However, you should not rely on this and plan on
restoring your database from backup because you might not be able to attach
databases which were not detached properly.
The bottom line is that you need to backup your databases periodically and
archive the backup files to a safe location.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Niels" <nkistrup@.comcast.net> wrote in message
news:NeudnYnNW-kXTiTdRVn2tQ@.giganews.com...
> Peter,
> So much for my mastery of English. I don't think I'm explaining the
> situation correctly, sorry.
> I'm running Win 2000 Pro, with the developer's edition of MS SQL Server,
but
> I have 4 hard drives ... and it's all on my home computer (I'm the
'network
> guy'). Maybe another server instance is not the correct terminology?
> Currently my data is on D:, but I would like to use one of the other hard
> drives to actively store data.
> If the computer crashes, I'm screwed, but I can always move the hard drive
> to another machine. Heck the drive where the data is 6 1/2 yrs old, and
has
> migrated across machines in the past. (The hard drive.)
> Niels
>|||Dan,
Lets talk 'preemptive correction'. My data drive is 6 1/2 yrs old & have
the replacement drive ready for swapping. How do you copy the server
instance onto a new drive. From what I can see, it is not as easy as
copying the SQL data folder to another drive, then onto the new one. (Or is
it?)
I am still curious about creating other server instances on other hard
drives. That way, I could spread the data across hard drives. Yes, I need
to transfer my data to a new drive, which will have the same drive. But
just because I cannot figure how out how to create new server instances,
makes me curious about the procedure. I work as a T-SQL developer, but my
DBA skills are minimal, which is why I'm being such a persistent pest about
this.
Hard drive crashes remain my #1 disaster threat. Failure of the computer is
also possible, but like you said, regular backups minimize problems from
that.
Niels
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:OPBjaKmREHA.2848@.TK2MSFTNGP10.phx.gbl...
> A disaster recovery plan will help you minimize data loss. You need to
> plan for various recovery scenarios according to the amount of data loss
> that is acceptable to you.
> The worst case is that you lose your computer completely due to a disaster
> such as for or theft. Your only recourse in this situation is to
reinstall
> SQL Server on a working machine and restore from backups you've kept in a
> safe location.
> If your computer crashes and/or you lose your SQL Server drive, you might
> get lucky with a successful attach of the database files if your database
> files are intact. However, you should not rely on this and plan on
> restoring your database from backup because you might not be able to
attach
> databases which were not detached properly.
> The bottom line is that you need to backup your databases periodically and
> archive the backup files to a safe location.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Niels" <nkistrup@.comcast.net> wrote in message
> news:NeudnYnNW-kXTiTdRVn2tQ@.giganews.com...
> > Peter,
> >
> > So much for my mastery of English. I don't think I'm explaining the
> > situation correctly, sorry.
> >
> > I'm running Win 2000 Pro, with the developer's edition of MS SQL Server,
> but
> > I have 4 hard drives ... and it's all on my home computer (I'm the
> 'network
> > guy'). Maybe another server instance is not the correct terminology?
> > Currently my data is on D:, but I would like to use one of the other
hard
> > drives to actively store data.
> >
> > If the computer crashes, I'm screwed, but I can always move the hard
drive
> > to another machine. Heck the drive where the data is 6 1/2 yrs old, and
> has
> > migrated across machines in the past. (The hard drive.)
> >
> > Niels
> >
>|||I am not sure if you really mean another instance or just moving the data
files. If you want to install a second instance of sql server (binaries)
then you need to rerun the setup and point it to the other drive for the
install. If you just want to move the data files you can find what you need
here:
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.databasejournal.com/features/mssql/article.php/2228611
Transferring Logins
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
This still does not mean you should not have valid backups. See BACKUP and
RESTORE in BooksOnLine for more info.
Andrew J. Kelly
SQL Server MVP
"Niels" <nkistrup@.comcast.net> wrote in message
news:GY6dneIma9N3zSfdRVn2tA@.giganews.com...
> Dan,
> Lets talk 'preemptive correction'. My data drive is 6 1/2 yrs old & have
> the replacement drive ready for swapping. How do you copy the server
> instance onto a new drive. From what I can see, it is not as easy as
> copying the SQL data folder to another drive, then onto the new one. (Or
is
> it?)
> I am still curious about creating other server instances on other hard
> drives. That way, I could spread the data across hard drives. Yes, I
need
> to transfer my data to a new drive, which will have the same drive. But
> just because I cannot figure how out how to create new server instances,
> makes me curious about the procedure. I work as a T-SQL developer, but my
> DBA skills are minimal, which is why I'm being such a persistent pest
about
> this.
> Hard drive crashes remain my #1 disaster threat. Failure of the computer
is
> also possible, but like you said, regular backups minimize problems from
> that.
> Niels
> "Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
> news:OPBjaKmREHA.2848@.TK2MSFTNGP10.phx.gbl...
> > A disaster recovery plan will help you minimize data loss. You need to
> > plan for various recovery scenarios according to the amount of data loss
> > that is acceptable to you.
> >
> > The worst case is that you lose your computer completely due to a
disaster
> > such as for or theft. Your only recourse in this situation is to
> reinstall
> > SQL Server on a working machine and restore from backups you've kept in
a
> > safe location.
> >
> > If your computer crashes and/or you lose your SQL Server drive, you
might
> > get lucky with a successful attach of the database files if your
database
> > files are intact. However, you should not rely on this and plan on
> > restoring your database from backup because you might not be able to
> attach
> > databases which were not detached properly.
> >
> > The bottom line is that you need to backup your databases periodically
and
> > archive the backup files to a safe location.
> >
> > --
> > Hope this helps.
> >
> > Dan Guzman
> > SQL Server MVP
> >
> > "Niels" <nkistrup@.comcast.net> wrote in message
> > news:NeudnYnNW-kXTiTdRVn2tQ@.giganews.com...
> > > Peter,
> > >
> > > So much for my mastery of English. I don't think I'm explaining the
> > > situation correctly, sorry.
> > >
> > > I'm running Win 2000 Pro, with the developer's edition of MS SQL
Server,
> > but
> > > I have 4 hard drives ... and it's all on my home computer (I'm the
> > 'network
> > > guy'). Maybe another server instance is not the correct terminology?
> > > Currently my data is on D:, but I would like to use one of the other
> hard
> > > drives to actively store data.
> > >
> > > If the computer crashes, I'm screwed, but I can always move the hard
> drive
> > > to another machine. Heck the drive where the data is 6 1/2 yrs old,
and
> > has
> > > migrated across machines in the past. (The hard drive.)
> > >
> > > Niels
> > >
> >
> >
>
Adding and additional drive
On a database server, I have mapped a new drive letter to
a SAN so that I can backup my database. When I go into
Enterprise Manager, I can see the drive, but when I try to
create a new backup device, it gives me an error stating
that 'the directory in whch you want to create this file
does not exist'.
If I try to create a new data or log file for a database
on that server, I do not see the drive.
Should I just reboot the server or is it something else?
SQL Server will probably not see mapped drives... it is running under a
different account than what you used when you mapped the drive.
The BEST way to do this is to make sure that the account SQL Server is
running under has rights to the remote share.
Simply issue a backup using the UNC
BACKUP DATABASE master TO DISK = '\\RemoteServer\SomeShare\master.bak' WITH
INIT
Keith
"canaries" <anonymous@.discussions.microsoft.com> wrote in message
news:225801c49a93$8ec19da0$a501280a@.phx.gbl...
> On a database server, I have mapped a new drive letter to
> a SAN so that I can backup my database. When I go into
> Enterprise Manager, I can see the drive, but when I try to
> create a new backup device, it gives me an error stating
> that 'the directory in whch you want to create this file
> does not exist'.
> If I try to create a new data or log file for a database
> on that server, I do not see the drive.
> Should I just reboot the server or is it something else?
>
|||http://support.microsoft.com/default...b;en-us;555128
Everything you ever wanted to know about backing up to remote shares.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"canaries" <anonymous@.discussions.microsoft.com> wrote in message
news:225801c49a93$8ec19da0$a501280a@.phx.gbl...
> On a database server, I have mapped a new drive letter to
> a SAN so that I can backup my database. When I go into
> Enterprise Manager, I can see the drive, but when I try to
> create a new backup device, it gives me an error stating
> that 'the directory in whch you want to create this file
> does not exist'.
> If I try to create a new data or log file for a database
> on that server, I do not see the drive.
> Should I just reboot the server or is it something else?
>
a SAN so that I can backup my database. When I go into
Enterprise Manager, I can see the drive, but when I try to
create a new backup device, it gives me an error stating
that 'the directory in whch you want to create this file
does not exist'.
If I try to create a new data or log file for a database
on that server, I do not see the drive.
Should I just reboot the server or is it something else?
SQL Server will probably not see mapped drives... it is running under a
different account than what you used when you mapped the drive.
The BEST way to do this is to make sure that the account SQL Server is
running under has rights to the remote share.
Simply issue a backup using the UNC
BACKUP DATABASE master TO DISK = '\\RemoteServer\SomeShare\master.bak' WITH
INIT
Keith
"canaries" <anonymous@.discussions.microsoft.com> wrote in message
news:225801c49a93$8ec19da0$a501280a@.phx.gbl...
> On a database server, I have mapped a new drive letter to
> a SAN so that I can backup my database. When I go into
> Enterprise Manager, I can see the drive, but when I try to
> create a new backup device, it gives me an error stating
> that 'the directory in whch you want to create this file
> does not exist'.
> If I try to create a new data or log file for a database
> on that server, I do not see the drive.
> Should I just reboot the server or is it something else?
>
|||http://support.microsoft.com/default...b;en-us;555128
Everything you ever wanted to know about backing up to remote shares.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"canaries" <anonymous@.discussions.microsoft.com> wrote in message
news:225801c49a93$8ec19da0$a501280a@.phx.gbl...
> On a database server, I have mapped a new drive letter to
> a SAN so that I can backup my database. When I go into
> Enterprise Manager, I can see the drive, but when I try to
> create a new backup device, it gives me an error stating
> that 'the directory in whch you want to create this file
> does not exist'.
> If I try to create a new data or log file for a database
> on that server, I do not see the drive.
> Should I just reboot the server or is it something else?
>
Adding and additional drive
On a database server, I have mapped a new drive letter to
a SAN so that I can backup my database. When I go into
Enterprise Manager, I can see the drive, but when I try to
create a new backup device, it gives me an error stating
that 'the directory in whch you want to create this file
does not exist'.
If I try to create a new data or log file for a database
on that server, I do not see the drive.
Should I just reboot the server or is it something else?SQL Server will probably not see mapped drives... it is running under a
different account than what you used when you mapped the drive.
The BEST way to do this is to make sure that the account SQL Server is
running under has rights to the remote share.
Simply issue a backup using the UNC
BACKUP DATABASE master TO DISK = '\\RemoteServer\SomeShare\master.bak' WITH
INIT
--
Keith
"canaries" <anonymous@.discussions.microsoft.com> wrote in message
news:225801c49a93$8ec19da0$a501280a@.phx.gbl...
> On a database server, I have mapped a new drive letter to
> a SAN so that I can backup my database. When I go into
> Enterprise Manager, I can see the drive, but when I try to
> create a new backup device, it gives me an error stating
> that 'the directory in whch you want to create this file
> does not exist'.
> If I try to create a new data or log file for a database
> on that server, I do not see the drive.
> Should I just reboot the server or is it something else?
>|||http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
Everything you ever wanted to know about backing up to remote shares.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"canaries" <anonymous@.discussions.microsoft.com> wrote in message
news:225801c49a93$8ec19da0$a501280a@.phx.gbl...
> On a database server, I have mapped a new drive letter to
> a SAN so that I can backup my database. When I go into
> Enterprise Manager, I can see the drive, but when I try to
> create a new backup device, it gives me an error stating
> that 'the directory in whch you want to create this file
> does not exist'.
> If I try to create a new data or log file for a database
> on that server, I do not see the drive.
> Should I just reboot the server or is it something else?
>
a SAN so that I can backup my database. When I go into
Enterprise Manager, I can see the drive, but when I try to
create a new backup device, it gives me an error stating
that 'the directory in whch you want to create this file
does not exist'.
If I try to create a new data or log file for a database
on that server, I do not see the drive.
Should I just reboot the server or is it something else?SQL Server will probably not see mapped drives... it is running under a
different account than what you used when you mapped the drive.
The BEST way to do this is to make sure that the account SQL Server is
running under has rights to the remote share.
Simply issue a backup using the UNC
BACKUP DATABASE master TO DISK = '\\RemoteServer\SomeShare\master.bak' WITH
INIT
--
Keith
"canaries" <anonymous@.discussions.microsoft.com> wrote in message
news:225801c49a93$8ec19da0$a501280a@.phx.gbl...
> On a database server, I have mapped a new drive letter to
> a SAN so that I can backup my database. When I go into
> Enterprise Manager, I can see the drive, but when I try to
> create a new backup device, it gives me an error stating
> that 'the directory in whch you want to create this file
> does not exist'.
> If I try to create a new data or log file for a database
> on that server, I do not see the drive.
> Should I just reboot the server or is it something else?
>|||http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
Everything you ever wanted to know about backing up to remote shares.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"canaries" <anonymous@.discussions.microsoft.com> wrote in message
news:225801c49a93$8ec19da0$a501280a@.phx.gbl...
> On a database server, I have mapped a new drive letter to
> a SAN so that I can backup my database. When I go into
> Enterprise Manager, I can see the drive, but when I try to
> create a new backup device, it gives me an error stating
> that 'the directory in whch you want to create this file
> does not exist'.
> If I try to create a new data or log file for a database
> on that server, I do not see the drive.
> Should I just reboot the server or is it something else?
>
Subscribe to:
Posts (Atom)