Re: SQL Server Yukon

> > Actually, it is supposed to happen. It has been widely publicized that
> > M$ will be replacing NTFS with a database running the SQL Server engine
> > (should be appearing in Longhorn). Instead of a file system that uses
> > directories, etc., one will just put their files into a database. It
> > should be obvious to this group the advantages of this approach.
>
> Surely you meant "disadvantages". There are plenty of obvious
> disadvantages, but very few obvious advantages to taking something
> simple (files in a directory) and making it complex (files in an
> SQL database). Just sticking a file in a "database" isn't going to
> make it searchable or locate-able in any meaningful way.

No. I meant "advantages". If your files are in a database, then many things become available to you that didn't exist before. You have much more control over security than file permissions and file groups have allowed you. What to give someone access to just a part of your datafile? You can do that when it is in a database. Want to audit access to sensitive files? You can do that when it is in a database. Want to back up just the block level changes to your files instead of the entire file? You can do that when it is in a database. Want to have some concurrency control on your files? You can do that when it is in a database. And I'm just getting started.....

Cheers,
Brian

-- 
===================================================================

Brian Peasland
dba_at_remove_spam.peasland.com

Remove the "remove_spam." from the email address to email me.


"I can give it to you cheap, quick, and good. Now pick two out of
 the three"