Thanks for the links.
I know that MS-SQL supports SAN and we have a system using MS-SQL
and SAN in which the database file is in the network storage and it
works fine.

Elisabete

--- In firebird-support@yahoogroups.com, Daniel Rail <daniel@a...>
wrote:

> Hi,
>
> At October 6, 2004, 07:14, lsbtreis wrote:
>
> > Because it´s a network storage.
>
> And if you read about NAS, you'll also see that it's not really
> recommended for databases.
>
> Here's a paragraph that I found:
> [Start quote...]
> NAS systems generally support multiple operating systems and are
> directly accessible by heterogeneous clients via the LAN. Media can
> usually be replaced or added in these systems without impact to the
> network or application servers. NAS systems are highly suitable for
> most applications except high bandwidth video and larger, multi-

user

> database applications, which will can bottleneck the LAN and slow

the

> overall NAS appliance performance with TCP/IP overhead.
> [...End Quote]
>
> And, here's the link to the whole document(watch the wrap):
> http://storage.ittoolbox.com/browse.asp?

c=StoragePeerPublishing&r=http%3A%2F%2Fad%2Edoubleclick%2Enet%2Fclk%
3B3604520%3B5699191%3Bl%3Fhttp%3A%2F%2Fnw%2Eittoolbox%2Ecom%2Fpub%
2Fcisco%5Fstoragenw%2Epdf

>
> And, even MS-SQL doesn't seem to support NAS, but it does support

SAN,

> with a warning(multiple fiber optic connections for fast access and
> redundancy in case one connection fails). Here's the reference for
> MS-SQL:
>

http://www.microsoft.com/technet/itsolutions/techguide/wssra/raguide/
Data_Services_SB_1.mspx

>
> --
> Best regards,
> Daniel Rail
> Senior System Engineer
> ACCRA Group Inc. (www.accra.ca)
> ACCRA Med Software Inc. (www.filopto.com)