I’m setting up a Subversion repository and I’m curious about using SQL Server as the backend option instead of the usual FSFS. I understand that Subversion mainly supports FSFS and Berkeley DB, but is it possible to configure SQL Server in this way? Has anyone had experience with this? Any insights into the advantages or challenges compared to the traditional file system would be appreciated.
interesting question! subversion doesn’t support sql server as a backend - it’s locked into fsfs and berkeley db. what’s driving you toward sql server specifically? trying to integrate with existing database infrastructure or chasing better performance? there might be a workaround i’m missing.
Nope, SQL Server won’t work as a backend for Subversion repos. The architecture just doesn’t match up - Subversion’s built around FSFS and Berkeley DB storage formats, not SQL databases. You can’t really hack around this with custom hooks or middleware because the core repository structure depends on specific file formats and transaction models that SQL Server can’t handle. I’ve migrated plenty of legacy repos, and FSFS is still your best bet for Subversion. If you really need database integration, you’d have to switch to a different version control system that actually supports SQL backends.
nah, sql server isn’t gonna cut it with subversion. it’s hardcoded for fsfs and bdb only. if you’re lookin for db integration, consider git with hooks or maybe switch to another vcs that plays nice with sql backends.