Architecture question: vb.net with SQL similar to Access on shared drive

[phillipi]

I've been struggling with this issue, yet the answer is probably simple. I wrote an application in vb.net that uses SQL server 2005. However, I would like to deploy the application .. say on a folder on a shared drive.. and have multiple users access the application, but the database is being managed by SQL server, whether it's compact edition or express or the like. The original architecture was to deploy SQL Server's MDF file on SQL Server instance, on some "server" machine, but that would require the DBA to get involved.. .etc..

Basically, I want to offer a solution similar to someone dropping an Access file on the shared drive and having multiple users access it right away. What would the comparable "SQL Server" version look like, and what would be required in terms of software/architecture and for each client machine. Also, would concurrency be enabled is such an architecture?

Thanks,
Phillip

 

[cjard]

Quick answer?

Putting an MDF on a network share, and letting all clients use their local installation of SQLS Express engine to access that data file, is dumb

SQLS was created as a network aware DB so that you install the MDF in a SQLS instance ona network, then the clients conenct to that engine

 

[cjard]

but that would require the DBA to get involved..

So what? Presumably you hired that guy for a reason? (cjard is in cynic mode today)