Could be... but I've dealt with companies where NO ONE is allowed on the server. So... it's just another tool in your box.

I admit that I have NO experience with MS SQL Server, and quite frankly, if the Access team will just add VSS to Access, I can't envision when I might need it for the projects I have planned. But never say never.

Now, I do have a good friend, that spends his entire day connected remotely to (one of) the SQL Servers doing all kinds of black magic stuff with stored procedures, of which he manages hundreds if not thousands. My eyes glaze over after about thirty seconds of him showing me what he does for users at the big "nonprofit" he works for. And he is just one of a team of over 15 administrators doing all this so users "don't touch the server".

Want to take a guess how many hours/days their system is down to "users" because some "administrator" screwed up? He says about half his day is wasted every day because some other administrator hosed their SQL Server systems or some planning meeting over some new hiccup. Now top management is tired of all this, and is looking to replace the entire "faulty" software. This grossly inefficient nonprofit has a budget in the hundreds of millions for "technology".

It all makes me wonder how, at my last job, I managed $US 18,000,000,000+ to the penny for 15 years on just one small 486 PC running a version of a minicomputer OS/Db for my commercial banking application with 25+ local users and hundreds of dial-up users doing inquiry.

VSS as in snapshots or backups?

VSS for getting a backup snapshot so that the db doesn't have to close and go exclusive just to backup a FE or BE.