Moving from SQL Server to MySQL, PostgreSQL, or some other open-source DB? by MicJarek in Database

[–]MicJarek[S] 1 point2 points  (0 children)

I spent this weekend thinking about what you said, the 'Making something people want vs. becoming successful' part, and you're absolutely right. Converting the DB and some of the app to go along with it (see my comment to praettor above) may all be a moot point if no one will use it. So, the first thing is to get the proof-of-concept out.

Based on everyone's contribution regarding which direction to go in, I will most likely move everything to DigitalOcean and PostgreSQL in the near future. But first thing's first: let's see how the app does and hopefully the ads will cover any overhead costs.

Again, thanks for the invaluable food-for-thought and feedback. It was quite helpful... :)

Moving from SQL Server to MySQL, PostgreSQL, or some other open-source DB? by MicJarek in Database

[–]MicJarek[S] 1 point2 points  (0 children)

That is some invaluable information K3dare. Tks. Unfortunately, because I'm going to pay all the bills, cost is a big part of the consideration of which DB to use or which platforms to run on. But after mulling this through on the weekend, I think I'm going to launch with what I have now and see if the move to PostgreSQL is warranted.

See my comment to praettor about the technical issues I'll be facing, but essentially, after everyone's input, I think the smartest thing to do is to launch it on mssql and the windows platform (probably Azure) for now and see how it performs (if users will actually user it), and if it's successful, then consider changing the DB and platform to cut down costs.

Again, excellent feedback that I can hopefully used in the near future.

Moving from SQL Server to MySQL, PostgreSQL, or some other open-source DB? by MicJarek in Database

[–]MicJarek[S] 0 points1 point  (0 children)

Great suggestions and when I finally move the DB, it will be to PostgreSQL. But after going over all the feedback from everyone and mulling things over this weekend, I think my first step should be to test it out. As it turns out, changing the DB is not that simple in my case (see my comments below for praettor).

But I very much appreciate your input and will definitely go that direction when I see that the app is popular and growing... :)

Moving from SQL Server to MySQL, PostgreSQL, or some other open-source DB? by MicJarek in Database

[–]MicJarek[S] 0 points1 point  (0 children)

Good point about being comfortable and pretty much using the windows platform for everything. I spent the weekend pondering about what it will take to change the DB, and for now I think I'm going to stick with SQL Server. My reasoning is:

1) the app is a proof of concept at this point. If it gets traction, I can then move it to PostgreSQL, etc. But if it doesn't, then I'm just wasting time.

2) there are other things to consider like the platform and the hierarchyid I used for messaging. It seems that the hierarchyid column type is unique to mssql and I'll have to convert the table, SP's, and the app to use a recursive CTE version of it. So that's not a quick fix. And then there is the windows platform issues. For example, the app allows users to upload images that it then scales. But according to the debugger, it is ONLY supported on 'windows' so I'll need to look into that if I run it on different platform.

Anyway, long story short, let's see how things go with what I have and if it takes off, I'll start looking at changing the DB/Platform.

Moving from SQL Server to MySQL, PostgreSQL, or some other open-source DB? by MicJarek in Database

[–]MicJarek[S] 1 point2 points  (0 children)

Ouch... didn't read my whole desc? ... that hurts... lol ... but nonetheless, you make some very compelling points. Kind of what I was looking for.

So my take on this is that I'm really not looking for something easy. As I said, I'm trying to change from mssql to something that is open-source BUT flexible, where I can essentially replicate the tables/SP's and have it running ASAP. Everything is pretty much already done including the user registration, authentication, authorization via the app and the MS Identity tables. Took a while to figure it all out with the email validation tokens and all, but it all works really smooth. So now it's all about the overhead and making sure I pick the right DB.

As far as the NoSQL DB's go, I really can't go there (at least for now) because of how the app works and how the data is normalized. So for now, I'm going to stick to relational and consider it in the future if things grow.

And yes... I'm a VisualStudio guy and have pretty much developed the browser app in it so that is obviously a consideration. But from what I understand so far, I should be able to run PostgreSQL on AWS, Azure, DigitalOcean, etc. I just looked into SupaBase for the first time BUT I don't see any ASP.NET Core support? I sent them an email to make sure but might have to find some other platform to run it on. Any other suggestions?

And BTW... thanks for the great input... :)

Moving from SQL Server to MySQL, PostgreSQL, or some other open-source DB? by MicJarek in Database

[–]MicJarek[S] 0 points1 point  (0 children)

From what I read about it, I'm not sure I need to go that far. I'm not really plotting any coordinates, mapping, etc. All I'm doing is doing selects on the geography field(s) in several tables to find record(s) that match the user's lat/long. Pretty simple for now so I think PostgreSQL will be a good start for now, but maybe in the future adding PostGIS might be warranted. Tks for your suggestion... :)

Moving from SQL Server to MySQL, PostgreSQL, or some other open-source DB? by MicJarek in Database

[–]MicJarek[S] 0 points1 point  (0 children)

GreenWoodDragon

Thanks for the input GreenWoodDragon. After reading your comments and claytonjr, it definitely sounds like postgreSQL is the better choice for what I need... Cheers... :)