Clojure
Rich Hickey discusses Clojure features and syntax, example code, functional programming, concurrency semantics, transactions, software transactional memory, agents, implementation and pain points.
- Java,
News
New File Storage Mechanism for SQL Server
Posted by Jonathan Allen on Dec 03, 2007 06:09 AM
SQL Server was never designed to act as a file system, but many developers use it that way nonetheless. Countless content management systems rely on either shoving large files into blobs or storing filenames. The former has subpar performance while the later requires manually keeping the file system in sync.
SQL Server 2008 seeks to correct this by introducing a filestream option that can be applied to a varbinary(max) column. When used, binary data is stored as files in a private section of a NTFS drive. This offers the performance of a normal file but without the concurrency and backup issues.
The files are created in a folder specified by creating a new FileGroup. In order to link files to rows, each row must contain a GUID column. No explanation was given for why this was necessary in addition to the actual file column.
RelatedVendorContent
Lean Software Development Governance, a whitepaper by Per Kroll and Scott Ambler
Offshore software development: Making it a success with Agile Practices
Architectural Quality: Design, Development and Testing Rules
The Future of Software Delivery According to visionaries Grady Booch & Erich Gamma
about time
by
joey jo jo shabadoo
Posted
Dec 3, 2007 8:09 AM
Re: about time
by
Brian Lyttle
Posted
Dec 3, 2007 8:49 PM
-
At least they are trying to address this. I've long been an advocate of keeping binary data out of the database and using the filesystem to um, store files. I've gotten weird looks in the past from Microsoft MVPs and n00bs alike. "Just put it in the database, that's what it's there for, it can handle it!".
-
At least they are trying to address this. I've long been an advocate of keeping binary data out of the database and using the filesystem to um, store files. I've gotten weird looks in the past from Microsoft MVPs and n00bs alike. "Just put it in the database, that's what it's there for, it can handle it!".
Well I there are limitations to both approaches. Depending on your needs, a single method of backup/restore may be useful. I think performance concerns can be dealt with in many situations, and you can end up with performance issues on the file system too. As with most things the fault is the people rather than the technology.
2 comments
Reply