Click here to Skip to main content
15,891,375 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
I am creating software in Visual Studio using C# which I am going to need a SQL database for. In short, the database will need to hold data about cars and their models and very long “strings” of binary/hex data.

The software is going to need to be able to insert data into the tables and read and display from them.

Any tips or help is appreciated.

What I have tried:

I have created a small prototype with mysql workbench just to get the hang of SQL databases, but I’m having quite a few errors connecting data sources to Visual Studio.
Posted
Updated 6-May-22 4:47am
v2
Comments
PIEBALDconsult 6-May-22 8:43am    
It sounds like you may want to use compression for some of those strings. SQL Server supports compressing strings.

mysql all the way. Your connection errors are just that - errors. If you swapped to something else like Postgres or sqlserver, you'd likely have the same connection errors.

I've not done db development in years, but connecting to a db is that "first step". Post your errors.
 
Share this answer
 
Comments
Charlie Gale 6-May-22 9:11am    
I quite liked using mysql, and from what i’ve heard and videos it seems like quite a simple and useable option for me. I’ve only just started learning to use sql and databases. I think that they are just errors aswell but just are very annoying. Like for example i had to downgrade visual studio in order download the mysql extension. At the moment i’m facing issues connecting a data source. Cannot obtain provider factory for MySql.Data.MySqlClient is the one at the moment, but i think i can resolve it when i get home.
charlieg 6-May-22 23:48pm    
It's way too early in your process to even worry about what database to use. You need to get the transmission cranking :).

That said, if you get into a fight between MS dev tools and the database, your problem is the dev tools. -not the database. The amount of elephanting bullshit MS has caused with integration. is worthy of a public bit$h slapping.

It depends on what you are going to use it for.

If you will have multiple users simultaneously accessing it, then SQL Server or MySql are the appropriate system.

If you will have just one user at a time, and your data doesn't need to be shared between users, then SQLite or Access are good choices.

If you require "always on" data access, then consider a cloud solution - AWS or Azure.

But try and use a multiuser system for single user, and it's a PITA. It can be done, but it's a lot of work.
Try to use a single user system for multiuser access and it's a real PITA! Again, it can be done, but it throws up more intermittent problems that it's worth.

And try to user anything other than a cloud based solution for "always on" and you get into security nightmares.
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900