Database Recommendation?
-
I have a pet project designed for VC++ 6 that uses SQLite3 as a database engine. The database component is used to manage approximately 2500 entries with the following: - PID (string, 63) - GID (short integer) - TID (short integer) - ID1 (string, 7) - ID2 (string, 15) It's not a terribly data-intensive application, so SQLite3 serves well, and the price is right. Eventually, the project will be distributed to about 12 people. I'd like to migrate the project to C#, so I need to replace the database component. I'd really like to avoid having everyone get a copy of SQL Server, so I'm hoping for a suggestion or two for a suitable replacement. I'd prefer to stick with something SQL-y if possible; I like to SELECT things. :laugh: Thanks! -- I've killed again, haven't I?
-
I have a pet project designed for VC++ 6 that uses SQLite3 as a database engine. The database component is used to manage approximately 2500 entries with the following: - PID (string, 63) - GID (short integer) - TID (short integer) - ID1 (string, 7) - ID2 (string, 15) It's not a terribly data-intensive application, so SQLite3 serves well, and the price is right. Eventually, the project will be distributed to about 12 people. I'd like to migrate the project to C#, so I need to replace the database component. I'd really like to avoid having everyone get a copy of SQL Server, so I'm hoping for a suggestion or two for a suitable replacement. I'd prefer to stick with something SQL-y if possible; I like to SELECT things. :laugh: Thanks! -- I've killed again, haven't I?
Typically, you can just write a .NET component (typically written in Managed C++ for performance, but could be written in C#) that calls unmanaged code to manipulate the underlying umanaged database. This is how the various database providers in the .NET framework are written. So you *could* write your own .NET data provider for SqlLite, if you were up to the challenge. If you'd prefer an already existing solution, have a look at VistaDB[^] or the MySQL .NET adapter[^]. *edit* looks like someone's already written a SQLLite for .NET driver[^].
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Little House on the Flickr Judah Himango
-
I have a pet project designed for VC++ 6 that uses SQLite3 as a database engine. The database component is used to manage approximately 2500 entries with the following: - PID (string, 63) - GID (short integer) - TID (short integer) - ID1 (string, 7) - ID2 (string, 15) It's not a terribly data-intensive application, so SQLite3 serves well, and the price is right. Eventually, the project will be distributed to about 12 people. I'd like to migrate the project to C#, so I need to replace the database component. I'd really like to avoid having everyone get a copy of SQL Server, so I'm hoping for a suggestion or two for a suitable replacement. I'd prefer to stick with something SQL-y if possible; I like to SELECT things. :laugh: Thanks! -- I've killed again, haven't I?
-
Oh wow, I can still use my SQLite database. That should work nicely! :-D -- I've killed again, haven't I?
-
I have a pet project designed for VC++ 6 that uses SQLite3 as a database engine. The database component is used to manage approximately 2500 entries with the following: - PID (string, 63) - GID (short integer) - TID (short integer) - ID1 (string, 7) - ID2 (string, 15) It's not a terribly data-intensive application, so SQLite3 serves well, and the price is right. Eventually, the project will be distributed to about 12 people. I'd like to migrate the project to C#, so I need to replace the database component. I'd really like to avoid having everyone get a copy of SQL Server, so I'm hoping for a suggestion or two for a suitable replacement. I'd prefer to stick with something SQL-y if possible; I like to SELECT things. :laugh: Thanks! -- I've killed again, haven't I?
Forget about SQL and learning more and more languages. You can use a native object database like db4o (http://www.db4o.com/) which is extremely fast and reliable. Regards
-
I have a pet project designed for VC++ 6 that uses SQLite3 as a database engine. The database component is used to manage approximately 2500 entries with the following: - PID (string, 63) - GID (short integer) - TID (short integer) - ID1 (string, 7) - ID2 (string, 15) It's not a terribly data-intensive application, so SQLite3 serves well, and the price is right. Eventually, the project will be distributed to about 12 people. I'd like to migrate the project to C#, so I need to replace the database component. I'd really like to avoid having everyone get a copy of SQL Server, so I'm hoping for a suggestion or two for a suitable replacement. I'd prefer to stick with something SQL-y if possible; I like to SELECT things. :laugh: Thanks! -- I've killed again, haven't I?
If each of these 12 people is using their own copy on their own desk/lap top, you can look at MSDE (old name) / SQL Server Express (new name) which is a three connection max version of MS SQL Server and totally free. It's a lot more mainstream and you can pick up the 120 day trial copy of SQL Server and have the Server Manager for development as well.
-
I have a pet project designed for VC++ 6 that uses SQLite3 as a database engine. The database component is used to manage approximately 2500 entries with the following: - PID (string, 63) - GID (short integer) - TID (short integer) - ID1 (string, 7) - ID2 (string, 15) It's not a terribly data-intensive application, so SQLite3 serves well, and the price is right. Eventually, the project will be distributed to about 12 people. I'd like to migrate the project to C#, so I need to replace the database component. I'd really like to avoid having everyone get a copy of SQL Server, so I'm hoping for a suggestion or two for a suitable replacement. I'd prefer to stick with something SQL-y if possible; I like to SELECT things. :laugh: Thanks! -- I've killed again, haven't I?
Thanks for all the suggestions, everyone. Since I can access SQLite with just a slight modification to my overall design scheme, I'm going to use the wrapper to get this first iteration out. After that, I'll weigh these alternate DB solutions. -- I've killed again, haven't I?