halfmoonforever
Expert Member
- Joined
- Feb 1, 2016
- Messages
- 1,196
- Reaction score
- 9
That's amazing, they have double the users than facebook, yet I have never heard of them until now.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Unfortunately I can't +1 sqlite because the OP didn't specify the use-case. If the "mobile" needs to sync to some centralized database somewhere so that other "mobile" users can see/access the updated data and pull reports from everyone concerned, then sqlite won't fit in well because it's usually tied to the device that's not syncing to a central db at all.
They also failed to specify if this is a native app on mobile devices, or just a responsive HTML5 implementation. When working with HTML5, you have several storage options, but again, if the client, at any point in time wants to see what Sales Rep 1 is doing, there needs to be a central database to store this in.
Add it as a Nuget package then, it will sort everything out for you. https://www.nuget.org/profiles/mistachkin
I'm looking for something I can use because the one client does not want to install SQL server. It's a fairly small app itself only holds about 12 users information with time cards for each person. What can I use?
Feeling pretty stupid now with my flat file recommendation, to me his needs sounded basic enough.
What are the limitations on Express these days? We all have MSDN Enterprise setups so I am not sure what cutbacks they make on Express or Pro anymore?
They'll work but it's not future proof. If the app will stay a desktop app to run on one machine and the data will remain small then flatfiles with json data will work just fine.Feeling pretty stupid now with my flat file recommendation, to me his needs sounded basic enough.
Concurrent connections?Namely the query optimiser - that's reserved for people that have the cash to throw away. In addition you can't use column-store indexes on anything but Enterprise Edition. You're also limited to like 10GB per database.
No love for NoSQL databases when working server side? I've been a huge fan of MongoDB for the past 20 months and it scales quite easily using it's built-in sharding. Not the solution for on-device database though...
Don't feel stupid. In all my time on myBB this is the first time I took a look at something that even remotely has a bearing on what I do daily for a living. If the OP does end up using SQLite on his central point to which all mobile base stations report to I will be pretty impressed. Thus far the only server side DB I have worked with was MS SQL Server or Oracle 8i and above.
What are the limitations on Express these days? We all have MSDN Enterprise setups so I am not sure what cutbacks they make on Express or Pro anymore?
They actually quite decent these days
As of 2016 the SKU's are more aligned than ever before. Express can run on up to 4 cores, Max DB size of 10GB, and it misses some of the high end features.