|
I have tried upgrading a system with a shared network storage but the
upgrade wizard could not continue because the databases should be on a fied hard drive.
QUESTION:I have tried upgrading a system with a shared network storage but the
upgrade wizard could not continue because the databases should be on a fied
hard drive.
I am using Filer from Network Appliance.
Does any body know a way to overcome this problem ( restriction )
ANSWER: Network attached storage wasn't officially supported in 6.5 - hence the
problem. I think you'll have to dump/load to a system with local disks,
upgrade, then copy back.
Q: I have tried upgrading a system with a shared network storage but the
upgrade wizard could not continue because the databases should be on a fied
hard drive.
I am using Filer from Network Appliance.
Does any body know a way to overcome this problem ( restriction )
Q. Can I create SQL Server databases on network drives?
(v1.3 1999.02.02)
A. First ask yourself why on earth you would want to do this? Your
performance will be degraded and you will be more prone to database corruption
due to network glitches (which are far more common than scsi/fibre bus
glitches). Putting i/o's across a network (even a fast network) is typically
orders of magnitude slower than via scsi/fibre and the latency is a lot longer.
SQL Server currently has no concept of sharing a database that is held on
a.n.other server. You need to locally and directly attach the disk subsystem
to the box running SQL Server. Via scsi-extenders and/or fibre this could be
100's of meters or even kilometers away. You can also purchase large disk
subsystems that can be "shared" by many servers (typical vendors of these are
Digital (Compaq) Storageworks and EMC). However these disk subsystems are
physically/logically partitioned so that each scsi/fibre attached server has
it's own set of disks - there is no sharing of data at the disk/file/database
level.
Now saying that it IS possible to store databases on network drives as long as
SQL is fooled into thinking they are in fact local drives. Under 6.5 you must
map a drive letter to a network share - UNC paths will not work. With SQL 7.0
UNC paths will work as long as you use trace flag 1807.
There is more information on this in Q196904. This describes the support being
allowed in SQL 7.0 for use against Network Appliance networked raid units only.
Note that these will suffer the same performance penalties as if you were
accessing a network share on an NT box, as effectively that is what they are.
These boxes run a proprietary operating system on an embedded Alpha chip that
talks the SMB protocol required to handle NT-style network file-io. They
connect to the LAN via a standard Ethernet interface.
|
|
|
|
