|
>SQL Server 2000 doesn't, to my knowledge, support dbs on >network drives. Can't say about the latest release. Um, "support" is a relative term. <G> By default, SQLServer will not allow you to store the database files (data or log) on non-local drives. The stated reasons for this are performance and stability. On a local drive SQLServer can be assured that data written to disk has truly been written, the same cannot be said of remote drives. However, by setting on trace flag 1807 you can bypass that check. This is documented trace flag, but don't expect MS to spend time with you recovering your multi-TB database stored on a buffalo tech NAS device. SQLServer needs 1807 seton anytime you try to write to the network file, so your best option is to set it on as a startup flag. Do a google on DBCC TRACEON 1807 for more info. -Walden ------------ Walden H Leverich III Tech Software (516) 627-3800 x11 WaldenL@xxxxxxxxxxxxxxx http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.)
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
