SQLite vs LocalDB in concurrent WCF scenario

I am creating a C# client server rendering application.

-The Server runs with a small Database holding 'jobs' and 'presets'

-The Clients (probably no more than 10) access the db every 2 seconds for example to poll for job information.

-The render nodes write to the server DB every 2 seconds to update the render status of the jobs.

All client server comms is done over a local network via WCF. Each write is only updating a row. Each read will read the whole single table of jobs. (approx 30 columns and maybe upto 500 rows)

I am currently using LocalDB in the development (with Linq-toSQL - but don't mind using connection strings), but its a bit of a pain to have to distribute the 140MB installer with the app and then install something during my installer, and have the DB file located only in a certain location.

I have just started looking at SQLite. It seems the perfect solution - lightweight, a single file, no installer.

But how does it deal with the concurrency with potential simultaneous[ concurrent] writes (and reads) from my render nodes/clients vs MSSQL LocalDB?

I have previously read conflicting things about write concurrency with LocalDB so any pointers would be appreciated if SQLite would be suitable in this scenario.